Path: utzoo!mnetor!uunet!husc6!tut.cis.ohio-state.edu!rutgers!sunybcs!boulder!murillo
From: murillo@sigi.Colorado.EDU (Rodrigo Murillo)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Echo Off!   Dammit!
Message-ID: <4965@sigi.Colorado.EDU>
Date: 21 Mar 88 15:34:05 GMT
References: <2110@phoenix.Princeton.EDU>
Reply-To: murillo@boulder.Colorado.EDU (Rodrigo Murillo)
Distribution: na
Organization: University of Colorado, Boulder
Lines: 17
Keywords: no hope

In article <2110@phoenix.Princeton.EDU> amlovell@phoenix.Princeton.EDU (Anthony M Lovell) writes:
>[examples of how impossible it is to avoid the ECHO OFF message from
> a batch file...]
>wholesale.  To pursue this further, echo off >nul as the first line of
>the batch file also will not work.  DOS really wanted to screw you over
>on this little flaw, and I think they succeeded.
 
I saw a patch posted a long time ago in PC Magazine that would patch
command.com so that the default was ECHO OFF.  Does anybody out there have that
patch,  or maybe someone would like to figure it out.  I used it on a system
once it it was great not to have to write batch files that always started
with 'ECHO OFF;CLS'.
-- 
_______________________________________________________________________________
 Rodrigo Murillo, University of Colorado - Boulder  (303) 761-0410 
 murillo@boulder.colorado.edu | ..{hao|nbires}!boulder!murillo
 ( Machines have less problems.  I'd like to be a machine. -- Andy Worhol )