From: "Peter Remmers" Newsgroups: comp.os.msdos.djgpp Subject: Re: Async COM managing Date: Sat, 6 Jan 2001 09:42:32 +0100 Organization: T-Online Lines: 26 Message-ID: <936lkf$7mj$01$1@news.t-online.com> References: <9250eb$a84$00$1 AT news DOT t-online DOT com> <557-Fri05Jan2001203419+0200-eliz AT is DOT elta DOT co DOT il> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: news.t-online.com 978770383 01 7891 b7YjC7SSYYBPO 010106 08:39:43 X-Complaints-To: abuse AT t-online DOT com X-Sender: 320094726121-0001 AT t-dialin DOT net X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii schrieb... > > I wonder if it would be possible > > to write a library that would allow you to call the Windows functions > > to access the COM ports > > It's possible, but someone needs to crack down the backdoor into the > Windows VxD which controls the COM port, in the same manner as they > did with Winsock. I think it's not even too hard, since it's documented in the Win98 DDK. Windows 98 DDK Related Driver Documentation Windows 95 Documentation Design Guide Virtual Communications Device Drivers Virtual Communications Driver Protected-Mode Application Programming Interface Peter