CompuServe Thread

Hi Ya Danny, << mdb.. >> With your laptop, you may want to use the 2 computer approach. This is documented in the REMOTE Debugging section of the MDB Tools manual on pg 125 of my manual. I use one computer and two monitors. For the one computer approach, your computer must have an additional mono video card installed and a monochrome monitor. additional environment variables are: set MDBHELP=d:\hc3_1\bin set MDBENV=d:\hc3_1\bin I get things going with the following bat file. mode co80 e: cd \3ds3 copy x:\jonasr\axptst_i.axp process cls mode mono set R386=-priv mdb -spath X:\JONASR -tandem cd \3ds3 MDB initializes and prompts for a file to load: "Executable program file name:" 3ds.exe<CR> // you should see assembler on your screen g <CR> //go.. 3ds should initialize // for axp debugging, you can do a modify/object/attributes/setting. // this causes an INT and the debugger regains control eip++<CR> // to step over the int load process\axptst_i.axp nocode // load in your code // if your source code is pointing to the correct path // *and* if you've compiled the *xp.c with the debug option // you'll see your source code now. // Set some breakpoints b ClientDoCustomDialog <CR> b pxp_in_axp<CR> // you can also use pg-up/pg-dwn in your source and then // click an a line number to set a breeak point. // From here on you can use single step into|over (F7|F8) or // the go command. g <CR> // .. this will execute to your next breakpoint. // // Note. Symbol/Examine // Check out the section in thge MDB Tools manual // regarding Following Pointers (5.14 in the debugger section) // and following the Call Stack.. Keep in touch with your progress..