Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!ncar!tank!eecae!cps3xx!gcook
From: gcook@cps3xx.UUCP (Greg Cook)
Newsgroups: comp.sys.ibm.pc
Subject: Redirect > nul affects procomm, why?
Message-ID: <3817@cps3xx.UUCP>
Date: 17 Jul 89 01:13:09 GMT
References: <3816@cps3xx.UUCP>
Sender: usenet@cps3xx.UUCP
Lines: 24

From article <3816@cps3xx.UUCP>, by gcook@cps3xx.UUCP (Greg Cook):
> Recently, someone posted a request for help concerning procomm not being
> able to find the dialing directory.  I have just started to experience
> the same difficulty.  Whoever you were, do you know how to fix it?

I seem to have found the problem, but it doesn't make sense to me.  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.  It won't find the dialing directory,
it won't run command.com when using DOS gateway, and it won't run
script files (cmd files).  

If I use > nul on only some of the programs, then procomm only acts 
up on some things (ie. it loads dialing directory, but won't do
DOS gateway).  This is very puzzling to me.

I have two questions:

1.  What exactly is the "nul" ?
2.  Why is this affecting PROCOMM?

Greg Cook
gcook@horus.cem.msu.edu    cook@frith.egr.msu.edu