Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!usc!oxy!rafetmad
From: rafetmad@oxy.edu (David Ronald Giller)
Newsgroups: comp.windows.ms.programmer
Subject: AUX port....
Message-ID: <142879@tiger.oxy.edu>
Date: 6 Feb 91 01:46:33 GMT
Distribution: usa
Organization: Occidental College, Los Angeles, CA  90041
Lines: 29

There seems to be alot of question on the net about the AUX device, and what
it is used for under windows.  Some Observations I have made:

I have never found a way to redirect AUX to com2:.  I have a modem on com1:,
and I don't particularly care to move it.  AUX is supposed to be one of the re-
directible standard streams, derived from Unix.  The problem with AUX on
com1: isn't that I cannot use it, but rather that when Windows Debugging
Version starts up, it ALWAYS puts my modem into auto-answer mode.  Without
fail.  What's up, Msoft?  Did you do this on purpose for dial-up debugging?
If so, why didn't you tell us?	If not, why does this happen?

Contrary to what has been said on the net numerous times, Windows will NOT
redirect the debugging output to a monochrome monitor, UNLESS YOU HAVE EITHER
OX.SYS (or equivalent) OR A DEBUGGER RUNNING.  It doesn't even see the extra
monitor, but happily writes to the AUX port.

Even if you do have a com1:, if you don't have a terminal hooked up to it, but
have it unused or (you guessed it) a modem, messages going to AUX sometimes
give the annoying 'Can't Write to device AUX...' message.  This happens about
half the time when I run my debugging versions of my programs without the
debugger running.  I get a bunch of noise as Windows pesters my modem, and then
when the modem bites back (just a metaphor, it's not the modem's fault) Windows
pukes this complaint back at me.

-Dave

David Giller ----- (rafetmad@oxy.edu) or (dgiller@oxy.edu) ------------ Box 134
"Some of us wake up -- others roll over."		     Occidental College
"It's easy to deceive a child." 			  Los Angeles, CA 90041