🚀 go-pugleaf

In article <RHARMON.92Dec10144328@triton.uucp> you wrote:

: I got a System error: Can't read from device AUX'

Try setting AUX=NUL in your system.ini.  I do not remeber in which section of
system.ini it goes into off-hand, but I will check it out and e-mail you 
later.  Do not hesitate to remind me by e-mail if I forget!

: This happens if I try to resize the Solitate app.  The only other thing running
: is clock.

: Anyone know why Its got to read from AUX (when I didn;t ask it to).

I means that it's trying to dump some debugging info to AUX port (it does 
not mean that you have an error anywhere !).  Normally, you'd have a second
monitor attached to the computer, and it would serve as a AUX output device
for the debugging kernel, but since you don't have one and you haven't told
kernel that you don't, it is still trying to output the info to AUX and of
course fails to do so.  

I've had a lot of trouble with this problem myself -- that's why I did not use 
debugging kernel for almost a yeart, until I figured out what the problem
was.

If you do not want to buy a second monitor for debugging messages, you should be
using DBWin utility which comes with SDK.   DBWin shows all the info that 
was supposed to go to the secondary monitor in a window.  The only thing that
it does not do is show back-trace in case your app produces an error-msg --
for speed reasons this feature has been turned off by MMicrosoft.  All that
needs to be changed to get back-trace is three or four lines of code; you
can get this from Microsoft's CompuServe forum.

E-mail me if you have any other questions on this
---------------------------------------------------------
Alex Vinogradov
Cornell Cooperative Extension, Electronic Technology Group
avinogra@empire.cce.cornell.edu
(607)256-8129

-- 
---------------------------------------------------------
Alex Vinogradov
Cornell Cooperative Extension, Electronic Technology Group
avinogra@empire.cce.cornell.edu