CompuServe Messages

Jonas, Hello again. We have opted for remote debugging with the Metaware debugger. We've followed the installation instructions from Metaware and the Autodesk README.DOC for the IPAS3 Toolkit. Currently, we are able to "run386 mon 2 9600" successfully on monitor system mdb on remote system load "3ds.exe" (if we're in the 3DS3 directory on the remote) go (which loads 3DS on the monitor system) invoke the kxp on the monitor system the mdb goes to int3 we eip++ successfully load "ekg_i.kxp" nocode go (takes us to the user dialog on the kxp in 3DS) And now we're confused: 1. mdb is locked, no key functions at all 2. we aren't seeing source, but ASM 3. if we complete kxp and do a go we get a general fault protection from mdb. So, I have some questions: 1. Assuming the we've compiled/linked correctly "ekgmw30 debug" (a modified makesample.bat), and we've copied the source (ekg.c) and executable (ekg_i.kxp) to the 3ds3 directory on the monitor and remote. Also copied the ekg_i.kxp to 3ds3\process on the monitor system. set the source dir in mdb to c:\3ds3 Why are we not seeing source in mdb? 2. Any ideas why we have no mdb keyboard or mouse when the user dialog comes up in 3DS? Is it because 3DS is in control then? 3. Is the general protection fault error #00000000 a clue to anything? 4. From reading the README.DOC for IPAS3 toolkit it appears that it wants us to copy ekg_i.kxp and ekg.c to the 3ds3 dir on the remote, and the 3ds3 dir on the monitor system, I assume I also need to put ekg_i.kxp in 3ds3\process\ on the monitor system as well. Am I reading this correctly? It seems that it really only needs to be where 3ds picks it up for execution, and where mdb picks it up for source debug. Hope this was too garbled…I know what I mean 🙂 Steve