At 07:08 PM 4/25/2004 -0400, Patrick J. LoPresti wrote: >Michael Devore <[EMAIL PROTECTED]> writes: > >> I don't do kernel work, but depending on how much you want to dig in >> the guts of the problem, you might want to grab the 386SWAT debugger >> and load it immediately after the driver, with nothing else. It >> should catch the exception and throw you into the 386SWAT debugger. > >After paring down my boot disk, I got 386SWAT to fit (with 2K to >spare). And by invoking it with "DEVICE=A:\386swat.lod TRAPINV", I >actually get thrown into the debugger where I used to get invalid >opcode + reboot. > >So it's a start. But I really have no idea what I am looking at...
Another thing, besides the register and CPU stuff. Type D 40:7B <enter> at the command line down at the bottom. What is the byte value of the first entry on the memory display? Want to make sure that BIOS is not flagging the machine as supporting VDS, since that would be A Bad Thing. ------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
