Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!tank!eecae!cps3xx!gcook
From: gcook@cps3xx.UUCP (Greg Cook)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Procomm HELP!
Message-ID: <3829@cps3xx.UUCP>
Date: 17 Jul 89 22:22:50 GMT
References: <646@chyde.uwasa.fi>
Sender: usenet@cps3xx.UUCP
Lines: 21

From article <646@chyde.uwasa.fi>, by ts@chyde.uwasa.fi (Timo Salmi LASK):
>>The problem is that procomm v. 2.4.3 can't find the dialing directory
>>or run command.com when I try to use the DOS gateway.  I recently
>>deleted some lines from my autoexec.bat and don't remember what I
>>had changed.  I'm not sure if that is the problem, but procomm has
>>always worked fine for me (6 months) until today.
> 
> 1) Procomm 2.4.2 and 2.4.3 tend to become corrupted under certain
> undefinable circumstances.  I suggest that you set up a *completely*
> fresh copy from you originals. 

I tried that already and it did not work.  I had found the problem.
If you are curious, please see me previous posting:

 Redirect > nul affects procomm, why?



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