Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!sdd.hp.com!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!fauern!lan!rommel
From: rommel@lan.informatik.tu-muenchen.dbp.de (Kai-Uwe Rommel)
Newsgroups: comp.windows.ms
Subject: Re: Dropped characters in Win. Comm programs at 19200 baud
Message-ID: <6076@tuminfo1.lan.informatik.tu-muenchen.dbp.de>
Date: 14 Dec 90 14:55:04 GMT
References: <1990Dec13.062051.3478@amd.com>
Sender: news@lan.informatik.tu-muenchen.dbp.de
Reply-To: rommel@lan.informatik.tu-muenchen.dbp.de (Kai-Uwe Rommel)
Organization: Inst. fuer Informatik, TU Muenchen, Germany
Lines: 21

In article <1990Dec13.062051.3478@amd.com> indra@brahms.amd.com (Indra Singhal) writes:
>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

--
/* Kai Uwe Rommel, Munich ----- rommel@lan.informatik.tu-muenchen.dbp.de */

DOS ... is still a real mode only non-reentrant interrupt
handler, and always will be.                -Russell Williams (MS)