cgordon@vpnet.chi.il.us (Crash Gordon) (10/26/90)
OK. Windows has run sorta-OK for a couple of months. Sometimes it dies,
but I get by.
Recently, I started getting "Sharing Violation Error" when launching non-
windows apps via PIFs which call BATs. I have narrowed this problem down to:
Redirecting TTY output to NUL:. Apparently, WIN30 has decided to start
locking NUL: (??!!).
Example:
In a DOS window,
TYPE AUTOEXEC.BAT
works fine, but
TYPE AUTOEXEC.BAT > NUL:
gives me
Sharing Violation error reading drive A
Talk about stupid... What the &^%$ good is NUL: if it's lockable? And why
is it a _read_ error?
I'm constantly tuning and trying new things here (hoping to get something
90% as solid as vanilla DOS -- no luck yet) so it's probably something I
did, but what? I've tried everything short of deleting the WIN30 directory
and starting over...
-----------------------------------------------------
Gordon S. Hlavenka cgordon@vpnet.chi.il.us
Disclaimer: Yeah, I said it. So what?