delorie.com/archives/browse.cgi | search |
Date: | Fri, 21 Apr 2000 03:44:55 -0400 (EDT) |
Message-Id: | <200004210744.DAA16989@indy.delorie.com> |
From: | Eli Zaretskii <eliz AT delorie DOT com> |
To: | "Alexei A. Frounze" <alex DOT fru AT mtu-net DOT ru> |
CC: | djgpp AT delorie DOT com |
In-reply-to: | <38FF5622.33D06B98@mtu-net.ru> (alex.fru@mtu-net.ru) |
Subject: | Re: Q: Serial port communication / Hardware interrupts |
References: | <slrn8fuho1 DOT hn DOT drososa AT localhost DOT localdomain> <38FF5622 DOT 33D06B98 AT mtu-net DOT ru> |
Reply-To: | djgpp AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> From: "Alexei A. Frounze" <alex DOT fru AT mtu-net DOT ru> > Newsgroups: comp.os.msdos.djgpp > Date: Thu, 20 Apr 2000 23:10:26 +0400 > > 4th, interrupt driven serial I/O is not good also. I have no luck with it. It > really works, but again characters are lost... You can't rely on it too. FWIW, I once wrote an interrupt-driven serial library, and it worked well (on plain DOS, never tried it on Windows), up to the maximum rate of 115K baud, never losing a single character.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |