Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site atux01.UUCP
Path: utzoo!linus!decvax!decwrl!amdcad!lll-crg!caip!atux01!perry
From: perry@atux01.UUCP (P. Kivolowitz)
Newsgroups: net.micro.amiga
Subject: Spoken Bell And Memory/Disk Space
Message-ID: <139@atux01.UUCP>
Date: Wed, 8-Jan-86 16:59:04 EST
Article-I.D.: atux01.139
Posted: Wed Jan  8 16:59:04 1986
Date-Received: Fri, 10-Jan-86 04:56:16 EST
References: <922@caip.RUTGERS.EDU>
Organization: CSEd, AT&T Communications, Piscataway, N.J.
Lines: 32

To the people putting spoken bells and the  like into their
terminal emulators  (and  putting  terminal  emulators into
their shells!):

At the root  of the  matter, it  is *neat* to have a spoken
bell in your terminal program.  But...to have just one word
spoken,  the  narrator  and  (depending on how you go about
things) the  translator  devices need to loaded into memory
(and of course) resident on disk.

Yeah the amiga  can  amazing  things,  but  for predestrian
work-horse applications like terminal  emulators you should 
always be aware of the cost  versus benifit of a particular
feature.

In the case of the spoken  bell,  DisplayBeep is already in
ROM (you know what I mean).

Ask your self the question: Is saying  Beep! worth the five
or ten kbytes of overhead  (in  addition to possibly inter-
fering with  other  programs doing sound at the same time).

To sum up: yeah it's  a neat  idea but  does it belong in a
product?


					Perry S. Kivolowitz

"I regret that I have but one Amiga to vie for!"
------------------------------------------------------------
JAUG MEETING JANUARY  24th  -  Hall 114 , Hill Ctr , Rutgers
New Brunswick. 7:30 p.m. Featured: Activision.