From:	drososa AT pat DOT forthnet DOT gr (Tasos Drosopoulos)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Q: Serial port communication / Hardware interrupts
Date:	20 Apr 2000 18:04:11 GMT
Organization:	Hellenic Telecommunications & Telematics Applications Company FORTHnet S.A., Thetidos 6, GR-11528 Athens, Greece, Tel: +30 (1) 7295100, Fax: +30 (1) 7258520, url: http://www.forthnet.gr
Lines:	18
Message-ID:	<slrn8fuho1.hn.drososa@localhost.localdomain>
NNTP-Posting-Host:	ppp14.pat.forthnet.gr
X-Trace:	medousa.forthnet.gr 956253851 9206 194.219.229.114 (20 Apr 2000 18:04:11 GMT)
X-Complaints-To:	abuse AT forthnet DOT gr
NNTP-Posting-Date:	20 Apr 2000 18:04:11 GMT
User-Agent:	slrn/0.9.6.2 (Linux)
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

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

- Raw text -