Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcsun!unido!fauern!NewsServ!rommel
From: rommel@Informatik.TU-Muenchen.DE (Kai-Uwe Rommel)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Okay, so am I missing anything from this AUX "device"?
Message-ID: <1991Feb13.140620.2657@newsserv.informatik.tu-muenchen.de>
Date: 13 Feb 91 14:06:20 GMT
References: <1991Feb6.193818.11660@javelin.es.com> <11332@jpl-devvax.JPL.NASA.GOV> <1991Feb11.192300.29677@dbase.A-T.COM>
Sender: news@newsserv.informatik.tu-muenchen.de
Organization: Technische Universitaet Muenchen, Germany
Lines: 19

In article <1991Feb11.192300.29677@dbase.A-T.COM> awd@dbase.A-T.COM (Alastair Dallas) writes:
>OX.SYS has one slight problem and that is that the debug display is a 
>stack trace (which is surprisingly useful--it knows the names of the 
>System toolbox calls you've made) followed by Abort, Ignore, etc.  The
>OX.SYS magic can't conjure up a keypress from the AUX device to save
>itself, so you end up rebooting.  When CodeView is active, the stack trace 
>appears in the command window and the keyboard is heard.

Because I did not have OX.SYS, I wrote a replacement which I called
AUXIL.SYS. It has the advantage over OX.SYS, that it always returns 'I'
on reads from this device and thus only shows the stack traces and then
continues program execution. I find this useful to be notified of errors
and use CodeView then to locate it. On the other hand, there exists a
program called MDA.EXE or VGA.EXE which even allows keyboard input in
response to the Abort.. prompt. And it supports the VGA/8514 setup which
I also plan to support with my own driver. If there is interest, I could
put my driver on cica.cica.indiana.edu or post it to c.b.i.p.

Kai Uwe Rommel