X-Originating-Host:	195.154.148.69
Organization:	http://www.remarq.com: The World's Usenet/Discussions Start Here
Subject:	Re: Q: Serial port communication / Hardware interrupts
Lines:	25
From:	Clemens Valens <c DOT valensNOc DOT SPAM AT mindless DOT com DOT invalid>
Newsgroups:	comp.os.msdos.djgpp
Message-ID:	<05a199b0.8ff676f0@usw-ex0102-016.remarq.com>
References:	<slrn8fuho1 DOT hn DOT drososa AT localhost DOT localdomain> <38FF5622 DOT 33D06B98 AT mtu-net DOT ru>
Bytes:	1080
X-Wren-Trace:	eHVQeHlgJ20mNi9rcTlxcnRGaHl+dTlmY2o0dXNsLGQjJnslLmEuKi0sPyYi
Date:	Fri, 21 Apr 2000 00:45:57 -0700
NNTP-Posting-Host:	10.0.2.16
X-Complaints-To:	wrenabuse AT remarq DOT com
X-Trace:	WReNphoon3 956303768 10.0.2.16 (Fri, 21 Apr 2000 00:56:08 PDT)
NNTP-Posting-Date:	Fri, 21 Apr 2000 00:56:08 PDT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I have some experience with interrupt driven serial I/O using
DJGPP for DOS applications and I never loose characters. I tried
some of the libraries available on the net and finally wrote my
own, based on the interrupt stuff in Allegro.

I must disagree with the previous poster on his opinion on
interrupt driven serial communication, I think that for most
cases it is the only real solution.

What is the baudrate you are looking for?

If you want to create a windows app, try your luck in the
Windows VxD newsgroup. I have seen many postings there from
people writing this kind of drivers.

Finally, where I work we have an old app written for DOS in
Borland PASCAL using a lot of interrupt driven serial
communication and it has always worked flawlessly in a DOS box.
It even seems that the DOS support in Windows 2000 has been
improved. So if everything else fails, you can always try that.

Clemens

* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!

- Raw text -