Path: utzoo!utgpu!attcan!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!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: <700@dogie.edu> Date: 21 Sep 88 20:35:17 GMT Sender: news@dogie.edu Distribution: na Organization: University of Wisconsin Academic Computing Center Lines: 20 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. Ah, if you do set procomm=c:\comm\ to define the enviornment variable procomm (and note well the trailing backslash!), you can invoke procomm from anywhere and it will know where to find its parameter, command, and other files. Of course you put whatever path *you* keep the stuff in. Oops -- also need to declare that directory in the PATH as well. ==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===============