Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!uwvax!dogie!anderson@vms.macc.wisc.edu From: anderson@vms.macc.wisc.edu (Jess Anderson, MACC) Newsgroups: comp.sys.ibm.pc Subject: Re: Procomm command files Message-ID: <701@dogie.edu> Date: 21 Sep 88 21:56:22 GMT Sender: news@dogie.edu Distribution: na Organization: University of Wisconsin Academic Computing Center Lines: 28 In article <700@dogie.edu>, anderson@vms.macc.wisc.edu (Jess Anderson, MACC) writes... ]In article <9316@cup.portal.com>, Vaprak@cup.portal.com writes... ] ]]when the connection is made, procomm will ]]look in the current directory for the cmd file. it must be in your ]]current directory and have the extender .CMD. ] Sorry to followup to my own article, but I certainly put it a clumsy way earlier. In the interest of greater clarity, here's the info again: Assuming you keep Procomm and all its parameter, command, and other work files in directory C:\COMM, you can call Procomm from any current drive and directory if you have that path in your environment (one usually does these declarations in autoexec.bat): path=.......;C:\COMM;....... set procomm=C:\COMM\ the first of which enables the shell to find PROCOMM.EXE at loading time, while the other enables Procomm to find its work files. ==Jess Anderson======(home:)========INTERNET: anderson@vms.macc.wisc.edu==== | 1210 W. Dayton 2838 Stevens UUCP: {harvard,rutgers,allegra,ucbvax} | | Madison, WI 53706 Madison 53705 !uwvax!vms3.macc.wisc.edu!anderson | ==608/263-6988=======608/238-4833===BITNET: anderson@wiscmacc===============