CompuServe Thread

Hi Ken, << I'm able to run my 3DS and my IXP without running debug (MDB), but can't even get 3DS to run under MDB. >> 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 // clear any changes to the screen…. e: cd \3ds3 // note that i'm in the 3ds directory copy x:\jonasr\axptst_i.axp process cls mode mono // passes control to the mono screen set R386=-priv // (from the ipas2 readme..) mdb -spath X:\JONASR -tandem 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 ——————————————————————————- ——- Ken what happens here after you've typed the g <carriage return>? are you using the dual monitor approach? // 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 more_functions.. <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..