Hi All,

I am going to develop an application based on layered service
provider (LSP) sample provided by MSFT. Before that, i decided to run
a few tests on the sample framework. I took this sample from the
Platform SDK i downloaded a month ago. Without making any change in
the code at all, I compiled both the registrant and the dll using
Visual Studio .Net2003.

Everything went well as far as the compilation is concerned. The next
thing i did was i fired up two virtual machines (using virtual PC).
One was Windows 2000 Advanced Server SP4 and the other was XP 2002
Base. I installed the LSP on XP (with success) and started the telnet
sever to quickly check if things are working ok after the installation
but it turned out that telnet server refused to start (errors
mentioned below). I uninstalled the LSP and then tried to start the
telnet server and it started successfully without a hitch. I tried the
same on Win 2000 but the error is the same.

The error displayed (in a dialog) says that:

If you're talking about this sample:
ftp://ftp.microsoft.com/bussys/Winsock/Winsock2/layered.zip then it works
just fine. Recently, there were a feedback about this problem on
microsoft.public.win32.programmer.networks NG:

fixed it. it was the path to the dll when installing the LSP. I had to
specify the full path.

"Cosmin" wrote:

<<

--
V.
This posting is provided "AS IS" with no warranties, and confers no
rights.
yahoo.com> wrote in message
news:ab69658f-9a91-4e70-8d5c-6d5e835742cf@e6g2000prf.googlegroups.com...

Volodymyr,

Thank you so much for your response. I havent been able to go into the
source code yet to tell the differences between PSDK code and code
from ftp url but the number of LSP files from both sources are not
the same. I am assuming that PSDK code is the latest since the sdk is
latest and PSDK code (which i am trying to use) is a V.S .Net project
and the code from the ftp url is not. Dont you think that it is better
to use the sample provided by PSDK since it is the latest, most up-to-
date and could have bug fixes?

I am still having the same issues with PSDK LSP. No success so far.

Thanks again,
sarshah.

On Feb 15, 2:51 pm, "Volodymyr M. Shcherbyna"
online.mvps.org> wrote:

Also, you might need to restart your computer _after_ you install the
LSP.

Viv

On Fri, 15 Feb 2008 10:51:28 +0100, "Volodymyr M. Shcherbyna"
online.mvps.org> wrote :

Have you tried the LSP on actual machines as opposed to virtual ones?

This is not a hardware-level or timing-sensitive code, so, if it fails on a VM,
this is a strong direction that there is a bug in it.

So, I would not spend time trying the buggy code on a real machine, but would
debug it, ensure it works on the VM, and then try on real machine.

Many experienced Windows kernel module writers do the initial testing
(debugging) on a VM. Only after the thing runs OK on the VM, the final testing
(validation) is performed on actual machine (the more CPU cores, the better).

As about the initial issue - for me, this is an installation issue (check the
registry), or the DLL dependency issue (debug C runtime library, MSVC8 vs
MSVCRT or such). I would first look at these possibilities.

Adding DbgPrints to the DLL and listening to them using WinDbg/KD attached to a
VM is also a good idea. Maybe the LSP DLL does not load at all.