Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbosgd!gatech!seismo!ut-sally!nather
From: nather@ut-sally.UUCP (Ed Nather)
Newsgroups: net.micro
Subject: Re: Changing SWITCHAR in dos 3.x
Message-ID: <5085@ut-sally.UUCP>
Date: Fri, 6-Jun-86 12:47:25 EDT
Article-I.D.: ut-sally.5085
Posted: Fri Jun  6 12:47:25 1986
Date-Received: Sat, 7-Jun-86 14:15:22 EDT
References: <883@brl-smoke.ARPA> <12600005@gorgo.UUCP>
Organization: U. Texas CS Dept., Austin, Texas
Lines: 62
Summary: Huh?

In article <12600005@gorgo.UUCP>, ddrex@gorgo.UUCP writes:
> /* Written  9:47 am  May 23, 1986 by nather@ut-sally.UUCP in gorgo.UUCP:net.micro */
> In article <883@brl-smoke.ARPA>, bridger@RAND-UNIX.arpa writes:
> > This doesn't work for dos 3.1.  Is there another way to do it?
> 
> Yes.  Put the stuff between the two lines of dashes into a file
> called fixcom, then type the command
> 
>      debug command.com < fixcom
> 
> and lo! "echo off" is silent unless you insist on chatter.
> ----------------------------------------------------------------------
> e 105b 2
> ----------------------------------------------------------------------
> -- 
> Ed Nather
> 
> That had some rude side effects on my system (pcdos 3.1 on an XT clone).
> ECHO didn't, but ERRORLEVEL went away, too (always returned 0 after that
> hack), and CED forgot all about synonyms. Restoring the original command.com
> restored all those. I'd rather have dos chatter at me than put up with
> cpm-oid dumbness.

Oops.  Looks like quite a few characters were lost in that posting; it may
have come about because the "debug script" I included in the original article
had CR codes without LF codes following -- that's the way Debug insists its
input be formatted.

I've used the changed "command.com" on several IBM PC/XTs and a foreign
clone ("Standard Brand") with no side effects whatever.  Errorlevel works
fine.  I use "Keydo" instead of CED but no trouble there, either.  

Here's the complete change to type in by hand:

debug command.com
-e 105b 2
-e 1967 0
-w
-q

and here's the "debug script" I posted in the original article.  THEY SHOULD
BE THE SAME.  If they are not, best do it by hand (if you do it at all).  It
would be a pity if we can't post "debug scripts" to the net and have them
arrive whole ...

The command:

debug command.com < fixcom

The contents of the file "fixcom"  (remove dashed lines above & below)

----------------------------------------------------------------------
e 105b 2
e 1967 0
w
q
----------------------------------------------------------------------

Of course, the problem may be with the PC clone this was tried on ...

-- 
Ed Nather
Astronomy Dept, U of Texas @ Austin
{allegra,ihnp4}!{noao,ut-sally}!utastro!nather
nather@astro.AS.UTEXAS.EDU