Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!wuarchive!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!kodak!uupsi!cci632!srw
From: srw@cci632.UUCP (Steve Windsor)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Okay, so am I missing anything from this AUX "device"?
Keywords: OX.SYS
Message-ID: <50444@cci632.UUCP>
Date: 7 Feb 91 13:38:36 GMT
Reply-To: srw@op632.cci.com (Stephen Windsor) (Steve Windsor)
Organization: CCI, Communications Systems Division, Rochester, NY
Lines: 22

In article <11332@jpl-devvax.JPL.NASA.GOV> brad@huey.Jpl.Nasa.GOV writes:
>
>Does OX.SYS fix this?  I've looked for OX.SYS on all my favorite ftp
>sites and haven't been able to find it.  Does anyone know where it is?
>
>Brad Hines
>Internet: brad@huey.jpl.nasa.gov
>Jet Propulsion Lab, Pasadena, California

Microsoft University gives you two files, WINOX.SYS, to place in your
CONFIG.SYS file, and WINAUX.EXE, a windows executable to drive the
sucker.  They gave this code freely to us when we left the class.

I do not know what WINOX.SYS will or will not fix.  I use it, along with the
WINAUX.EXE, as a debug window to display messages from my procs.
Note I have only one monitor; thus the winaux functions as an AUX: port
for me.  However, when codeview and the debug SDK is invoked, all bets
are off; winaux in my one monitor context dies, presumably because codeview
is not following the rules that winox has set.  So for codeview, as
far as I know, winaux will not help you.

stephen windsor    srw@op632@cci.com