Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!purdue!mentor.cc.purdue.edu!sks
From: sks@mentor.cc.purdue.edu (Dan Schikore)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Killing the 4DOS beep
Message-ID: <8842@mentor.cc.purdue.edu>
Date: 26 Mar 90 02:41:14 GMT
References: <11912@xanth.cs.odu.edu> <4014@nmtsun.nmt.edu>
Reply-To: sks@mentor.cc.purdue.edu (Dan Schikore)
Distribution: usa
Organization: Purdue University
Lines: 18

In article <4014@nmtsun.nmt.edu> jrwsnsr@nmtsun.nmt.edu (Jonathan R. Watts) writes:
>In article <11912@xanth.cs.odu.edu>, hall@cs.odu.edu (Randolph Ted Hall) writes:
>> [text deleted on how to kill beeps]
>
>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.

In the case of 4dos it did work for me.  There were only two cases of that
pattern in the files 4dos88 and 4dos286, and they were the two beeps, and
now I don't have that problem.  For those who asked why don't I just register,
I would like to point out that I did state I had just installed it, so I
am still trying it out, as I am allowed to, but I still don't like the beeps.

Dan Schikore
sks@mentor.cc.purdue.edu