Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!chinacat!uudell!twaddle.dell.com!jporter
From: jporter@twaddle.dell.com (Jeff Porter)
Newsgroups: comp.windows.ms.programmer
Subject: Re: What the heck is this AUX device?
Message-ID: <14909@uudell.dell.com>
Date: 6 Feb 91 17:12:38 GMT
References: <1991Jan31.182905.7337@javelin.es.com> <1991Feb2.190407.24906@dbase.A-T.COM>
Sender: news@uudell.dell.com
Reply-To: jporter@twaddle.dell.com (Jeff Porter)
Organization: Dell Computer Corp.
Lines: 12

It sounds like you are running a buggy application under the debugging
version of Windows.   When a Windows API function receives a invalid
window handle (i.e. NULL or such), it generates a trap that displays a
stack trace on the AUX port.  If you don't have a terminal connected and
the port initialized (MODE COM1:2400, for example), Windows will choke when
trying to write message.  If you have a monochrome card installed, Windows
will display the message on that instead.

I've noticed that Word For Windows 1.0 also generates these error messages.
It sounds like MicroSoft didn't get quite all of the bugs out...

Jeff Porter