hexhack

Anybody know of a cracked version for Vista? I tried to hexedit the file bootmgr (which kind of replaced setupldr.bin or ntldr) but this file has a checksum as well. I would like to point it to different BCD files.

I have been running these suggestions now for a long time... Just wanted to report it's stable, no problems did occur at all. And what a beautiful silence: No more directories are created. Wonderful... Still an impertinence that you have to employ such drastic measures to stop your operating system from it but that is a different story. Just out of curiosity: Did anybody follow my guide and try it? Would be nice to hear your suggestions especially since there was a lot of discussion going on before...

There is a way to prevent the creation of "Recycler" and "System Volume Information". I was _very_ annoyed by these reapearing directories, so I looked into it and came up with the following solution. It is quite hardcore so you should now what you are doing... BE WARNED... 1) Create a complete backup of your harddisk. You will be messing around with system files, so don't take this easy. Things might go wrong. And have a bootable CD ready to recover your system... 2) Use a program that is capable of searching for hex values, e.g. Total Commander. Search for the following hex string in your drive containing windows: "530079007300740065006D00200056006F006C0075006D006500200049006E0066006F0072006D006100740069006F0 06E" with is nothing else than "S y s t e m V o l u m e I n f o r m a t i o n" - that's how it is stored in executable files. Note that there are not simple spaces but hex00 values, that is why we are using that search string. 3) You will be returned with some files. Now use a hex editor, like winhex, and search in all returned files for the hex string from above. Every finding replace with a different tag, eg ongoing numbers (Change "S y s t e m" in "S y s 0 0 1" and so on). And keep track which number you assigned to which file. After doing that with all files, you can now easily determine, which one is causing the creation of the directory from the number in the directories name. For me, it was the "ntoskrnl.exe" in the system32 folder. 4) Copy this file to a different directory. Change the SVI with your hex editor to "C:\WINDOWS\TEMP". Boot into the recovery console, replace the original file with your altered one. (Think about the dllcache directory. Either delete all files in that directory or be aware of replaing the file here as well.) NOW YOU ARE FREE OF SVI DIRECTORIES... 5) Remove all previous SVI directories from your system (eg. by using that script posted earlier). Now you should test your system for stability. After perhaps 3-4 days you can reinstall your backup and replace only the files that needed modification. You can do the same for Recycler according to the method stated above. Search String is "520045004300590043004C00450052" to be replaced by hex 20 values which is equivalent to space. For my sytem, it was shell32.dll in system32 directory. Again: You should now what you are doing... Just a nice example: If you replace the SVI with hex 20 values, you get a nice directory with a name of blanks. Very difficult to remove from you system... So, both files seem to be using different methodes of creating the directories.