wew@naucse.UUCP (Bill Wilson) (08/15/88)
From article <3641@bsu-cs.UUCP>, by feg@clyde.UUCP (Forrest Gehrke): > [Origninally received via path ucscc!ucbvax!hplabs!ihnp4!clyde!feg from > Forrest Gehrke. > > Original message slightly edited and submission broken up into two > articles -- R.D.] > > Epath is much easier to use than the one posted to comp.sys.ibm.pc > called chgpath. Besides, chgpath doesn't work on the pc6300+. > I tried this program out and it doesn't have the same purpose and scope as chgpath. They are both for changing the path but appear to work in totally different ways. EPATH dis not work at all on my system. I use Norton's DOS Editor (a facility like NDOSEDIT) and it's use of the F3 key for allowing the editing of the path, did not work. I would suspect that this would be a problem on any DOS machine running a command line editor. CHGPATH was meant to be used in batch files so that a path element could be added or subtracted with ease. The program is a little unforgiving in certain areas (I must admit), I wrote it because I needed a facility with that type of function. If anyone would like the code, or if the writers of any facilities like this would care to exchange code I would be glad to. CHGPATH is written in Turbo C, tiny model and changed from EXE to BIN format. -- Bill Wilson (Bitnet: ucc2wew@nauvm) Northern AZ Univ Flagstaff, AZ 86011 {These views are mine and do not necessarily reflect those of my employer}