Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!sbi!zeus!cf_su10!cf_su14!nee From: nee@cf_su14.Sbi.Com (Robert Nee) Newsgroups: comp.windows.ms.programmer Subject: Re: What the heck is this AUX device? Message-ID: <161@cf_su20.cf_su10.Sbi.COM> Date: 4 Feb 91 14:32:46 GMT References: <1991Feb2.223122.26046@world.std.com> <1991Jan31.182905.7337@javelin.es.com> Sender: news@cf_su10.Sbi.COM Reply-To: nee@cf_su14.Sbi.Com (Robert Nee) Organization: Salomon Brothers, NY Lines: 30 I would like to point something out to programmers with a second monitor. If you run the device driver OX.SYS then you can tell the SDK spy application to route it's output to COM1 a.k.a AUX a.k.a your second monitor. This is very helpful and I use it alot. One other piece of info: OX.SYS while it will let you see the fatal exit messages and stack trace, it does not let you reply to the Abort, Break, Ignore prompt. I have a utility that will let you do this. It redirects messages to the monochrome monitor by replacing the OutputDebugString routine after it is run (I guess it does this similar to the way ATM replaces the Windows font routines.) It will also let you reply the prompts after the stack dump rather than being forced to reboot. This program does not completely replace OX.SYS. As mentioned above, if you want to redirect AUX to the MDA you still need OX.SYS. One last thing: OX.SYS does nothing for users with a 8514/VGA setup. This program (MDA.EXE) will work in this configuration and it will also send output to your primary monitor if you only have one! Please mail me if you would like this utility. I do not have ftp access, I would ask that the first person who mails me a reply who does place this utility on cica or where ever appropriate. Robert F. Nee