Path: utzoo!attcan!uunet!samsung!gem.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!aries!mcdonald
From: mcdonald@aries.uiuc.edu (Doug McDonald)
Newsgroups: comp.windows.ms
Subject: Re: Redirecting Output of Debugging Windows
Message-ID: <1989Oct29.173056.12091@ux1.cso.uiuc.edu>
Date: 29 Oct 89 17:30:56 GMT
References: <32251@ucbvax.BERKELEY.EDU>
Sender: paul@ux1.cso.uiuc.edu (Paul Pomes)
Reply-To: mcdonald@aries.scs.uiuc.edu (Doug McDonald)
Organization: ^
Lines: 18

In article <32251@ucbvax.BERKELEY.EDU> kipnis@janus.Berkeley.EDU (Gary Kipnis) writes:
>Hi, when using debugging version of windows to test my programs when an
>error occurs windows tries to write to the serial port where a monitor
>should be connected.  I don't have a second monitor connected so is there a
>was to redirect this debugging output from the serial port to some file
>on the disk?
>The main reason for doing this is that windows doesn't let me do anything
>untill it successfully writes to the serial port and I just have to reboot
>the machine.
>

I had this problem also, so I hooked up a PC Portable as a terminal.
It reproduced screen after screen after screen of useless garbage
that said, quite clearly "I am totally corrupted", and then died. So
I now simply reboot my machine (twice?? Why do I have to do it
TWICE?) when the garbage starts, and use debugging statements in my program.

Doug McDonald