Date: Sat, 06 Jan 2001 14:59:50 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: "Peter Remmers" Message-Id: <6137-Sat06Jan2001145950+0200-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6 CC: djgpp AT delorie DOT com In-reply-to: <936lkf$7mj$01$1@news.t-online.com> (Peter.Remmers@t-online.de) Subject: Re: Async COM managing References: <9250eb$a84$00$1 AT news DOT t-online DOT com> <557-Fri05Jan2001203419+0200-eliz AT is DOT elta DOT co DOT il> <936lkf$7mj$01$1 AT news DOT t-online DOT com> 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 Precedence: bulk > From: "Peter Remmers" > Newsgroups: comp.os.msdos.djgpp > Date: Sat, 6 Jan 2001 09:42:32 +0100 > > 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 Are the values to put into registers documented there in enough detail to allow one to write a non-trivial code which uses the COM port? The problem with this interface is not how to access it---this is documented in RBIL---but what data structures to use, how to lay them out, and what values to use for some of the flags. If that is documented by Microsoft, then the problem is solved (but then I wonder how come it took such a long time for Rich Dawe and friends to find the way to make the Wsock2 interface work).