Exetools  

Go Back   Exetools > General > General Discussion

Notices

Reply
 
Thread Tools Display Modes
  #1  
Old 12-06-2005, 01:04
squareD's Avatar
squareD squareD is offline
VIP
 
Join Date: Aug 2005
Location: Banana Republic
Posts: 287
Rept. Given: 31
Rept. Rcvd 35 Times in 27 Posts
Thanks Given: 32
Thanks Rcvd at 106 Times in 69 Posts
squareD Reputation: 36
WKT-VBDebugger and Win XP?

Hello,

I worked with WKT P-Code Debugger under Win98 without any problems so far.

Just installed under Win XP SP2 and this error message is coming up:

Quote:
Compiled with VB6
Address of table 1: 4014d0
Can NOT locate the VB DLL inside this computer.

Can NOT find a ENGINE section for the DLL.
Installation worked not very well, because WKT was unable to write IMAGEHLP.DLL in system32 directory,
because IMAGEHLP.DLL was used by some other processes...

May this be the reason for error, or any other suggestion?

Regards,
squareD
Reply With Quote
  #2  
Old 12-06-2005, 02:45
ricnar456 ricnar456 is offline
Friend
 
Join Date: May 2002
Posts: 290
Rept. Given: 1
Rept. Rcvd 28 Times in 10 Posts
Thanks Given: 0
Thanks Rcvd at 52 Times in 40 Posts
ricnar456 Reputation: 28
i use wkt in XP - Sp2 and work perfect for me

Ricardo Narvaja
Reply With Quote
  #3  
Old 12-06-2005, 03:39
Unforgiv3N's Avatar
Unforgiv3N Unforgiv3N is offline
Friend
 
Join Date: Aug 2005
Posts: 172
Rept. Given: 0
Rept. Rcvd 0 Times in 0 Posts
Thanks Given: 0
Thanks Rcvd at 3 Times in 3 Posts
Unforgiv3N Reputation: 0
works here too!

but you can install Micro$oft Virtual PC and Debug your Application in your Virtual PC
Reply With Quote
  #4  
Old 12-06-2005, 14:02
MengLong
 
Posts: n/a
Perhaps msvbvmXX.dll in use
Reply With Quote
  #5  
Old 12-06-2005, 18:22
imagin
 
Posts: n/a
Quote:
Originally Posted by MengLong
Perhaps msvbvmXX.dll in use
Yes - and register library + copy target to WKT directory.
Reply With Quote
  #6  
Old 12-06-2005, 22:59
Sarge
 
Posts: n/a
I have that problem a lot...I forget to be ready for it every time I install the debugger on a different computer. I seem to have the best luck if I install ALL the files in the debugger directory...don't let Windows put stuff in the System directory. The debugger seems to prefer it's OWN copies of the support files in it's OWN directory, not someplace else, and not an upgraded version...but it's own exact, specific files in it's own, exact, specific directory.

Hope this helps.

Sarge
Reply With Quote
  #7  
Old 12-12-2005, 17:10
xyzjhe
 
Posts: n/a
It only use WIN9X!
Reply With Quote
  #8  
Old 12-12-2005, 20:24
imagin
 
Posts: n/a
Quote:
Originally Posted by xyzjhe
It only use WIN9X!
It isn't truth,I I have win XP SP1 and WKT works OK.

- install WKT - (ignore message "IMAGEHLP.DLL........")
- copy Msvbvm60.dll (Msvbvm50.dll) to \system.32 and too to WKT directory!!
- copy target to WKT directory!!!!
- run WKT - File Open - Action RUN
- click OK on the message box "Running under win NT / 2000" (ignore this )
- click OK

..and WKT works

Last edited by imagin; 12-12-2005 at 20:41.
Reply With Quote
  #9  
Old 12-13-2005, 01:51
Sarge
 
Posts: n/a
I believe this is the significant statement:


Quote:
- copy Msvbvm60.dll (Msvbvm50.dll) to \system.32 and too to WKT directory!!
Although I usually do not copy the dll to the system directory, as it messes with the dll required for vb.

Sarge
Reply With Quote
  #10  
Old 12-13-2005, 18:24
squareD's Avatar
squareD squareD is offline
VIP
 
Join Date: Aug 2005
Location: Banana Republic
Posts: 287
Rept. Given: 31
Rept. Rcvd 35 Times in 27 Posts
Thanks Given: 32
Thanks Rcvd at 106 Times in 69 Posts
squareD Reputation: 36
Quote:
- copy Msvbvm60.dll (Msvbvm50.dll) to \system.32 and too to WKT directory!!
Sorry Sarge, but no need to do this...

WKT works perfect without copying the dll to WKT directory.

In my case the error occured, because msvbvm60.dll was in use by another program.

Don't know why WKT couldn't share the dll with other programs.

Regards,
squareD
Reply With Quote
  #11  
Old 12-17-2005, 03:12
Sarge
 
Posts: n/a
As I said, it's finicky (hmmm, did I say that?). And I use the "copy the dll" trick because it always works (at least, so far) even in those occasions where you DON'T need to do it (duh!). It's easier for us senior citizens to remember one workaround than have to do things differently each time.

And of course, when you DO want to run that "other program" at the same time??

Good luck

Sarge
Reply With Quote
  #12  
Old 12-17-2005, 19:47
squareD's Avatar
squareD squareD is offline
VIP
 
Join Date: Aug 2005
Location: Banana Republic
Posts: 287
Rept. Given: 31
Rept. Rcvd 35 Times in 27 Posts
Thanks Given: 32
Thanks Rcvd at 106 Times in 69 Posts
squareD Reputation: 36
Yeah Sarge, you're absolutely right.

I did explain, why another prog was running in an earlier posting.
But this one was blocked by admins, because they thought I was increasing my counter.

Hope they not do again, because I'm nearly 55 years old and don't think about playing such a kind of child stuff...

Program running was a router controller, which is always running in background.
Cracked this prog long time ago and couldn't remember, that it was written in VB.

May be, because I'm really a senior...

Regards,
squareD
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT +8. The time now is 08:01.


Always Your Best Friend: Aaron, JMI, ahmadmansoor, ZeNiX
( 1998 - 2022 )