Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!sun-barr!newstop!male!jethro!exodus!appserv!sun!amdcad!brahms!indra
From: indra@brahms.amd.com (Indra Singhal)
Newsgroups: comp.windows.ms
Subject: Re: Windows communications packages that work?
Message-ID: <1991Apr25.073316.13837@amd.com>
Date: 25 Apr 91 07:33:16 GMT
References: <1991Apr11.154433.22879@javelin.sim.es.com>
Sender: usenet@amd.com (NNTP Posting)
Organization: Advanced Micro Devices, Inc.
Lines: 23

lwallace@javelin.sim.es.com (Raptor) writes:

>See title.  I'm talking about the problem with lost characters.  Procomm for
>DOS certainly doesn't work, and I've seen the same problem with the SDK's
>TTY sample application.

>Is there a standard technique for fixing this problem (as in, a Windows 
>configuration)?  (Hope it's not in the FAQ...  It should be if it exists.)

You must be running on a 286 based machine. For the longest time I sufffered
with this problem. Now that I have upgraded to an AM386-33 I no longer have
the problem.

There is a company in Berkeley, CA that has written a comm.drv replacement for
windows that fixes the problem and uses the FIFO on the 16550 if you have one.
Sorry, I don't remember the name of the company. If you do not receive followup
to this posting with the information, let me know and I will try to dig up
the information.

--
iNDRA | indra@amd.com or {ames apple uunet}!amd!indra
      | (Indra Singhal) (408) 749-5445; Advanced Micro Devices
      | MS 167; Box 3453; 901, Thompson Pl., Sunnyvale, CA 94088