Path: utzoo!mnetor!tmsoft!dptcdc!jarvis.csri.toronto.edu!rutgers!apple!bionet!ames!pacbell!att!chinet!mcdchg!ddsw1!ddsw1!point!wek
From: wek@point.UUCP (Bill Kuykendall)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Redirect > nul affects procomm, why?
Message-ID: <[1058.5]comp.ibmpc;1@point.UUCP>
Date: 20 Jul 89 05:00:06 GMT
References: <3816@cps3xx.UUCP> <[1058.4]comp.ibmpc;1@point.UUCP>
Lines: 20

>are.  For Procomm 2.42 it should be SET PROCOMM=PATH.

Make sure that you include a trailing backslash on the path.  e.g.
SET PROCOMM=C:\\PROCOMM\\ in your autoexec.bat.  At one point, (I think this
bug was fixed but I don't remember) it was necessary to copy command.com
into the directory that contained procomm's support files as well.

There is also a known bug (I think it's in 'DOS, not Procomm, as it affects
Ventura Publisher and CSAM Picture Perfect as well) that causes programs to
exibit variably strange behavior if there are more than about 1330 bytes
in your environment (regardless of the assigned size).  Procomm is one of
the programs affected by this.  I've seen this behavior under IBM 3.2 and
Compaq 3.31 Doses.

(In the path statement above, one backslash is needed in each location.  My
editor interprets these, so there are two.  If you see two, ignore the
seconds |*)  )

Bill Kuykendall
...ddsw1!point!wek