View Full Version : WKT VB Debugger
whoda
January 28th, 2003, 01:32
I have tried to load a few exeutables with this app and I keep getting these errors.
Can NOT locate the VB DLL inside this compute
and
Can NOT find a ENGINE section for the DLL.
I'm running winxp pro. any help as to why I'm getting these errors?
wbe
January 28th, 2003, 03:08
Close all other VB apps.
wbe
whoda
January 28th, 2003, 03:35
tried that didn't work
rebooted and shut down everything still didn't work
nofurs
January 28th, 2003, 07:27
WKT Visual Basic Debugger only debug's p-code vb programs.It might not work on native vb
whoda
January 28th, 2003, 13:43
I'm actually going through a tutorial that uses this for the crackme I'm trying to crack
zacdac
January 28th, 2003, 14:41
You can get that error if another app/process is trying to debug/access the target application or if the pcode debugger is already running (it may have not terminated the process correctly).
Also make sure the support dlls (the WKT dlls) are in the correct directory. Check the help text for what they are..
Hope that helps.
Zac
whoda
January 28th, 2003, 23:16
I don't think it's anything debugging the target application or anything like this, because like I wrote earlier I have rebooted and hit clt-at delete and tried to shut download everything expect a few things.
as far as the dll files, the help menu only talks about two help files that are supposed to be in the windows directory. Both of these dll files are there.
zacdac
January 29th, 2003, 00:08
Sorry I forgot to mention something. The error you mention will occur if any other program are accessing/using the vbruntime files. So you may have something that is running at startup etc that is a vb authored app. Close it done and it should fix the problem.
BTW, Only the bdasmdll.dll needs to be in the windows system directory, but it doesn't matter if the other one is in there or not.
Zac
esther
January 29th, 2003, 11:30
You need to put WKTVBDE.dll,bdasmdll.dll in your system directory.
Btw what operating system are you using
sarge
January 29th, 2003, 13:03
I had a similar problem under Win98. I have this text file as a note to myself:
WARNING!
This file will overwrite "imagehlp.dll" in the SYSTEM directory with
a different version. This version will not work under WIN98. Before
installing, make a copy of the original "imagehlp.dll", then overwrite
the new file with the copy of the original.
Maybe this will help.
Sarge
whoda
January 30th, 2003, 01:52
thanks for the help
I did a search for both files and I have the first dll file, but when I do a search I do not have this dll file wktvbde.dll but I noticed it's in the C:\Program Files\WKTVBDE directory which if the program is calling it it should look there. But I copied and paste this file in the windows directory anyway and still getting the same error.
Durring installation I do get an error when installing. It says
Error file opening for writing imagehlp.dll. I click ignore and continue with installation. The problem is still there.
My first post indicated that I was running windows xp pro. Is anybody else using winxp pro and this utility?
I sent a friend the setup and 2 crackmes that instruction tell to open it with wkt vb debugger. My friend gets the exact same error I do
sarge
January 30th, 2003, 13:07
Yeh, that image.hlp error thing is exactly what I got originally, too.
I just checked my install, WKTVBDE.dll is in the WKTVBDE directory, along with LOADER.exe. IMAGEHLP.DLL is in the WINDOWS/SYSTEM directory.
It didn't work for me when the copy of IMAGEHLP.DLL that comes with the program was kept in the WKTVBDE directory also, while the original IMAGEHLP.DLL was in the WINDOWS/SYSTEM directory. This (as was mentioned), should have kept them separate , but... it didn't work.
On my first install, the included IMAGE.HLP overwrote the original Windows file and crashed my system. After numerous re-starts, I followed a work-around procedure : Re-install the original Windows IMAGE.HLP file into the SYSTEM directory (from a backup or CABS), make a backup copy of it, install WKTVBDE, let it overwrite the original file, then erase the just loaded file and rename the backup copy.
As for the occurance of the error, it exists of course since IMAGEHLP.DLL is in use by Windows. I don't remember specifically how I got around it, but I am sure that that is your problem. I even sent an Email to the authors about this, but I don't know if they followed up.
Good luck.
Sarge
Powered by vBulletin® Version 4.2.2 Copyright © 2018 vBulletin Solutions, Inc. All rights reserved.