Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!rochester!udel!burdvax!gvlv2!kleonard
From: kleonard@gvlv2.GVL.Unisys.COM (Ken Leonard)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Redirect > nul affects procomm, why?
Message-ID: <278@gvlv2.GVL.Unisys.COM>
Date: 17 Jul 89 16:16:28 GMT
References: <3816@cps3xx.UUCP> <3817@cps3xx.UUCP> <8234@bsu-cs.bsu.edu>
Distribution: usa
Organization: Unisys Defense Systems, NISD, Great Valley Laboratory
Lines: 22

In article <8234@bsu-cs.bsu.edu> dhesi@bsu-cs.bsu.edu (Rahul Dhesi) writes:
* In article <3817@cps3xx.UUCP> gcook@cps3xx.UUCP (Greg Cook) writes:
* >I
* >have some programs that I install in my autoexec.bat such as kbfix2 and
* >dosedit.  I used the "> nul" to redirect the output to nothing so I 
* >won't see the messages those programs put on the screen.  However, if
* >I do this, procomm has problems.
* When you execute something from autoexec.bat, and that thing makes
* itself memory-resident, and if its output has been redirected to
* something, some strange undocumented things happen inside MS-DOS.  I
* suspect some files are remaining open permanently.  (When the TSR's
* non-resident part exits, MS-DOS doesn't seem to close all its open
* files.)
* Why this should affect Procomm I don't know.  Maybe you don't have
* FILES=xx large enough in your CONFIG.SYS file, and the one extra
Re: my earlier followup:  ASIDE from clobbered internal paths to files
which _are_ unlikely, Rahul has _this_ one RIGHT.  I had forgotten
about it, but it _is_ _very_ _easy_ _to_ _get_ _into_.
* permanently open file is enough to cause Procomm to run out of file
* handles.
----
Ken