WKT-VBDebugger and Win XP?

squareD · #1 12-06-2005, 01:04

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

ricnar456 · #2 12-06-2005, 02:45

i use wkt in XP - Sp2 and work perfect for me

Ricardo Narvaja

Unforgiv3N · #3 12-06-2005, 03:39

works here too!

but you can install Micro$oft Virtual PC and Debug your Application in your Virtual PC

#4 12-06-2005, 14:02

Perhaps msvbvmXX.dll in use

#5 12-06-2005, 18:22

Quote:

Originally Posted by MengLong

Perhaps msvbvmXX.dll in use

Yes - and register library + copy target to WKT directory.

#6 12-06-2005, 22:59

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

#7 12-12-2005, 17:10

It only use WIN9X!

#8 12-12-2005, 20:24

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

#9 12-13-2005, 01:51

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

squareD · #10 12-13-2005, 18:24

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

#11 12-17-2005, 03:12

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

squareD · #12 12-17-2005, 19:47

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