🚀 go-pugleaf

In article <1992Sep3.202411.3690@dcatlas.dot.gov>, joet@dcatlas.dot.gov (Joe Trott) writes:
|> leadfoot@bigbootay.sw.stratus.com (Mark Curtis) writes:
|> 
|> >I can not get MS's C7 pwb to compile inside a dos window.  It gets
|> >a sharing violation on the dev NUL.  NUL is used to throw away
|> >unwanted output.  Outside of windows all is fine, but inside a dos
|> >window any write accesses to NUL produce share violations.
|> 
|> >copy \autoexec.bat nul               inside a dos window causes A/R/F
|> >                                     error message.  PWB displays an
|> >                                     error prompt and aborts.
|> 
|> It is hard to resist thinking that this is an act of self preservation on
|> the part of Windows.  Only by plugging up NUL can it prevent itself from
|> being sucked into the void where it belongs.

I found the problem.  When I installed C7 somewhere in the docs it
said something about redirecting kernel debug messages.  I don't have
a second monitor or a dedicated terminal on com1, so I redirected the
debug output to nul.  In system.ini I added:
[debug]
OutputTo=nul

This was the problem!

I'm not sure what to use so I just put a file name in there for
right now.  Fixed the problem.

Mark