brown@nicmad.UUCP (Mr. Video) (05/12/87)
Well, I tried to patch my copy of PC-DOS 3.30 and managed to make it crash. It is different enough that one of the two mods for turning off echo doesn't work. It so happens to be the one for the autoexec.bat handling. Anyway, here are two of the mods: Regular batch file echo off: DEBUG COMMAND.COM -E 1D68 xxxx:1D68 01.00<CR> -W<CR> -Q<CR> Blank lines from echo: (ECHO followed by two blank spaces) DEBUG COMMAND.COM -E 3F29 xxxx:3F29 E8.83 20.F9 00.02 74.72<CR> -W<CR> -Q<CR> I have not verified that the echo blanks work. The code matched, so I changed it and COMMAND.COM didn't lock up. I hope this helps somebody out. -- harvard-\ ihnp4--\ Mr. Video seismo!uwvax.......!nicmad!brown (How I hate 4 line .sigs!) rutgers-/ decvax--/ terminus-/
davidsen@steinmetz.steinmetz.UUCP (William E. Davidsen Jr) (05/14/87)
In article <1658@nicmad.UUCP> brown@nicmad.UUCP (Mr. Video) writes: > >Well, I tried to patch my copy of PC-DOS 3.30 and managed to make it crash. > >It is different enough that one of the two mods for turning off echo doesn't >work. It so happens to be the one for the autoexec.bat handling. Why would you ever want to do that? DOS3.3 has a way to disable echo selectively in the batch file. Why mess with patches? Any line starting with @ is not echoed. Thus, if the first line is @ECHO OFF, nothing echos. As for blank echos, if you put a dot after the echo command (and nothing else) it just gives you a blank line (as: "echo."). That's been in every version since 2.0! I hate patching the system, and try to use existing features when possible. I hate to admit it, but IBM listened on this one. -- bill davidsen sixhub \ ARPA: wedu@ge-crd.arpa ihnp4!seismo!rochester!steinmetz -> crdos1!davidsen chinet / "Stupidity, like virtue, is its own reward"
nather@ut-sally.UUCP (05/16/87)
In article <5986@steinmetz.steinmetz.UUCP>, davidsen@steinmetz.steinmetz.UUCP (William E. Davidsen Jr) writes: > As for blank echos, if you put a dot > after the echo command (and nothing else) it just gives you a blank > line (as: "echo."). That's been in every version since 2.0! Has it, now! I've been collecting DOS patches for over 2 years, and this is the first time I've seen this one. (It works ... I just tried it). Aint Microsoft documentation just wunnerful? -- Ed Nather Astronomy Dept, U of Texas @ Austin {allegra,ihnp4}!{noao,ut-sally}!utastro!nather nather@astro.AS.UTEXAS.EDU
brown@nicmad.UUCP (Mr. Video) (05/18/87)
In article <5986@steinmetz.steinmetz.UUCP> davidsen@kbsvax.steinmetz.UUCP (William E. Davidsen Jr) writes: <In article <1658@nicmad.UUCP> brown@nicmad.UUCP (Mr. Video) writes: <> <>Well, I tried to patch my copy of PC-DOS 3.30 and managed to make it crash. <> <>It is different enough that one of the two mods for turning off echo doesn't <>work. It so happens to be the one for the autoexec.bat handling. < <Why would you ever want to do that? DOS3.3 has a way to disable echo <selectively in the batch file. Why mess with patches? < <Any line starting with @ is not echoed. Thus, if the first line <is @ECHO OFF, nothing echos. As for blank echos, if you put a dot <after the echo command (and nothing else) it just gives you a blank <line (as: "echo."). That's been in every version since 2.0! < <I hate patching the system, and try to use existing features when possible. <I hate to admit it, but IBM listened on this one. True, very true. But, what if you had LOTS of batch files out there and you didn't want to go and edit all of them so that the @ is used to suspend output of certain lines. By patching PC-DOS 3.30, you only play with one file and all the rest won't have to be touched. -- harvard-\ ihnp4--\ Mr. Video seismo!uwvax.......!nicmad!brown rutgers-/ decvax--/ terminus-/