rafetmad@oxy.edu (David Ronald Giller) (02/06/91)
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
akm@cs.uoregon.edu (Anant Kartik Mithal) (02/09/91)
Thanks to the person who posted ox.sys to the net. I scarfed it and installed it on my machine, and it seems to work just the way it is supposed to (i.e. dos and windows both write to the secondary monitor). However, once I get the message on my monochrome screen, I can't seem to get any further. I got a bit of info about where an error occurred. What happens is that when I switch to the debugging kernel, I immediately start getting errors. Apparently some of the applications that I use have bugs. I am running a bunch of things like screen peace and Winpost. So I am not sure what to do. The message on the secondary monitor said "abort, ignore, break?", so I said ignore, and the machine hung. thanks, kartik -- Anant Kartik Mithal akm@cs.uoregon.edu Research Assistant, (503)346-4408 (msgs) Department of Computer Science, (503)346-3989 (direct) University of Oregon, Eugene, OR 97403-1202
goodearl@world.std.com (Robert Goodearl) (02/09/91)
In article <1991Feb8.173232.24015@cs.uoregon.edu> akm@cs.uoregon.edu (Anant Kartik Mithal) writes: > I scarfed it [ox.sys] and >installed it on my machine, and it seems to work just the way it is >supposed to (i.e. dos and windows both write to the secondary >monitor). However, once I get the message on my monochrome screen, I >can't seem to get any further. ... >So I am not sure what to do. The message on the secondary monitor said >"abort, ignore, break?", so I said ignore, and the machine hung. > You need to know more about the error before you can "ignore" it. In most cases, the only viable choice is to abort. This causes windows to exit back to DOS. It's not great, but it's better than having to do a power -- Bob Goodearl -- goodearl@world.std.com
chrisg@microsoft.UUCP (Chris GUZAK) (02/11/91)
In article <1991Feb8.173232.24015@cs.uoregon.edu> akm@cs.uoregon.edu (Anant Kartik Mithal) writes: >kernel, I immediately start getting errors. Apparently some of the >applications that I use have bugs. I am running a bunch of things like >screen peace and Winpost. Call these people up and tell them their programs have bugs! Don't trust any software that rips. Everyone needs to understand that you can't develope a clean windows app without the debugging version of windows. Programs that rip are simply buggy programs! >kartik >-- >Anant Kartik Mithal akm@cs.uoregon.edu >Research Assistant, (503)346-4408 (msgs) >Department of Computer Science, (503)346-3989 (direct) >University of Oregon, Eugene, OR 97403-1202 Chris Guzak