Hi bret,


On Sun, 4 Feb 2024, Bret Johnson wrote:


I looked up a little bit about DECtalk.  It looks like the earlier versions 
used a serial port but the later versions plugged directly into an ISA slot.  I 
assume you have one of the later versions?  I can't imagine how one that works 
with a serial port would have a hardware compatibility issue.

Hi Bret,
Actually you have that information in the wrong order.
Portable synthesizers that used serial ports, the dectalk Express
for example came after the internal cards.
The Isa slot edition, the one I have installed now was followed
by a PCI <hope that is correct> slot edition.  Serial port
options, the above referenced express, my reading edge, those
were next.  There is actually currently a Dectalk USB synthesizer
as well.

Anyway, below is the exact information on the CD rom conflict.
There is a utility that shifts the i/a address dectalk uses, but
it does not fix the driver problem.
Here is what the documentation says:


     Conflict with DECtalk and EIDE CD-ROM Drivers.

We have found that the DECtalk hardware will not work with PCs
that have certain EIDE CDROMs intalled.

Some of the CDROMs are manufactured by ACER and Mitsumi and one
of the driver names in CONFIG.SYS is VIDE_CDD.

The problem apparently is caused by the DECtalk and CDROM drivers
trying to use the same software interrupt (different than
hardware IRQs).

Thanks for your ideas,

Karen

Hardware compatibility issues are usually either with Interrupt (IRQ) or I/O 
port conflicts, but IDE/ATAPI was such a widespread standard that it's hard to 
imagine how DECtalk would have a conflict with those.

Does the information you've found give any indication as to what the conflict 
might actually be?

--
Bret Johnson
It's oft been said that the Devil is in the Details.  I disagree completely.  I 
say God is in the Details -- the Devil is in the Fluff.



_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to