Re: Layered Service Provider incompatibilities
- From: "Arkady Frenkel" <arkadyf@xxxxxxxxxxxxxxxx>
- Date: Thu, 9 Feb 2006 10:37:29 +0200
Did you take it from last Server PSDK : that LSP included IFS and non-IFS
versions ?
Arkady
"Tom Yee" <thomas.yeeNOSPAM@xxxxxxxxx> wrote in message
news:5FBAD060-F425-4A60-9BF1-84DBB919C8CC@xxxxxxxxxxxxxxxx
My company has an application based on the example code in
Microsoft SDK\Samples\netds\WinSock\LSP
Our changes to the SDK code are primarily in how we communicate with the
primary application, i.e. via shared memory, and how we monitor/filter the
byte stream. In several years of deployment, no problems have been
reported
by any of our customers.
A customer now complains that our code is incompatible with another
application. Reversing the order of installation of our application and
the
other application does not cure the problem.
Is anybody aware of problems with the SDK example code, or what we might
possibly have done to damage it in adapting it to our purposes?
Tom
P.S. Please do not confuse the SDK example code with the "layered.exe"
example referred to in "Unraveling the Mysteries of Writing a Winsock 2
Layered Service Provider"
http://www.microsoft.com/msj/0599/LayeredService/LayeredService.aspx
.
- Prev by Date: use IOCTL_NDISUIO_SET_OID_VALUE return a error code 31?
- Next by Date: Re: NDISPROT working with SET OID
- Previous by thread: use IOCTL_NDISUIO_SET_OID_VALUE return a error code 31?
- Next by thread: Re: Layered Service Provider incompatibilities
- Index(es):
Relevant Pages
|
