Problems with PASSTHRU

NTDEV
1

I’m trying to install the PASSTHRU sample in a Win2k Pro machine
(VMWare), with no success. I did this:

  • Compiled PASSTHRU using the “Windows 2000 free build environment”
  • Installed the passthru using Net Connection –> Add Service –>
    pointed the INFs (netsf.inf and netsf_im.inf). Windows copied the .sys
    to system32\drivers, but didn’t ask me about the driver signature.
  • Rebooted the machine with debug support. Attached Windbg and “bp
    passthru!DriverEntry”.

Windbg’s LM command doesn’t show the driver and the breakpoint is
never reached. Do I need to modify the INFs?

Strauss

2

On Mon, 2004-07-05 at 20:21, Rodrigo Strauss wrote:

I’m trying to install the PASSTHRU sample in a Win2k Pro machine
(VMWare), with no success. I did this:

  • Compiled PASSTHRU using the “Windows 2000 free build environment”

Which PassThru sample are you using? There was a bit in the 2k version
that required a notify object IIRC; you probably don’t want that. There
have been other bugfixes, so in general, I’d recommend the 2k3 DDK
sample.

Are you using 2000 as the target? Get a checked kernel and ndis and a
checked network class installer. The class installer can be made to
generate a logfile - search the archives for the details. Also look at
setupapi.log, and maybe try a checked setupx.dll.

Make sure you try with unmodified INFs from the 2k3 DDK before you go
looking too far for trouble - a naked passthru.sys + infs from the DDK
should always install. If it doesn’t, I’d suspect the target. Is it
using the US/English version of the OS?

HTH.

-sd

3

I’m using the Win2k3 DDK version, and both the source code and the
INFs are unmodified. I don’t need a notification object now, since I
just want to debug the driver to see how NDIS IM drivers work.
I’m using a fresh installed Windows 2000 Pro, En/US, no SPs, in a
VMWare Machine. The driver installation works fine in my Windows XP Pro
En/US production machine.

The driver is copied to system32\drivers folder, and the service
“Passthru Driver” is listed in connection properties. Here is the
setupapi.log:

[2004/07/06 18:27:28 656.55]
Could not locate section “Passthru.ndi.Remove.Services” (or the section
is empty).
[2004/07/06 18:27:31 656.65 Driver Install]
Enumerating files C:\WINNT\inf*.inf
The file (C:\WINNT\inf\oem0.inf) is not digitally signed, ignoring
driver date.
Device install function: DIF_SELECTDEVICE.
Device install function: DIF_SELECTDEVICE.
Enumerating files c:\documents and settings\noone\desktop\i386*.inf
The file (c:\documents and settings\noone\desktop\i386\netsf.inf) is not
digitally signed, ignoring driver date.
[2004/07/06 18:27:42 656.68 Driver Install]
Searching for hardware ID(s): ms_passthru
The file (c:\documents and settings\noone\desktop\i386\netsf.inf) is not
digitally signed, ignoring driver date.
Found ms_passthru in c:\documents and
settings\noone\desktop\i386\netsf.inf; Device: Passthru Driver; Driver:
Passthru Driver; Provider: Microsoft; Mfg: Microsoft; Section: Passthru.ndi
Decorated section name: Passthru.ndi
Selected driver installs from section Passthru.ndi in c:\documents and
settings\noone\desktop\i386\netsf.inf.
Changed class GUID of device to {4D36E974-E325-11CE-BFC1-08002BE10318}.
Set selected driver.
[2004/07/06 18:27:42 656.71]
An unsigned or incorrectly signed driver (c:\documents and
settings\noone\desktop\i386\netsf.inf) was installed for Network
Service. Error 0xe000022f: The third-party INF does not contain digital
signature information.
Copying file c:\documents and settings\noone\desktop\i386\passthru.sys
to C:\WINNT\System32\DRIVERS\passthru.sys.
An unsigned or incorrectly signed driver (c:\documents and
settings\noone\desktop\i386\netsf.inf) was installed for Network
Service. Error 0xe000022f: The third-party INF does not contain digital
signature information.

I installed the checked build before, but it’s toooo slow in VMWare.
I’ll just debug now, I don’t think I need a full checked windows. Can I
use just the ndis.sys checked or I do need to change the kernel and hal too?

Thanks in advance,

Strauss

Steve Dispensa wrote:

On Mon, 2004-07-05 at 20:21, Rodrigo Strauss wrote:

> I’m trying to install the PASSTHRU sample in a Win2k Pro machine
>(VMWare), with no success. I did this:
>
> - Compiled PASSTHRU using the “Windows 2000 free build environment”
>
>

Which PassThru sample are you using? There was a bit in the 2k version
that required a notify object IIRC; you probably don’t want that. There
have been other bugfixes, so in general, I’d recommend the 2k3 DDK
sample.

Are you using 2000 as the target? Get a checked kernel and ndis and a
checked network class installer. The class installer can be made to
generate a logfile - search the archives for the details. Also look at
setupapi.log, and maybe try a checked setupx.dll.

Make sure you try with unmodified INFs from the 2k3 DDK before you go
looking too far for trouble - a naked passthru.sys + infs from the DDK
should always install. If it doesn’t, I’d suspect the target. Is it
using the US/English version of the OS?

HTH.

-sd

Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@scua.com.br
To unsubscribe send a blank email to xxxxx@lists.osr.com

4

On Tue, 2004-07-06 at 21:04, Rodrigo Strauss wrote:

Here is the
setupapi.log:

It’s not signed, so those errors are expected.

I installed the checked build before, but it’s toooo slow in VMWare.
I’ll just debug now, I don’t think I need a full checked windows. Can I
use just the ndis.sys checked or I do need to change the kernel and hal too?

Yeah, you probably only want a checked kernel/hal, checked ndis, a
checked build of your driver, and a checked device installer and network
class installer for troubleshooting install/binding problems. This is
the setup I usually use (plus a checked tcpip.sys) to work on network
drivers.

-sd

5

I tried to install passthru in another Windows 2000 VM, in another
real machine, and the result was the same. I’ve installed service pack 4
and now everything works.

Thank you

Strauss

Steve Dispensa wrote:

On Tue, 2004-07-06 at 21:04, Rodrigo Strauss wrote:

>Here is the
>setupapi.log:
>
>

It’s not signed, so those errors are expected.

> I installed the checked build before, but it’s toooo slow in VMWare.
>I’ll just debug now, I don’t think I need a full checked windows. Can I
>use just the ndis.sys checked or I do need to change the kernel and hal too?
>
>

Yeah, you probably only want a checked kernel/hal, checked ndis, a
checked build of your driver, and a checked device installer and network
class installer for troubleshooting install/binding problems. This is
the setup I usually use (plus a checked tcpip.sys) to work on network
drivers.

-sd

Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@scua.com.br
To unsubscribe send a blank email to xxxxx@lists.osr.com

6

On Thu, 2004-07-08 at 20:05, Rodrigo Strauss wrote:

I tried to install passthru in another Windows 2000 VM, in another
real machine, and the result was the same. I’ve installed service pack 4
and now everything works.

How odd. Can anyone from Microsoft comment on IM-related changes in any
Win2k service packs? I don’t remember hearing about anything but maybe
my memory is off.

-sd