Article View: comp.os.ms-windows.setup
Article #1106Re: Can't pipe to NUL in a dos session - Help please!
From: Fuzzy Fox
Date: Wed, 18 Nov 1992 17:56
Date: Wed, 18 Nov 1992 17:56
21 lines
1311 bytes
1311 bytes
ANAVARRO@vm.poly.edu (Anthony F. Navarro) writes: >When in a DOS session, be it at the command line or in a batch file, >if something is piped to NUL ( i.e. dir >NUL ) i get a "sharing violation >reading drive c - Abort, retry, fail" error. I get this at the command >line and in my batch files. It's possible that in your AUTOEXEC you loaded a TSR and piped its output to NUL in order to avoid seeing the startup text on the screen. Since the TSR never exits, it may not have closed the standard output device (NUL, in this case), and thus further attempts to modify that device result in a sharing violoation. I don't know if this can actually happen, but it doesn't hurt to go look. -- #ifdef TRUE | Fuzzy Fox (a.k.a. David DeSimone) fuzzy@netcom.com #define TRUE 0 | #define FALSE 1 | "You have been recruited by the Star League to defend #endif | the Frontier against Xur and the Kodan Armada."
Technical Details
Message-ID:
<1992Nov18.175648.17461@rei.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!rei2!foxReferences:
<168A28014.ANAVARRO@vm.poly.edu>Show Full Headers
Complete Article Headers
Newsgroups: comp.os.ms-windows.setup Path: arc1-ca.pugleaf.net!sparky!uunet!rei2!fox From: fox@rei.com (Fuzzy Fox) Subject: Re: Can't pipe to NUL in a dos session - Help please! Message-ID: <1992Nov18.175648.17461@rei.com> Date: Wed, 18 Nov 1992 17:56:48 GMT References: <168A28014.ANAVARRO@vm.poly.edu> Organization: Recognition Equipment, Inc. Lines: 21