russell@spdcc.COM (Tim Russell) (08/14/90)
Someone recently said that Windows 3.0 and the 16550 UART aren't
compatible.. Is this true? I had been planning to put a 16550 in my
2meg machine, because it drops characters while downloading in the
background on my 386 when it starts paging. I was hoping a 16550 would
be the answer.. Is it still?
--
Tim Russell Person at large russell@ursa-major.spdcc.com
"The opera ain't over till the last heterosexual falls asleep!"ghenniga@nmsu.edu (Gary Hennigan) (08/15/90)
I have a related problem with Win 3.0 and Qmodem. If I invoke Qmodem from the DOS level it finds my 16550 UART with no problem, howver if I run it as a non-windows app, fullscreen in windows it can't find it and only detects a 16450 UART, at least I think that's the number. Anyway it doesn't find the 16550. Anyone have any ideas? Also a person wrote to me via email some time ago about helping me with another Windows/Qmodem problem. Unfortunately, during my temporary insanity while taking my orals, I erased my mail file and have no way to again get in contact with this person. The only thing I remember was that he had a nickname of "Wolfman" so if you're reading this please send me mail again. Thanks, -- Gary Hennigan +---------------------------------------------------------------------------+ + e-mail: ghenniga@NMSU.Edu, henninsf@maxwel.NMSU.Edu + + Department of Electrical Engineering, Grad Student + + Physical Science Laboratory (ASS)istant systems programmer + +---------------------------------------------------------------------------+
mussar@bcars53.uucp (G. Mussar) (08/15/90)
I've tried the 16550 in 386 enh. mode and I am sad to say that it is true. Win3 virtualizes access to the comm hardware and it only virtualizes the interface for a 16450, so... apps under Win3 cannot play with the FIFO bits of the 16550. I also tried turning the FIFO on before invoking Win3. This caused Win3 to crash or not recognize the serial chip at all. Adding this support to the comm driver would be fairly trivial, however, you need the SDK, DDK and MSC (total about $1000-1500). Sigh. -- ------------------------------------------------------------------------------- Gary Mussar |Bitnet: mussar@bnr.ca | Phone: (613) 763-4937 BNR Ltd. | UUCP: ..uunet!bnrgate!bcars53!mussar | FAX: (613) 763-2626
kleonard@gvlv1.gvl.unisys.com (Ken Leonard) (08/15/90)
In article <1990Aug14.203320.5962@bigsur.uucp> mussar@bcars53.uucp (G. Mussar) writes:
* I've tried the 16550 in 386 enh. mode and I am sad to say [won't work]
* Win3 virtualizes ...
* interface for a 16450, so... apps under Win3 cannot play with the FIFO bits
* of the 16550.
---
SHEESH! Just when I thought I knew what was happening!
---
What's a 16_4_50?! What's the difference between 16450 and 16550?
Is FIFO the only difference?
---
_IS_ there a good solution for really high-rate (background) comm under WIN3?
----------------
regardz,
Kenmussar@bcars53.uucp (G. Mussar) (08/16/90)
The 16550 has 16 char FIFOs for receive and transmit. The 16450 has smaller FIFOs (if any). The 16450 is supposed to be reasonalbly compatable with the 8250. Perhaps some hardware expert would care to fill in all the gory details of 8250 vs 16450 vs 16550. -- ------------------------------------------------------------------------------- Gary Mussar |Bitnet: mussar@bnr.ca | Phone: (613) 763-4937 BNR Ltd. | UUCP: ..uunet!bnrgate!bcars53!mussar | FAX: (613) 763-2626