Date: Sun, 2 Feb 1997 23:31:34 -0600 (CST)
From: "Colin W. Glenn" <cwg01 AT gnofn DOT org>
To: jdashiel AT eagle1 DOT eaglenet DOT com
cc: Jason White <whiteja AT rvib2 DOT rvib DOT org DOT au>, opendos AT mail DOT tacoma DOT net
Subject: Re: [opendos] Accessibility of OpenDOS with braille and speech output devices
In-Reply-To: <Pine.NXT.3.95.970202205149.21620A-100000@eagle1>
Message-ID: <Pine.GSO.3.95.970202232726.25807B-100000@sparkie.gnofn.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-opendos AT mail DOT tacoma DOT net
Precedence: bulk

On Sun, 2 Feb 1997 jdashiel AT eagle1 DOT eaglenet DOT com wrote:
> If an environment variable say vidspeed or videospeed could be used
<blip>
> What concerns me with both possible approaches is which one
> has the highest cost in code size.

How about doing a little twist like what many drivers do?  After all, when
you think about it, command.com is a device driver, it's the user
interface driver.  We should have the option to include a switch, say like
/fast, which loads a patch automatically over the section of code which
would normally call the bios.  That would give a 'default' command.com
which will be speech syn.. friendly, and give those driven for speed an
outlet to let the pedal down.