Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!amdahl!dlb!plx!slvblc!dick
From: dick@slvblc.UUCP (Dick Flanagan)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Joy of MSDOS
Message-ID: <1193@slvblc.UUCP>
Date: 18 Mar 88 19:42:40 GMT
References: <3aee6925.44e6@apollo.uucp> <9429@sunybcs.UUCP>
Sender: uupc@slvblc.UUCP
Reply-To: slvblc!dick@ucscc.UCSC.EDU (Dick Flanagan)
Organization: SLV Systems Group, Ben Lomond, California
Lines: 36
Summary: DOS 3.3 solves both problems
Disclaimer: none


In article <9429@sunybcs.UUCP> ugfailau@sunybcs.uucp (Fai Lau) writes:
> In article <3aee6925.44e6@apollo.uucp> nelson_p@apollo.uucp writes:
> >
> >  Is there any way to create batch files that don't echo 
> >  their contents to the screen?  If I precede the other 
> >  commands in the .BAT file with 'ECHO OFF' then the @#&%*!
> >  'ECHO OFF' gets echoed!   
> > 
> 	Hey, anyone who knows the answer to this gives me a response too,
> will ya? Thanx
> 
> >  Why does the PATH command only apply to some kinds of files
> >  and not others?   If you're going to have a 'where to look'
> >  feature for the computer why limit the types of files it 
> >  applies to? 
> 
> 	Hummmm, Dos 3.20 has been good to me in that it does look
> through the whold path for a file to be executed. One thing though,
> when an executable looks for a "slave" file (like an overlay),
> it doesn't even know that the path exists!!!

I have seen patches to IBM's PC-DOS 3.2 that solves the first problem by
making ECHO OFF the default for batch files (No, I don't have a copy of
it, sorry!  Check with your neighborhood BBS.).

There are also several "dpath" (data path) utilities available from
various BBS's that solve the second problem.

DOS 3.3 solves *both* problems.

Dick

--
Dick Flanagan, W6OLD                         GEnie: FLANAGAN
UUCP: ...!ucbvax!ucscc!slvblc!dick           Voice: +1 408 336 3481
Internet: slvblc!dick@ucscc.UCSC.EDU         LORAN: N037 04.7 W122 04.6
USPO: PO Box 155, Ben Lomond, CA 95005