CompuServe Messages

Stephen, << MDB.. >> I use the dual monitor on one system approach. Here's the bat I use to get into mdb to debug a program called bub_i.kxp. My code is on x:\jonas\bub.c and the executable is in e:\3ds3\process\bub_i.kxp. mode co80 e: cd \3ds3 copy x:\jonasr\bub_i.kxp process cls mode mono set R386=-priv mdb -spath X:\JONASR -tandem << load "3ds.exe" go invoke the kxp on the monitor system the mdb goes to int3 we eip++ successfully load "bub_i.kxp" nocode>> Here's where we differ: b ClientUserCode (set a breakpoint) b ClientDoCustomDialog (set another one) b … set some more and then go << assembler…?? >> When you trace your compile stream you may find that kxp.c which gets linked in to your *.obj is compiled without debug. Doing the above will display your code when you hit it and the assembler that you are seeing is probably kxp.c and not bub_i.kxp as you expected.. Good to see you in the depths of this. I've never used remote metaware debugging but it sounds like you are very close. Does your "mdb.. " line need a -dev n? Where N specifies the com port… jonas[adesk]