[info]don't Dos When Modifying Dialog Resources

Hy.

I tought i'd post a problem that i've found and it's solution, so that other people don't do the same mistake i did :lol:

When you modify a DLL, CPL or EXE file, don't use Resource Hacker to modify the dialog resources as it sometimes screws up the file. For that you can use Restorator (or some other resource editor).

I've found out the hard way, i modified some dialogs in COMDLG32.DLL, replaced the original in the system, and after booting i couldn't get the "Open/Save" dialogs opened, it always say "USER32.DLL encountered a problem" :blink:

The worst part was, that i also modified another file after this and the system simply failed to boot up (it just hanged before showing the user selection dialog), and i ended up reinstalling the entire OS.

Anyway, you can check if the file is screwed up or not, if you open it again in ResourceHacker and when you try to see the dialogs it says "Invalid resource, possible a compressed EXE" (or something like that), than you better get your original file an start moding it again :rolleyes:

I hope this helpes others from having to reinstall windows.

#215510

Good advice. Reshacker can sometimes corrupt files on save.

Another tip: if you do a lot of hacking to system files, the best option is to perform your experiments on a dual boot machine. That way, if you screw something up where you can't boot, you can easily get back in and restore the original files without having to do anything tricky. For my experimenting machine, I have XP and 2000 both installed.

#215520

That's why you should make all adjustments to a file with reshacker the first time around. If you need to make additional changes, start fresh.

#215617

Actually the best way is to do all of your expirements on an installation of XP in VMware. Configure the XP install the way you want it and create a snapshot of it. Test your hacked files. If something isn't the way you want it, revert back to the snapshot, and in less than a minute it's back the way it was before the hacked files. This is also a great way to create screenshots of before and afters and stuff like that.

NOTE: VMware DOES support copying files from the host computer to the virtual computer, but you must install VMware Tools after the operating system is installed. Once in the menu bar go to "VM" --> "Install VMware tools". Installing VMware Tools also improves the speed of the virtual computer and allows larger resolutions to be run.

For those insterested you can download VMware trial HERE

Also, ResHacker does NOT corrupt system files if you know what you are doing. In my first forrays of file modding, I too ran into corrupted files. There's a reason though. If you are working on the file in ResHacker, do NOT delete the backup file it makes after you save, and do not move the original file while ResHacker is open. Basically do NOT touch the file until you have saved and closed ResHacker. Once ResHacker is closed, you can delete the backup file, rename the original file, move it, etc. Make your file mods, save, close ResHacker.

#215650

Originally posted by flyakite@Sep 21 2004, 03:44 PM

Actually the best way is to do all of your expirements on an installation of XP in VMware.

Nice tip. Thanks.

If you are working on the file in ResHacker, do NOT delete the backup file

Aha! Well there ya go. Didn't realize that. Thanks again for the handy tip.

#215680

Hy.

After my little "incident" (or i should call it accident) with Reshacker, i made a dual boot on my computer, both of them being XP. (one is installed on C: and the other on F:), but i think flyakite's ideea to use VMWare is better since it's a lot easier to revert to a snapshot in VmWare than to reinstall a "real" XP :-)

On the other hand, i believe i'me to blame for the "corrupted" files, i didn't know i'm not "allowed" to move the files while they are still opened with Reshacker, i made the (wrong) assuption that ResHacker loads the file in memory and it doesn't matter that it's been deleted since it can recreate it. But it turns out it only modify the resource part of the files, so if the file is moved, it can't recreate it since ResHacker only knows the resources part. (i hope i didn't mix something up :D).

Good "Res" hacking to everyone. :woot:

#215786