Xref: utzoo comp.sys.ibm.pc:46889 comp.binaries.ibm.pc.d:7120
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ogicse!zephyr.ens.tek.com!tekcrl!tekgvs!toma
From: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Newsgroups: comp.sys.ibm.pc,comp.binaries.ibm.pc.d
Subject: Re: Redirecting 4Dos output? ( > nul is bad)
Message-ID: <7153@tekgvs.LABS.TEK.COM>
Date: 22 Mar 90 00:49:52 GMT
References: <17026@orstcs.CS.ORST.EDU>
Reply-To: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Followup-To: comp.sys.ibm.pc
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 32

In article <17026@orstcs.CS.ORST.EDU> gatesl@uranus.CS.ORST.EDU (Lee Gates) writes:

>	After some dishartening attempts, I have rtfm, and not figured
>out the change to redirect output to nul.  I have several batch files
>I use daily, and after installing the new version of 4Dos, they aren't
>getting along too well.

I noticed this, too, in the new release. 
The problem occurs when redirecting to any file.
It seems to be cause by:

1. Using SHARE (have have a 320 meg partition in DOS 4).

and

2. When 4DOS (latest version) redirects output, it opens the file denying
   access to other programs. This, of course, may make sense for files and
   most devices, but hardly makes sense for NUL.

and

3. If the program run is a TSR, then the handle is left open.

Therefore

All following programs cannot access that file/device

I plan to call on this bug, but have been too lazy to do it yet.

Tom Almy
toma@tekgvs.labs.tek.com
Standard Disclaimers Apply