lpl

Empty Temporary Internet Files - this adds a right click option when you click on folders and on right click start menu too, to empty the -well duh, temporary internet files... Hmm I did a search and found nothing so here's a "tweak" I hope someone finds useful it did for me. not a super fantastic tweak, but it beats the hell out of going to tools-->internet options-->delete files-->check delete offline files-->wait a minute--->ok out. Note: the number 23 can be replaced by whatever unique number you wish, just have to be consistant throughout the tweak.. ;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [HKEY_CLASSES_ROOT\Directory\shell\Empty Temporary Internet Files] [HKEY_CLASSES_ROOT\Directory\shell\Empty Temporary Internet Files\Command] @="cleanmgr.exe /sagerun:23" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\VolumeCaches\Internet Cache Files] "StateFlags0023"=dword:00000002

Here is my code for adding windows explorer to cleanup.cmd...replace %cdrom% with %systemdrive% in this case.. COPY /Y "%cdrom%\install\QuickLaunch\Windows Explorer.lnk" "%UserProfile%\Application Data\Microsoft\Internet Explorer\Quick Launch"

This has worked for me... ;Use small icons in both Windows Explorer and IE [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\SmallIcons] "SmallIcons"="yes" hope it helps

i googled, and this's the only url that popped up on your specific error... http://www.sitepoint.com/forums/archive/index.php/t-88869 seems hard-ware (RAM) related. ?!?

hi..im a newbie myself but i've encountered the same problem before... this happened when i had installed xp successfully on VPC and tried to reinstall over it... this article has some info you might find useful... http://support.microsoft.com/default.aspx?...3&Product=winxp however that didn't solve my problem...in fact my problem never got solved. i just deleted the whole virtual machine file and created a new one..never had that problem again this way hope this helps.

thanks for the help... i had tried this on clean install in virtual pc (unattended reg tweaks applied via cmdlines and later on again at runonceex), and it didn't work. i deleted the persistent handler part, and even just deleting the "data" value leaving only the nullfile value didn't work either. *shrug* next im going to try just adding in a nullfile value on the next install...

great idea. i would try it out (when my computer goes down for reformat that is)... one question though, at t-12 min (or whichever minute cmdline executes, i forget), would the winnit.sif's driversigning policy have already been revoked? If so, then wouldn't we have to "attend" to it?

Thanks for your help. I wasn't trying to get it to say Windows NT Command prompt. When I first added in the nullfile value into the .cmd key, I right clicked to the new menu and the Windows NT command prompt (or script or whatever) appeared, which was great. but later on I added in the data value, and now it's disappeared forever. the codes for opening .cmd files with notepad by default was hopefully, incidental to this, I was just wondering if the two could have affected each other, as that was the only other thing i did before i added in the data value to .cmd key... hope you get what i mean.

Hi, Newbie here. Have been stuck to this thread for a few weeks now Following the advice here, I tried to create a ShellNew Windows NT Command script, but for some reason it doesn't work. Any ideas what I could have gone and done wrong? Situation: I had created the nullfile value and the beautiful words popped up when i right clicked new menu. Then later on I read down the page, and decided to try the data values. So, my itchy hands added in the data value, and behold, the thing's gone. Here is my ShellNew code: [HKEY_CLASSES_ROOT\.cmd] @="cmdfile" [HKEY_CLASSES_ROOT\.cmd\PersistentHandler] @="{5e941d80-bf96-11cd-b579-08002b30bfeb}" [HKEY_CLASSES_ROOT\.cmd\ShellNew] "NullFile"="" "Data"=hex:40,45,43,48,4f,20,4f,46,46,0d,0a Note: I also messed around with opening cmd files by notepad by default. Could this have messed it up? This's the code for that. ;Open Windows NT Command Script (.cmd) with Notepad by default - do not run [HKEY_CLASSES_ROOT\cmdfile\shell] @="Edit" [HKEY_CLASSES_ROOT\cmdfile\shell\Execute] "EditFlags"=hex:00,00,00,00 [HKEY_CLASSES_ROOT\cmdfile\shell\Execute\command] @="\"%1\" %*" [-HKEY_CLASSES_ROOT\cmdfile\shell\open] Sorry for the long post!