This is such a fundamental problem, I thought I'd have no problem finding info, but after googling it to death, I can't even find anything similar - on installation I get the following error -

error opening file for writing:
C:\WINDOWS\system32\IMAGEHLP.DLL

The dll is there and not read only, so I continue after hitting retry several times by hitting "ignore"

Now when I try to open a Pcoded file I get the error that the VB dll's can't be found on this computer - yes I did copy BDASMDLL.DLL to both /system and /system32 - and I have VB6 installed on this machine so all the files MSVBM60 etc. are there - is this a problem with XP SP2? or am I being patently stupid again and missing something obvious?

SiGiNT

According to http://64.233.179.104/translate_c?hl=en&sl=zh-CN&u=http://bbs.pediy.com/printthread.php%3Fs%3D99ffbb8c0c86007e11610c6de933bc84%26threadid%3D1724&prev=/search%3Fq%3Dwktvbde%2BIMAGEHLP%26num%3D100%26hl%3Den%26lr%3D%26safe%3Doff ("http://64.233.179.104/translate_c?hl=en&sl=zh-CN&u=http://bbs.pediy.com/printthread.php%3Fs%3D99ffbb8c0c86007e11610c6de933bc84%26threadid%3D1724&prev=/search%3Fq%3Dwktvbde%2BIMAGEHLP%26num%3D100%26hl%3Den%26lr%3D%26safe%3Doff"), you need an older version of msvbvm60.dll ("2003 version". No clue if this is true or not.

you can rename your imagehlp.dll, edit the renamed with lordpe, setting the charateristics of .text to e00000020, save it, rename to the original name and that should do the stuff.
Regards, Fighter_81

Thanx fighter 81 I'll give it a try.

SiGiNT

disavowed, fighter_81 -

Combination of the 2 fixed the problem! many thanx! - for anyone else who reads this in the future - the part to change of the .text sec. is the flags - my file was 60000020 - change to E0000020.

SiGiNT

Also - don't replace your MVBVMXX.DLL files in system32 put the 2003 versions in your target's directory.


OOPS! spoke too soon - I now get an information window that says running under WINNT with an ok button - when I click on that it exits - shit!

FYI, one trick that I've seen is when the author of the target VB program changes "MSVBVM60.DLL" to "msvbvm60.dll" in the Import Table, since IIRC WKTVBDE does a case-sensitive search for the DLL name in the IT. This can obviously be fixed by changing the string to the uppercase one.