WIndows es 16550
- To: email@example.com
- Subject: WIndows es 16550
- From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
- Date: Wed, 22 Jan 92 14:30:15 EST
In answer to my earlier question about a friend who had a problem
with recognition of the 16550. It WAS because he was running under
MS windows. Windows apparently masks the 16550. Possibly the 'f'
option supplied by wg7j in his latest code could be used. Not sure
though if it would still use the 16550 features or intercept the real
hardware and present an 8250 to the user. Probably if you used a
non-standard comm address (other than 1-4) it (windows) would leave
We have a windows 3.1 official beta tester here. I should pass onto
him the 16550 problem. If anyone has anymore details pass them to me.