Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!sjsca4!poffen
From: poffen@sj.ate.slb.com (Russ Poffenberger)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Cannot read from device AUX
Keywords: System error
Message-ID: <1991Jun27.204914.6664@sj.ate.slb.com>
Date: 27 Jun 91 20:49:14 GMT
References: <1991Jun24.122339.3944@cs.ruu.nl> <1991Jun25.192820.5631@hyper.hyper.com>
Reply-To: poffen@SunOS (Russ Poffenberger)
Organization: Schlumberger Technologies, ATE division, San Jose, Ca.
Lines: 29

In article <1991Jun25.192820.5631@hyper.hyper.com> bonneau@hyper.UUCP (Paul Bonneau,,) writes:
>In article <1991Jun24.122339.3944@cs.ruu.nl> tim@cs.ruu.nl (Tim Dumas) writes:
>>
>>
>>  What kind of bug causes the system error box, Cannot read from device
>>  AUX, to appear? It comes up at arbitrary points in the execution of the
>>  msw program I'm developping and also in some programs I ftp'd from cica.
>>
>>  If someone knows what's happening, please let me know by mail.
>>
>Windows has detected an error (see Appendix C "Windows
>Debugging Messages" in "Reference Volume 2"), and is
>attempting to write debugging info to your com port (com1
>I think by default).  This is commonly known as a "rip"
>(for Rest In Peace perhaps :).  Installing a terminal on
>your com port will both show you the message, and prevent
>the dreaded MessageBox.
>

Ans if you don't have a terminal, or the AUX port free to even hook one up,
there is a package called "winrip" that will route the messages to a secondary
monochrome monitor. There is also a driver "ox.sys" which will do this, but I
don't like it because it cannot provide the necessary input to continue once
it happens.

Russ Poffenberger               DOMAIN: poffen@sj.ate.slb.com
Schlumberger Technologies       UUCP:   {uunet,decwrl,amdahl}!sjsca4!poffen
1601 Technology Drive		CIS:	72401,276
San Jose, Ca. 95110             (408)437-5254