Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!bsu-cs!dhesi
From: dhesi@bsu-cs.bsu.edu (Rahul Dhesi)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Redirect > nul affects procomm, why?
Message-ID: <8234@bsu-cs.bsu.edu>
Date: 17 Jul 89 04:09:26 GMT
References: <3816@cps3xx.UUCP> <3817@cps3xx.UUCP>
Reply-To: dhesi@bsu-cs.bsu.edu (Rahul Dhesi)
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 21

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
permanently open file is enough to cause Procomm to run out of file
handles.
-- 
Rahul Dhesi <dhesi@bsu-cs.bsu.edu>
UUCP:    ...!{iuvax,pur-ee}!bsu-cs!dhesi