Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!tut.cis.ohio-state.edu!unmvax!nmtsun!jrwsnsr
From: jrwsnsr@nmtsun.nmt.edu (Jonathan R. Watts)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Killing the 4DOS beep
Message-ID: <4014@nmtsun.nmt.edu>
Date: 26 Mar 90 00:52:35 GMT
References: <11912@xanth.cs.odu.edu>
Distribution: usa
Organization: New Mexico Tech, Socorro NM
Lines: 20

In article <11912@xanth.cs.odu.edu>, hall@cs.odu.edu (Randolph Ted Hall) writes:
> 1. Search 4DOS286.EXE for E6 61. (with something like PC-Tools)
> 2. replace E6 61 with 90 90.
> 3. find next occourance of E6 61 and replace it with 90 90 also.
> 4. repeat steps 1-3 for 4DOS88.EXE.
> 
> Since this is the machine code command to turn on the speaker, you
> could effectivly search any program that makes noise and replace
> these bytes to silence it.

This sounds like a VERY BAD idea to me, as you can't guarantee that every
occurance of E6 61 is actually the code to turn on the speaker; it could be
data, or the E6 could be the tail end of one command and the 61 the beginning
of another (I don't know if 61 is an actual op code or not)!  I suggest
extreme caution in applying this trick.

 
  - Jonathan Watts
 
jrwsnsr@jupiter.nmt.edu (Internet address)