Don Guy wrote in a message to David Calafrancesco:
 DG> I get different results when trying com2 vs. com4 (COM2
 DG> exists in my system, COM4 doesn't).
 DG> Switching Telix's port to COM2 returns an immediate message
 DG> of "Can't initialize COM2"; trying COM4 hangs the session.
 DG> I've double and triple checked the virtual port addresses
 DG> and IRQs against Telix's settings, and also verified that
 DG> Telix's session has access to COM2/4. Argh. This is a
 DG> mystery.
OK... Telix is breaking all the rules and going direct to the hardware. I 
don't hold much hope for you ever solving this for telix. 
 #DC#> Also, will telix use a fossil driver?
 DG> 'fraid not.
Bummer...
 #DC#> Also, can telix see com1 and use it correctly?
 DG> Yep.
Of course, it is a standard port on a standard IRQ and as such has no 
problems being addressed directly. 
Dave Calafrancesco, Team OS/2
dave@drakkar.mhv.net
... They got the library at Alexandria, they're not getting mine! 
--- 
---------------