Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!uxc.cso.uiuc.edu!tank!uwvax!astroatc!nicmad!madnix!schaut
From: schaut@madnix.UUCP (Rick Schaut)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Procomm HELP!
Message-ID: <714@madnix.UUCP>
Date: 19 Jul 89 03:08:26 GMT
References: <3816@cps3xx.UUCP>
Reply-To: schaut@madnix.UUCP (Rick Schaut)
Organization: ARP Software, Madison, WI
Lines: 21

In article <3816@cps3xx.UUCP> gcook@cps3xx.UUCP (Greg Cook) writes:
>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.
>

You probably deleted a line that said something like:

set PROCOMM=[the directory where Procomm's files are located].

If you re-insert the line with the appropriate directory (minus the
'[' and ']'), Procomm should be able to find it's files.  Remember,
that the path to Procomm's files must end with a '\' character.

-- 
   Richard Schaut     Madison, WI              Madison: an alternative
ArpaNet: madnix!schaut@cs.wisc.edu                      to reality.
UseNet: ...uwvax!astroatc!nicmad!madnix!schaut
             {decvax!att}!