On Fri, Jul 3, 2009 at 4:34 PM, Shane Baggs<shan...@hotmail.com> wrote: > I've posted before about the four machines I'm running FreeDOS on -- One is > exceptionally well behaved with FreeDOS 1.0 and another is exceptionally > quirky. In particular, I've been experiencing the FreeCOM bug where the > command prompt returns without executing the command. Nobody knows for sure > when this happens, but it seems to happen in response to a general > protection fault that goes unreported, as 4DOS reports a general protection > fault under the same conditions. > > I just discovered MDADEBUG, available from Marc Alexander's page > http://www.onr.com/user/mda > It's a debugger as a TSR. > > I've got a machine where the bug can be triggered on a fairly regular basis. > I've been able to trigger the bug, then press ctrl/alt/F12 and get the > debugger. > Now that I've got the bug and the debugger, what should I look for?
It's probably a good idea to use the debugger to log what calls to int 0x21 occur between calling a command and the next prompt that occurs. We want to know exactly what FreeCOM is doing so that we can hopefully find out what is happening differently than in a normal instance. > > > ________________________________ > Lauren found her dream laptop. Find the PC that’s right for you. > ------------------------------------------------------------------------------ > > _______________________________________________ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > > ------------------------------------------------------------------------------ _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
