evilvoice

i never said your method was wrong...just run at a different time...runonce is executed after runonceex...no matter what anyone tells you...which is why I said programatically, coolsights2000 would technically be the correct method, because it STAYS in the runonceex mode, it never leaves it and goes to runonce method until it is completely done...Now, I do admit yours probably looks better because you only have 1 window at a time...and in the end Ill prolly use the method you posted...I was just making an observation just in case it comes down that someone has a problem with it, then they could go backwards a step or 2 and see...honestly, I dont think itll cause any problems, but just take a look at all the posts and im sure youll find 10% of them are about people having a problem that the person who posted the solution never counted on...So, in closing, nologic, your command works and looks better (and less files too), but if there is a problem using your files, you should let people know that they can fall back on coolsights2000's method...

anectdotally???? hmm, yes Im the one who says its not backwards compatible...ill run sp2 version on my sp1 machine and write the error verbatim (see I can use big words too LOL j/k RyanVM) msiexec.exe - Ordinal Not Found The ordinal 280 could not be located in the dynamic link library msi.dll (this is using sp2's msiexec.exe on a sp1 machine)

personally...programatically for windows, coolsights2000 is better. For info...runonce executes after runonceex is already finished...so therefore youre launching runonceex at a later time...

this doesnt look to be working notice the missing S?

Windows Server 2003 Remote Desktop client

ya know, i have a problem with the cdshell site...michael talks about releasing a new cdshell, but if you check the date of the post, its the date after the download was released...and im wondering if he will post up a new version...honestly, you could prolly email him and talk to him about your problem...and if he deems its a problem, he'll fix it...he was always nice on 911cd forums...I would say post there, but the boards are down...doctor xp is working on them...im evilvoice on those forums also...but most of the people releasing programs there are always nice...doctor xp, bart, michael (i think thats how you spell his name), henk...theyre all pretty cool.

i replied to the other thread, but I believe what I answered is what your problem is...and youd have to go back to the last 1.x version to resolve your issue.

ok, first, are you compiling cdshell into an iso (with 2.0 you could compile all boot files into an iso or single file)? second, where are your dat files? in root of cd? they need to be in the iso of cdshell and not in the root of the multiboot iso...i dunno how to translate this to german...basically its like this if you have cdshell.iso - your dat files and all image files need to be contained within cdshell.iso...in fact, i think with the commands your running, they must be in the boot folder if not using cdshell.iso, all dat files need to be in the boot folder where cdshell.ini resides.

hmmm, unless the update overwrites sfc_os.dll wfp should never be turned back on...you just gotta watch out for when it gets overwritten...but, the other flipside of the coin is that if you disable wfp and delete dllcache, as I do, if sfc_os.dll gets overwritten, how will windows rebuild the dllcache...so I think even if it does get overwritten, itll never be able to truly reactivate wfp.

uhm, sorta...renaming the one in dllcache makes it so that when windows does its little wfp thing, it doesnt copy windows notepad over metapad...he renames it to old just to keep it in case, I assume...so thats why notepad.exe is renamed to notepad.old in every case...but the reason its done in dllcache first is because of wfp.

well, here is a question...runonceex waits for each command to finish before going to the next, correct? what about runonce? does it wait for a command to finish before going to the next...I ask this because then you could have your runonceex execute, then itll close runonceex and move on to runonce keys, then you could have runonce load a new runonceex.cmd and the run iernonce.dll, then once that finishes, runonce will execute the next command, which would be runonceex3.cmd and execute iernonce.dll (maybe this will get rid of the errors the other guy was having...from the other thread) but it all depends on if runonce pauses, or if it just runs everything at once...If anyone wants to know, if you reshack iernonce.dll you can make scrollbars appear...BUT, when you exectue iernonce.dll, it shortens the entire screen so nothing is displayed other than the windows text and the titlebar...so maybe if someone knows where I went wrong? I tried using edit instead of listbox, and then I tried messing with listbox, there has to be someway to get listbox to display scroll bars after running out of a specified area...I really would like to see runonceex with scrollbars.

personally, I agree, it would be nice to have a croll bar in the runonceex window...but first youd need someone that knows how to program scrollbars in a dll, then you could edit the dll that runs runonceex.cmd (ierunonce.dll I think, dont quote me on it though) I could take a look at some dll's and see if I can figure out how to put one in.

well, extract mine with innounp...run ISTool 4, goto registry, delete all keys...click and drag your registry.reg file into the window, it should import your settings, but after drag and drop, click on script and check to make sure everything looks right (REG_BINARY messes up in drag and drop)...also check shortcuts...if you want more, add exactly like I have Pad.exe. Dont change the Setup heading...unless you want to, but I have it compressed to the max...

I meant move the software to the hard drive, not the runonceex.cmd's...I think after a while your cdrom craps out on ya, but youll have to moce your software to $OEM$\$1 folder, and change your runonceex.cmd's

ok, finished, let me know where to upload...its on 3.04...if you want though, you can extract mine with innounp and change some things...like default language is english right now...and if you wanna change some settings and whatnot...

I have no idea what that button is, i have it too...honestly it looks like going from full mode to regular, or regular to compact...if you dont show the titlebar, its a gray button - doesnt even look like it belongs with wmp and double clicking it maximizes/restores the window...and to answer youre other post...it should be fine to go from wmp8 to wmp10

could you try testing on your hard drive, instead of cdrom? ie using $1 folder...and report back if that works...because as i see it, that would have to be about the only thing messing it up...

hmmm, so now that JohnnyDo has completed a list of ALL tweaks...can a mod close this thread and open a new one with the first post being the reg file of JohnnyDo? And then we can all post NEW TWEAKS in this new thread? just a thought, cuz to me, this thread has really gotten cumbersome...

uhm, yea, definitely want that one LOL

deleted

@bitmonster...I believe idle.newbie, after I made my comments, decided that it wasnt all 7zsfx installs, that it was just this one program that he sfx'ed that had this problem...he might have thought since it didnt work with that app, it wouldnt work with .net, but at least he gave us a warning to check against, I would have hated to have a MACHINE folder on my computer...certain "out of place" things annoy me LOL.

finally works for my screens YAY!!! good job jcarle.

I didnt get this directory in profiles that youre talking about. hmmm, gotta retest...updates didnt install...will post back though shortly

@keul...nowhere did I see anyone say that they stopped t-39 from continuing and see what happens at that point...but you say you have, so thats all I wanted to know.

have you thought about testing if adding the files to dosnet.inf would work...one way to test it to maybe open a batch that pauses the main window, but first opens another cmd window so you can do some tests...the first test would be to run drvz.exe and see what happens...as I dunno if anyone has actually done some error checking at t-39, this would be a way...you could also run regedit and see if the reg keys are in fact being put in the registry...its hard to tell anything after the install has already taken place...and also, if you dont test at t-39 and wait until t-13 it would still cause problems, cause does anyone know for a fact that setup doesnt overwrite the driver reg keys? But this is what I would do to test... 1. add files to dosnet.inf 2. create a cmd file. @ECHO OFF start cmd pause 3. then alt+tab to the one not paused 4. run drvz.exe and see if you get any errors, if not proceed...if yes, write them down 5. proceeding 6. goto location the drivers are supposed to uncompress to...check and see if anything exists...are files being uncompressed here (should be...cant really mess up an extract command) 7. check locations and make sure they are in the correct subfolders 8. run regedit 9. check HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath and see if anything exists in this key 10. check the unsigned driver policy key (dunno where its at, but honestly, if you have your winnt.sif to ignore the policy, you shouldnt have to check this key. If anyone has done all these steps and verified that it doesnt work, could you post back at what step it failed at (1-10) so maybe serialzs can fix this...I know its asking a lot, but I really dont want to have to run drvz.exe to get reg locations to update the hive.inf file everytime I add a driver/driverpack...but if this truly is the only way, then I guess we are stuck with it...