home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!doc.ic.ac.uk!agate!usenet.ins.cwru.edu!magnus.acs.ohio-state.edu!shim
- From: shim@magnus.acs.ohio-state.edu (Sam Shim)
- Newsgroups: comp.dcom.modems
- Subject: UARTS / simulated UARTS / Intel SatisFAXtion 400 modems
- Message-ID: <1992Nov15.162222.1041@magnus.acs.ohio-state.edu>
- Date: 15 Nov 92 16:22:22 GMT
- Sender: news@magnus.acs.ohio-state.edu
- Organization: The Ohio State University
- Lines: 34
- Nntp-Posting-Host: magnusug.magnus.acs.ohio-state.edu
-
-
- There's been an interesting discussion on the value of the 16550AFN
- UART, so I'd like to add my bit of wisdom to this discussion.
-
- First, the 16550AFN has a 16 byte buffer, not a 16 bit buffer and not
- a 16 kilobyte buffer. I think not everyone is clear on that.
-
- Although I consider the 16550AFN to be much better than a 16450 and
- its clones, I don't consider it a "cure-all" UART chip. Running Desqview,
- I still experience quite a bit of dropped characters with the 16550AFN.
- The only piece of hardware that I have found that does not under any
- conditions overflow the UART is the Intel SatisFAXtion 400 modem.
- It's smart buffering capabilities truly work well. The 16550AFN, which
- you might consider to be 16 times better than a 16450, pales in
- comparison to the Intel S400 simulated UART. So if you are looking
- for a 14.4K or 9600 modem and worried about dropped characters due
- to the transmission speed, I would recommend the Intel SatisFAXtion
- 400 modem. But keep in mind of it's limitations. It's an internal
- modem, so you won't have the blinking lights, and it's designed for
- DOS/Windows and OS/2 use only. Unless you feel like hacking away, don't
- expect it to work with other operating systems. With DOS, the modem
- software is downloaded the to modem at boot up time, which takes a second
- or two, but allows for easy upgrades. The latest revisions are no more
- than a telephone call and a download away, and there's no need for ROM
- swaps.
-
- And for those of you running Windows in 386 enhanced mode, Windows
- automatically buffers the COM ports. It defaults to 128 characters.
- But if you want to be safe, you might want to up that a little, to
- around 512 bytes or 1K, with the possibility of a slight performance
- loss. It's controlled by the 'COMxBuffer' in the '[386enh]' section
- of the Window's system.ini file.
-
- -Sam-
-