Problem with resource Hacker

[redhat]

I was tweaking my Win XP system with Resource Hacker. I edited the msgina.dll file to change the shutdown dialog box. But, when I replace the original msgina.dll with the modded file, my system refuses to boot. It gives an error in winlogon.exe saying that a reference variable could not be read...
On replacing the modded file with the original, the system boots perfectly. All I did in the file was change the BMP's related to the dialog box

How do I replace the msgina.dll file without causing a problem??

[VarDOS]

Try Replacer

[redhat]

I AM using replacer to replace the system files, but on restarting after a replacing msgina.dll, the system refuses to boot, claiming an error in winlogon.exe

[Krazy Bluez]

Try one thing, If you can get a live boot cd of XP or linux then use it to copy the msgina.dll from the xp cd, usually it is msgina.dl_ which is nothing but it's compressed version, and replace it with the patched one...

Or else use the repair option on the installation point of XP.....this should solve the problem, the first one might be tough but the later one takes long time.....

[redhat]

^^ I had an original backup and i of-course replaced it to start my system. But the problem is that i want to use the tweaked msgina.dll

[Krazy Bluez]

One thing, have you deleted the msgina.dll_original file ? coz its been reused by resource hacker to update the file.

[Vishal Gupta]

"msgina.dll" file is very essential file and a small mistake while editing this file can make your system not bootable.

I think either you edited some code in the dialog box or your new BITMAPs dimensions are not matching with the default ones.

So make sure you use the same dimensioned BITMAPs to replace the default BITMAPs in dialog box.

[redhat]

I was following your tutorial on askVG.com and downloaded the bitmaps from the link given there. so i suppose there should not be a problem with them, and no, i havent edited any code in the dialog boxes, just replaced the bitmaps as the tutorial asks you to do

[Vishal Gupta]

^^ Thats strange. Because no one has faced any problem while editing this file and I have checked it already.

Are you using some other protecting software which is causing this issue? May be some security software checks the integrity of file and refuses to start whenever the file is edited?

[redhat]

Nope, I am not using any such software. I found it strange too because I have often edited sysdm.cpl and shell32.dll on my own too, without using any reference and such a problem has never occured