Any idea why NUL is busy inside of windows?

Article View: comp.os.msdos.programmer

Article #1241

Back to comp.os.msdos.programmer Previous Next

#1241

From: Mark Curtis
Date: Thu, 03 Sep 1992 01:09

17 lines
1073 bytes

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 isn't pwb that is causing the problem.  Start windows, open a dos
window, and try the above copy.  Yes you do need to have share loaded.

Any ideas on how to get around this?

Works fine outside of windows.

Mark

Technical Details

Message-ID: <6126@transfer.stratus.com>

Path:

arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!rpi!bu.edu!transfer!bigbootay.sw.stratus.com!leadfoot

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!rpi!bu.edu!transfer!bigbootay.sw.stratus.com!leadfoot
From: leadfoot@bigbootay.sw.stratus.com (Mark Curtis)
Newsgroups: comp.os.msdos.programmer
Subject: Any idea why NUL is busy inside of windows?
Message-ID: <6126@transfer.stratus.com>
Date: 3 Sep 92 01:09:45 GMT
Sender: usenet@transfer.stratus.com
Lines: 17