11-11-2004, 11:23 PM
Sense the whole point of getting data from pre-release builds of diablo is to encorperate them into the retail version of diablo. Blizzard has some kind of dissassemblly protection on there executables(this is more evident in version v1.02+)....which is why version v1.00 would probley be the best version for this type of a project. I have looked at a disassembler which is capable of recreating a EXE from the decompiled data using MASM...called PEdasm.
Problem is there are seven variables that are not disassembled, and leave the nasm compiler hanging. In later versions(including hellfire) the number of missing variables goes up to around 16ish.
Would anyone care enough to help me find and correct this?
Problem is there are seven variables that are not disassembled, and leave the nasm compiler hanging. In later versions(including hellfire) the number of missing variables goes up to around 16ish.
Would anyone care enough to help me find and correct this?