From:	1berto AT my-deja DOT com
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Q: Serial port communication / Hardware interrupts
Date:	Sun, 23 Apr 2000 18:18:12 GMT
Organization:	Deja.com - Before you buy.
Lines:	40
Message-ID:	<8dveop$8ne$1@nnrp1.deja.com>
References:	<slrn8fuho1 DOT hn DOT drososa AT localhost DOT localdomain>
NNTP-Posting-Host:	204.176.172.10
X-Article-Creation-Date:	Sun Apr 23 18:18:12 2000 GMT
X-Http-User-Agent:	Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
X-Http-Proxy:	1.1 x42.deja.com:80 (Squid/1.1.22) for client 204.176.172.10
X-MyDeja-Info:	XMYDJUID1berto
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

You need a VxD under Windows 95/98 if you want reliable and fast
communication. Take a look at http://www.wcscnet.com/cdrvvbro.htm. It
is the fastest product on the market for serual com.


In article <slrn8fuho1 DOT hn DOT drososa AT localhost DOT localdomain>,
  drososa AT pat DOT forthnet DOT gr wrote:
> Hi
>
> I'm trying to interface with a hardware device though a serial port
and get
> something faster than win98 can offer. Looking over available
sources/info it
> seems that direct, interrupt based code can do the job. I already have
> tried a windows api based library code (slow) and wrote a polling
based
> version with djgpp (still too slow). The async library mentioned in
the faq
> seems to compile fine but generates a locking memory error when I try
it out
> booting into DOS mode from the windows shut down menu. I'm checking
out
> now some old 16-bit code and wondering if I should go that way or
persist
> with djgpp. What are people's experience? Are there any more
info/examples
> besides the User's Guide on hardware interrupts? (Does anyone have
that doc by
> Alaric "dark art of writing djgpp hardware interrupts" somewhere? It
is no
> longer available at the site mentioned in the UG).
>
> Any suggestions/recommendations welcome.
>
> TIA
>


Sent via Deja.com http://www.deja.com/
Before you buy.

- Raw text -