🚀 go-pugleaf

From a previously posted note, courtesy of G. Seaburg, c/o keifer@uiucdcsp:

 
/* Written  2:56 pm  Jan 18, 1986 by nather@utastro.UUCP in uiucdcs:net.micro.pc */
/* ---------- "PC-DOS 3.1 and "echo off"" ---------- */
 
I am using a patched version of command.com for PC-DOS 2.1 that
sets the batch file interpreter to the "echo off" condition by default, and
it is great!  .bat files run silently, without screen chatter, as they
should.
 
For several reasons (none very good) I'd like to use PC-DOS 3.1, but not at
the expense of bat-chatter.  If anyone knows how to patch the 3.x command.com
so it runs .bat files silently, please send it to me, or post it to the net.
The patch for 2.x I am using does not work on 3.x (*sigh*).  I have a kludge
that erases the "echo off" which is echoed when the batch command "echo off"
is executed, but it is irritating after getting used to the real thing.
 
Thanks.
Ed Nather
Astronomy Dept, U of Texas @ Austin
{allegra,ihnp4}!{noao,ut-sally}!utastro!nather
nather@astro.UTEXAS.EDU
/* End of text from uiucdcs:net.micro.pc */
/* Written 12:51 pm  Jan 21, 1986 by connery@bnrmtv.UUCP in uiucdcs:net.micro.pc */
From Compuserve... the patch for echo off is as follows:
 
   debug COMMAND.COM
   -E 1967<cr>
   xxxx:1967  01.00<cr>
   -W<cr>
   -Q<cr>
 
Seems to work just perfectly--it doesn't have the bug some other patches
exhibit which disables the prompts during a nested COMMAND.COM session.
 
Glenn
/* End of text from uiucdcs:net.micro.pc */