Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!sun!amdcad!brahms!indra
From: indra@brahms.amd.com (Indra Singhal)
Newsgroups: comp.windows.ms
Subject: Re: Dropped characters in Win. Comm programs at 19200 baud
Message-ID: <1990Dec17.180239.20713@amd.com>
Date: 17 Dec 90 18:02:39 GMT
References: <1990Dec13.062051.3478@amd.com> <6076@tuminfo1.lan.informatik.tu-muenchen.dbp.de>
Sender: usenet@amd.com (NNTP Posting)
Organization: Advanced Micro Devices, Inc.
Lines: 30

rommel@lan.informatik.tu-muenchen.dbp.de (Kai-Uwe Rommel) writes:

>Earlier I wrote:
>>I have used Terminal, WinQVT, UniCOM and Microphone II. They all drop
>>single characters randomly. Outside Windows, Qmodem 4.2b never drops any
>>characters.

>This is a problem of the COMM.DRV driver shipped with windows.

>>Have others seen such consistent bad behavior? Anyone worked it out?
>>Workarounds? Anyone?

>Wrote my own device driver (not a windows one, but a DOS TSR which is
>called via INT 2F by my appliation(s)).
>MS has to fix this.
>/* Kai Uwe Rommel, Munich ----- rommel@lan.informatik.tu-muenchen.dbp.de */

I am surprised I have not seen much discussion of such an obnoxious
deficiency in comm.drv with Windows. Perhaps, not too many people are
running at 19200. Does this problem show up at 9600? or 2400 baud?

Is there a replacement comm.drv for windows available? Is anyone from
Microsoft reading this? Does anyone have a definitive response on a real
solution? Howcome all the comm. program developers and the media is
quiet? Then again, perhaps not too many people use 19200 :-(

--
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