dosgate/dosemu.

dosgate/dosemu.

[dave m mehler]

Hello,
	

On Sun, 19 Dec 1999 10:48:39 -0500 (EST) Nicolas Pitre <nico@cam.org>
writes:
> To use dosgate, start by making yourself a setup that works under
> straight DOS.  The synthesizer question depends on the screen reader
> package you want to use.
> 
	Ok, does this mean get the package working under regular, non-linux,
straight dos 6.22 or 7.0 and transfering it or using dosemu? If it means
the latter, I have a partial dos solution ready to go, but I'm running in
to a problem, and I know this has been commented on before on this list,
running jfd for example, with a synth, there is no to poor cursur
tracking at the commandline. This is not even factoring in dosgate yet,
this is just using dosemu, jfd, and a synth. Does anyone have a fix?
Thanks.
Dave.

___________________________________________________________________
Why pay more to get Web access?
Try Juno for FREE -- then it's just $9.95/month if you act NOW!
Get your free software today: http://dl.www.juno.com/dynoget/tagj.

Re: dosgate/dosemu.

[Enrico Zini]

On Sun, Dec 19, 1999 at 08:46:32PM -0500, dave m mehler wrote:

> 	Ok, does this mean get the package working under regular, non-linux,
> straight dos 6.22 or 7.0 and transfering it or using dosemu? If it means
> the latter, I have a partial dos solution ready to go, but I'm running in
> to a problem, and I know this has been commented on before on this list,
> running jfd for example, with a synth, there is no to poor cursur
> tracking at the commandline. This is not even factoring in dosgate yet,
> this is just using dosemu, jfd, and a synth. Does anyone have a fix?

The experimental setup script I wrote for dosgate expects a dos boot floppy
with a batch file called 'reader.bat' that starts up the screen reader.  It
then makes a disk image from the floppy and installs dosgate on it.

Unluckily, if there are problems with a dos screen reader under dosemu even
without dosgate, the only thing you can do is to tweak dosemu configuration,
like setting $_hogthreshold = (0) to improve responsiveness or similar things.

I would also be interested on mantaining a web page about how dos screen work
under dosemu, with suggestions on how to make them work or work better,
warnings about things that do not work and any other interesting comments.

dosemu authors could also be informed about this use of their work, so that
they could make dosemu run dos screen readers in the best possible way.


				Read you soon! Enrico

--
GPG public key available on finger -l zinie@cs.unibo.it

Re: dosgate/dosemu.

[Jacob Schmude]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anyone know how to get the internal doubletalk PC running under dosemu so
I can try this package out?



Jacob Schmude
MailTo:jacobs@ncinter.net
ICQ: 53401220
Email me for public gpg key.


On Mon, 20 Dec 1999, Enrico Zini wrote:

> On Sun, Dec 19, 1999 at 08:46:32PM -0500, dave m mehler wrote:
> 
> > 	Ok, does this mean get the package working under regular, non-linux,
> > straight dos 6.22 or 7.0 and transfering it or using dosemu? If it means
> > the latter, I have a partial dos solution ready to go, but I'm running in
> > to a problem, and I know this has been commented on before on this list,
> > running jfd for example, with a synth, there is no to poor cursur
> > tracking at the commandline. This is not even factoring in dosgate yet,
> > this is just using dosemu, jfd, and a synth. Does anyone have a fix?
> 
> The experimental setup script I wrote for dosgate expects a dos boot floppy
> with a batch file called 'reader.bat' that starts up the screen reader.  It
> then makes a disk image from the floppy and installs dosgate on it.
> 
> Unluckily, if there are problems with a dos screen reader under dosemu even
> without dosgate, the only thing you can do is to tweak dosemu configuration,
> like setting $_hogthreshold = (0) to improve responsiveness or similar things.
> 
> I would also be interested on mantaining a web page about how dos screen work
> under dosemu, with suggestions on how to make them work or work better,
> warnings about things that do not work and any other interesting comments.
> 
> dosemu authors could also be informed about this use of their work, so that
> they could make dosemu run dos screen readers in the best possible way.
> 
> 
> 				Read you soon! Enrico
> 
> --
> GPG public key available on finger -l zinie@cs.unibo.it
> 
> ---
> Send your message for blinux-list to blinux-list@redhat.com
> Blinux software archive at ftp://leb.net/pub/blinux
> Blinux web page at http://leb.net/blinux
> To unsubscribe send mail to blinux-list-request@redhat.com
> with subject line: unsubscribe
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: Made with pgp4pine

iD8DBQE4Xr6NGpdY0XMhJGQRAgtiAJ9IoloS2AeK9MpAZ9OvzTc56cRTHwCfabS7
gl7hwoD8yBhY6WoGOF4gQzk=
=tFg2
-----END PGP SIGNATURE-----

Re: dosgate/dosemu.

[Enrico Zini]

Hello!

I know nothing about DoubleTalk PC, but to get it running under dosemu you have
to get it running under dos.

As far as I can tell, any hardware for speech synthesis or braille display
comes with some sort of dos screen reader: you just have to get it running in a
dos boot floppy with a batch file named 'reader.bat' that makes it start.

This should be enough with many serial devices; in this case we are having a
hardware card, if I understand what the DoubleTalk is.  To make it work under
dosemu, you have to tell in dosemu configuration what hardware ports and
interrupts it should give access to dos programs.

You give access to interrupts with the $_irqpassing directive, setting it to a
space-separated list of interrupt numbers, as in:

	$_irqpassing = "1 4 6"

You give access to ports with the $_ports directive, setting it to a
space-separated list of ports and/or port ranges, as in:
	
	$_ports = "0x378 0x3e8 range 0x220,0x230"

A port range is indicated by the 'range' keyword followed by the two
comma-separated extremes of the range.

To know what hardware ports and interrupts your DoubleTalk is using, since I
guess you have it running under Linux, you can issue these commands:

	cat /proc/ioports
	cat /proc/interrupts

They list the io ports and interrupts currently in use by the kernel device
drivers, and you can look for what's used by the DoubleTalk driver.

As a personal note, I have to say that while trying to run Linux-supported
devices with dosgate is good for testing dosgate (and I thank you very much for
willing to do it), it's always best to take advantage of the native Linux
support one could have for its hardware.


Thank you for your interest! Enrico


> Anyone know how to get the internal doubletalk PC running under dosemu so
> I can try this package out?

--
GPG public key available on finger -l zinie@cs.unibo.it