scorpy Posted September 20, 2004 Posted September 20, 2004 Ok so in my previous post, http://www.msfn.org/board/index.php?showtopic=27967&hl= , I could not get several folders to delete. I did figure out the Alcohol ones, but those Windows Shared folders are tricky. So last night I came up with an idea that just might work. My batch file does seem to delete them if I run it after getting into Windows. I usually run it through cleanup.cmd, but that must be a tad to early. SO what if I were to have another cmd file that would delete them on next reboot, by using the msconfig run option? I would just import that cmd file through cleanup.cmd, have it run on reboot, and delete the value back out of the MSConfig. Could it work? It might be a long shot, but I thought there might be someone crazy enough to figure this out.
bonedaddy Posted September 20, 2004 Posted September 20, 2004 The older ver's of nlite use a cmd file run from, I think hive, that pops upon the destktop just seconds after the desktop does. This is very powerful,I just add my cleanup stuff right to the cmd and everything is deleted, all theicons. the printing thing in startmenu, driver and install folders, all gone. So ifyou don't use nLite perhaps you can use Nuhi's method.
MHz Posted September 20, 2004 Posted September 20, 2004 You could use a self-deleting cmd script in the startup folder. I use this with success. For me, it removes some shortcuts, closes some windows, and deletes itself while rebooting the pc.
TechnoNRG Posted September 20, 2004 Posted September 20, 2004 the easiest way is to have the batch file do a check to see which boot it is on.1. put the batch into the "%ALLUSERSPROFILE%/start menu/startup/" location. This way it will run no matter who logs on.2. The batch file should look something like this.cleanup.cmd@echo offclsdir /b test.echoif errorlevel 1 goto endecho "in the middle":endecho File now exists > test.echo echo the endwhat this does it the code "in the middle" will only run when the file test.echo exists. If the file test.echo doesnt exist then it creates it. This way the file will only be run on the boot after you place the shortcut into the start menu. If you want it to wait to boots then just check for the existance of another file in the end section using the same dir but with a diffrent file name. the "in the middle" code is where you put your cleanup code. Just remember to add to your cleanup code to delete the startup link, and the directory where you put this batch file and the test.echo etc. Do not put this cmd directly into the startup folder, only a shortcut so that the extra file generated dont try to get run when the computer logs in.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now