From: "Wojciech Galazka" <wojciech DOT galazka AT polkomtel DOT com DOT pl>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: vxd file system drivers and DPMI
Date: Sat, 2 Dec 2000 10:10:08 +0100
Organization: NASK - www.nask.pl
Lines: 16
Message-ID: <90aead$8tn$1@pippin.nask.waw.pl>
References: <3A281B86 DOT 19CFEB8A AT almaden DOT ibm DOT com>
NNTP-Posting-Host: plus32.polkomtel.com.pl
X-Trace: pippin.nask.waw.pl 975748237 9143 212.2.96.159 (2 Dec 2000 09:10:37 GMT)
X-Complaints-To: usenet AT nask DOT pl
NNTP-Posting-Date: Sat, 2 Dec 2000 09:10:37 +0000 (UTC)
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
X-Newsreader: Microsoft Outlook Express 4.72.3612.1700
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


Mark wqrote
<3A281B86 DOT 19CFEB8A AT almaden DOT ibm DOT com>...
>Hello,
[...]
Hello,

1 Did you check services provided by tcpip.vxd, wsock2,vxd and the like?
Check out libsocket sources for some hints
2 BTW to me it seems that you may consider redesigning your driver a bit,
perhaps split it into a user mode DLL and a vxd and communicate through
ioctls or asynchronous communication API