Re: Any idea why NUL is busy inside of windows?

Article View: comp.os.msdos.programmer

Article #1267

Back to comp.os.msdos.programmer Previous Next

#1267

From: Joe Trott
Date: Thu, 03 Sep 1992 20:24

20 lines
1209 bytes

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.

(Sorry...just got carried away for a moment...)

Seriously, do you need more file handles?  Just a wild guess...

-JTT

Technical Details

Message-ID: <1992Sep3.202411.3690@dcatlas.dot.gov>

Path: arc1-ca.pugleaf.net!sparky!uunet!dcatlas!joet

References: <6126@transfer.stratus.com>

Show Full Headers

Complete Article Headers

Newsgroups: comp.os.msdos.programmer
Path: arc1-ca.pugleaf.net!sparky!uunet!dcatlas!joet
From: joet@dcatlas.dot.gov (Joe Trott)
Subject: Re: Any idea why NUL is busy inside of windows?
Message-ID: <1992Sep3.202411.3690@dcatlas.dot.gov>
Organization: U.S Dept. of Transportation
References: <6126@transfer.stratus.com>
Date: Thu, 3 Sep 1992 20:24:11 GMT
Lines: 21

Reply to Parent Message