home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.modems
- Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!zaphod.mps.ohio-state.edu!malgudi.oar.net!news.uakron.edu!neoucom.edu!wtm
- From: wtm@uhura.neoucom.edu (Bill Mayhew)
- Subject: Re: 16550 vs. 16550AFN re: Windows
- Message-ID: <1992Aug26.003745.9009@uhura.neoucom.edu>
- Organization: Northeastern Ohio Universities College of Medicine
- References: <1992Aug22.060307.19838@qiclab.scn.rain.com> <3737@randvax.rand.org> <BtIDJ1.Ex2@animal.gcs.co.nz>
- Date: Wed, 26 Aug 1992 00:37:45 GMT
- Lines: 17
-
- In Windows, try setting ComBoostTime=5 in the system.ini file.
- This will allow the comm driver to linger up to 5 mS before
- returning from the interrupt routine. This makes it much less
- likely to lose characters. I believe the default time is only 1
- mS. Even if you have 16550 support (COMxFIFO=TRUE) enabled,
- increasing the ComBoostTime helps a lot. There is only a little
- degredation to background processes.
-
- Also, if possible, enable rts/cts flow control in your windows
- telecom application. Out of band flow handling doesn't have to
- ripple though the input buffer before being noticed.
-
-
- --
- Bill Mayhew NEOUCOM Computer Services Department
- Rootstown, OH 44272-9995 USA phone: 216-325-2511
- wtm@uhura.neoucom.edu (140.220.1.1)
-