NDIS intermediate driver - imsamp problem

Hi everybody!

I’m writing this message after spending 2 whole
days on trying to operate the darn thing…

(I run WinNT workstation 4.0, SP5)

Well, her goes:

I built the ImSamp.sys file, with a few DbgPrint() calls
in certain places (e.g.: when entering the “send” function)
and tried the following 2 things:

  1. Installing it using the OEMSETUP file supplied by MS.
    After installing the imsamp file and pressing “OK”, I got
    a message from the TCP stack that the newly installed ADAPTER
    needs an IP address… needless to say that I gave it an
    IP address, and nothing happened (I did a reboot, and did not
    see any debug message)…

OK, I removed the device and tried:

  1. Following the instructions in the readme file.
    Nothing… The driver was loaded (I saw it “running”
    in control panel ->devices), but no debug messages were printed.

Can anybody help me? I’m new to intermediate drivers (although I
do understand NDIS and kernel drivers, like the packet.sys sample
of the DDK).

thank you ever so much,

  • Barak

Barak Mandelovich Mercury Interactive ltd.
xxxxx@conduct.com 19 Shabazi st.
Tel: +972 3 539 9286 Yehud, 56100
Fax: +972 3 533 1617 Israel

A few things you can check:

Did you install the debug build or release build?
What did you use to look for debug outputs?
Did you set the DebugLevel and DebugMask to the correct values in the
registry?

Jeffrey

-----Original Message-----
From: Barak Mandelovich [mailto:xxxxx@conduct.com]
Sent: Friday, April 07, 2000 11:29 AM
To: NT Developers Interest List
Subject: [ntdev] NDIS intermediate driver - imsamp problem

Hi everybody!

I’m writing this message after spending 2 whole
days on trying to operate the darn thing…

(I run WinNT workstation 4.0, SP5)

Well, her goes:

I built the ImSamp.sys file, with a few DbgPrint() calls
in certain places (e.g.: when entering the “send” function)
and tried the following 2 things:

  1. Installing it using the OEMSETUP file supplied by MS.
    After installing the imsamp file and pressing “OK”, I got
    a message from the TCP stack that the newly installed ADAPTER
    needs an IP address… needless to say that I gave it an
    IP address, and nothing happened (I did a reboot, and did not
    see any debug message)…

OK, I removed the device and tried:

  1. Following the instructions in the readme file.
    Nothing… The driver was loaded (I saw it “running”
    in control panel ->devices), but no debug messages were printed.

Can anybody help me? I’m new to intermediate drivers (although I
do understand NDIS and kernel drivers, like the packet.sys sample
of the DDK).

thank you ever so much,

  • Barak

Barak Mandelovich Mercury Interactive ltd.
xxxxx@conduct.com 19 Shabazi st.
Tel: +972 3 539 9286 Yehud, 56100
Fax: +972 3 533 1617 Israel

Barak,

There are several versions of ImSamp around. All are confusing to install.
Sorry.

The NDIS IM FAQ at http: offers
some information.

Regards,

Thomas F. Divine

PCAUSA - Toolkits & Resources For Network Software Developers
NDIS Protocol - TDI Client - Windows 95 Redirector
http:

----- Original Message -----
From: Barak Mandelovich
To: NT Developers Interest List
Sent: Friday, April 07, 2000 11:29 AM
Subject: [ntdev] NDIS intermediate driver - imsamp problem

> Hi everybody!
>
> I’m writing this message after spending 2 whole
> days on trying to operate the darn thing…
>
> (I run WinNT workstation 4.0, SP5)
>
> Well, her goes:
>
> I built the ImSamp.sys file, with a few DbgPrint() calls
> in certain places (e.g.: when entering the “send” function)
> and tried the following 2 things:
> 1. Installing it using the OEMSETUP file supplied by MS.
> After installing the imsamp file and pressing “OK”, I got
> a message from the TCP stack that the newly installed ADAPTER
> needs an IP address… needless to say that I gave it an
> IP address, and nothing happened (I did a reboot, and did not
> see any debug message)…
>
> OK, I removed the device and tried:
>
> 2. Following the instructions in the readme file.
> Nothing… The driver was loaded (I saw it “running”
> in control panel ->devices), but no debug messages were printed.
>
> Can anybody help me? I’m new to intermediate drivers (although I
> do understand NDIS and kernel drivers, like the packet.sys sample
> of the DDK).
></http:></http:>

I don’t have a quick answer for you, but since I use a driver based on this
sample, I have some tips. The first is to try the modified sample from
www.pcausa.com; it’s very good, and they have a version that will work with
WAN adapters. The second is to be sure that whatever you are using to
capture debug output can capture kernel mode debug output, such as SoftIce,
WinDbg, or the DebugViewer from www.sysinternals.com.

Ed

Hi everybody!

I’m writing this message after spending 2 whole
days on trying to operate the darn thing…

(I run WinNT workstation 4.0, SP5)

Well, her goes:

I built the ImSamp.sys file, with a few DbgPrint() calls
in certain places (e.g.: when entering the “send” function)
and tried the following 2 things:

  1. Installing it using the OEMSETUP file supplied by MS.
    After installing the imsamp file and pressing “OK”, I got
    a message from the TCP stack that the newly installed ADAPTER
    needs an IP address… needless to say that I gave it an
    IP address, and nothing happened (I did a reboot, and did not
    see any debug message)…

OK, I removed the device and tried:

  1. Following the instructions in the readme file.
    Nothing… The driver was loaded (I saw it “running”
    in control panel ->devices), but no debug messages were printed.

Can anybody help me? I’m new to intermediate drivers (although I
do understand NDIS and kernel drivers, like the packet.sys sample
of the DDK).

thank you ever so much,

  • Barak

Barak Mandelovich Mercury Interactive ltd.
xxxxx@conduct.com 19 Shabazi st.
Tel: +972 3 539 9286 Yehud, 56100
Fax: +972 3 533 1617 Israel

Please excuse the blatant advertising, but there is a talk dedicated to
writing NDIS Intermediate drivers at WinHEC
(http://www.microsoft.com/winhec) this year. Barak, you might find it
helpful if somehow you can manage to travel to New Orleans.

Others, do you think it is appropriate to discuss (and announce) public
Microsoft events on this alias. I want to make sure that everyone hears
about activities that are useful to driver developers, but at the same time,
I don’t want to abuse this alias.

I welcome your comments…

–Sandy

-----Original Message-----
From: Jeffrey Wang [mailto:xxxxx@morecom.com]
Sent: Friday, April 07, 2000 8:38 AM
To: NT Developers Interest List
Subject: [ntdev] RE: NDIS intermediate driver - imsamp problem

A few things you can check:

Did you install the debug build or release build?
What did you use to look for debug outputs?
Did you set the DebugLevel and DebugMask to the correct values in the
registry?

Jeffrey

-----Original Message-----
From: Barak Mandelovich [mailto:xxxxx@conduct.com]
Sent: Friday, April 07, 2000 11:29 AM
To: NT Developers Interest List
Subject: [ntdev] NDIS intermediate driver - imsamp problem

Hi everybody!

I’m writing this message after spending 2 whole
days on trying to operate the darn thing…

(I run WinNT workstation 4.0, SP5)

Well, her goes:

I built the ImSamp.sys file, with a few DbgPrint() calls
in certain places (e.g.: when entering the “send” function)
and tried the following 2 things:

  1. Installing it using the OEMSETUP file supplied by MS.
    After installing the imsamp file and pressing “OK”, I got
    a message from the TCP stack that the newly installed ADAPTER
    needs an IP address… needless to say that I gave it an
    IP address, and nothing happened (I did a reboot, and did not
    see any debug message)…

OK, I removed the device and tried:

  1. Following the instructions in the readme file.
    Nothing… The driver was loaded (I saw it “running”
    in control panel ->devices), but no debug messages were printed.

Can anybody help me? I’m new to intermediate drivers (although I
do understand NDIS and kernel drivers, like the packet.sys sample
of the DDK).

thank you ever so much,

  • Barak

Barak Mandelovich Mercury Interactive ltd.
xxxxx@conduct.com 19 Shabazi st.
Tel: +972 3 539 9286 Yehud, 56100
Fax: +972 3 533 1617 Israel


You are currently subscribed to ntdev as: xxxxx@exchange.microsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

you have not told which debugger you are using to see debugprints…

Ajitabh Prakash
Sr.Software Engineer
Future Software
480/481 Nandnam,Chennai

-----Original Message-----
From: Barak Mandelovich [SMTP:xxxxx@conduct.com]
Sent: Friday, April 07, 2000 8:59 PM
To: NT Developers Interest List
Subject: [ntdev] NDIS intermediate driver - imsamp problem

Hi everybody!

I’m writing this message after spending 2 whole
days on trying to operate the darn thing…

(I run WinNT workstation 4.0, SP5)

Well, her goes:

I built the ImSamp.sys file, with a few DbgPrint() calls
in certain places (e.g.: when entering the “send” function)
and tried the following 2 things:

  1. Installing it using the OEMSETUP file supplied by MS.
    After installing the imsamp file and pressing “OK”, I got
    a message from the TCP stack that the newly installed ADAPTER
    needs an IP address… needless to say that I gave it an
    IP address, and nothing happened (I did a reboot, and did not
    see any debug message)…

OK, I removed the device and tried:

  1. Following the instructions in the readme file.
    Nothing… The driver was loaded (I saw it “running”
    in control panel ->devices), but no debug messages were printed.

Can anybody help me? I’m new to intermediate drivers (although I
do understand NDIS and kernel drivers, like the packet.sys sample
of the DDK).

thank you ever so much,

  • Barak

Barak Mandelovich Mercury Interactive ltd.
xxxxx@conduct.com 19 Shabazi st.
Tel: +972 3 539 9286 Yehud, 56100
Fax: +972 3 533 1617 Israel
---------------------------------------------------- << File: barak.vcf >>

the purpose is to share the knowledge…isn’t it…I feel that you should go ahead…

Ajitabh Prakash
Sr.Software Engineer
Future Software
480/481 Nandnam,Chennai

-----Original Message-----
From: Sandy Spinrad [SMTP:xxxxx@Exchange.Microsoft.com]
Sent: Saturday, April 08, 2000 12:04 AM
To: NT Developers Interest List
Subject: [ntdev] RE: NDIS intermediate driver - imsamp problem

Please excuse the blatant advertising, but there is a talk dedicated to
writing NDIS Intermediate drivers at WinHEC
(http://www.microsoft.com/winhec) this year. Barak, you might find it
helpful if somehow you can manage to travel to New Orleans.

Others, do you think it is appropriate to discuss (and announce) public
Microsoft events on this alias. I want to make sure that everyone hears
about activities that are useful to driver developers, but at the same time,
I don’t want to abuse this alias.

I welcome your comments…

–Sandy

-----Original Message-----
From: Jeffrey Wang [mailto:xxxxx@morecom.com]
Sent: Friday, April 07, 2000 8:38 AM
To: NT Developers Interest List
Subject: [ntdev] RE: NDIS intermediate driver - imsamp problem

A few things you can check:

Did you install the debug build or release build?
What did you use to look for debug outputs?
Did you set the DebugLevel and DebugMask to the correct values in the
registry?

Jeffrey

-----Original Message-----
From: Barak Mandelovich [mailto:xxxxx@conduct.com]
Sent: Friday, April 07, 2000 11:29 AM
To: NT Developers Interest List
Subject: [ntdev] NDIS intermediate driver - imsamp problem

Hi everybody!

I’m writing this message after spending 2 whole
days on trying to operate the darn thing…

(I run WinNT workstation 4.0, SP5)

Well, her goes:

I built the ImSamp.sys file, with a few DbgPrint() calls
in certain places (e.g.: when entering the “send” function)
and tried the following 2 things:

  1. Installing it using the OEMSETUP file supplied by MS.
    After installing the imsamp file and pressing “OK”, I got
    a message from the TCP stack that the newly installed ADAPTER
    needs an IP address… needless to say that I gave it an
    IP address, and nothing happened (I did a reboot, and did not
    see any debug message)…

OK, I removed the device and tried:

  1. Following the instructions in the readme file.
    Nothing… The driver was loaded (I saw it “running”
    in control panel ->devices), but no debug messages were printed.

Can anybody help me? I’m new to intermediate drivers (although I
do understand NDIS and kernel drivers, like the packet.sys sample
of the DDK).

thank you ever so much,

  • Barak

Barak Mandelovich Mercury Interactive ltd.
xxxxx@conduct.com 19 Shabazi st.
Tel: +972 3 539 9286 Yehud, 56100
Fax: +972 3 533 1617 Israel


You are currently subscribed to ntdev as: xxxxx@exchange.microsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)


You are currently subscribed to ntdev as: xxxxx@future.futsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Barak,

I find it strange that it asked for an IP address. Normally an IM
driver binds transparently between an adapter and a protocol. It
shouldn’t look like another adapter, it should look like the adapter
that it is bound above.

I used the PCAUSA IM sample a while back; I’ll try and dig up the
sources I used. It worked fine when binding to a standard Ethernet
driver. Where I ran into trouble was in trying to bind to a WAN
adapter. I never got that working properly.

Just out of curiosity, what do you want to do with it?

Clark

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Barak
Mandelovich
Sent: Friday, April 07, 2000 10:29 AM
To: NT Developers Interest List
Subject: [ntdev] NDIS intermediate driver - imsamp problem

Hi everybody!

I’m writing this message after spending 2 whole
days on trying to operate the darn thing…

(I run WinNT workstation 4.0, SP5)

Well, her goes:

I built the ImSamp.sys file, with a few DbgPrint() calls
in certain places (e.g.: when entering the “send” function)
and tried the following 2 things:

  1. Installing it using the OEMSETUP file supplied by MS.
    After installing the imsamp file and pressing “OK”, I got
    a message from the TCP stack that the newly installed ADAPTER
    needs an IP address… needless to say that I gave it an
    IP address, and nothing happened (I did a reboot, and did not
    see any debug message)…

OK, I removed the device and tried:

  1. Following the instructions in the readme file.
    Nothing… The driver was loaded (I saw it “running”
    in control panel ->devices), but no debug messages were printed.

Can anybody help me? I’m new to intermediate drivers (although I
do understand NDIS and kernel drivers, like the packet.sys sample
of the DDK).

thank you ever so much,

  • Barak

Barak Mandelovich Mercury Interactive ltd.
xxxxx@conduct.com 19 Shabazi st.
Tel: +972 3 539 9286 Yehud, 56100
Fax: +972 3 533 1617 Israel

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2

iQA/AwUBOPDG9eB0WaKgfXz5EQKtzACfTH87E969ev73xVJMytLpb52s1aEAnjtr
NOrrOu6xVXo8pH6fa9lY6lLm
=uKUr
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I don’t have a problem with announcements like this. I doubt that it
will help Barak’s problem though.

I’ll bet that the talk at WinHEC will center on NDIS 5.0 IM drivers,
which are a bit different than the NDIS 4.0 driver that Barak wants to
use (since he’s using NT, not Win2k/98).

Just my $0.02

Clark

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Sandy Spinrad
Sent: Friday, April 07, 2000 1:34 PM
To: NT Developers Interest List
Subject: [ntdev] RE: NDIS intermediate driver - imsamp problem

Please excuse the blatant advertising, but there is a talk dedicated
to
writing NDIS Intermediate drivers at WinHEC
(http://www.microsoft.com/winhec) this year. Barak, you might find
it
helpful if somehow you can manage to travel to New Orleans.

Others, do you think it is appropriate to discuss (and announce)
public
Microsoft events on this alias. I want to make sure that everyone
hears
about activities that are useful to driver developers, but at the
same time,
I don’t want to abuse this alias.

I welcome your comments…

–Sandy

-----Original Message-----
From: Jeffrey Wang [mailto:xxxxx@morecom.com]
Sent: Friday, April 07, 2000 8:38 AM
To: NT Developers Interest List
Subject: [ntdev] RE: NDIS intermediate driver - imsamp problem

A few things you can check:

Did you install the debug build or release build?
What did you use to look for debug outputs?
Did you set the DebugLevel and DebugMask to the correct values in
the
registry?

Jeffrey

> -----Original Message-----
> From: Barak Mandelovich [mailto:xxxxx@conduct.com]
> Sent: Friday, April 07, 2000 11:29 AM
> To: NT Developers Interest List
> Subject: [ntdev] NDIS intermediate driver - imsamp problem
>
>
> Hi everybody!
>
> I’m writing this message after spending 2 whole
> days on trying to operate the darn thing…
>
> (I run WinNT workstation 4.0, SP5)
>
> Well, her goes:
>
> I built the ImSamp.sys file, with a few DbgPrint() calls
> in certain places (e.g.: when entering the “send” function)
> and tried the following 2 things:
> 1. Installing it using the OEMSETUP file supplied by MS.
> After installing the imsamp file and pressing “OK”, I got
> a message from the TCP stack that the newly installed ADAPTER
> needs an IP address… needless to say that I gave it an
> IP address, and nothing happened (I did a reboot, and did not
> see any debug message)…
>
> OK, I removed the device and tried:
>
> 2. Following the instructions in the readme file.
> Nothing… The driver was loaded (I saw it “running”
> in control panel ->devices), but no debug messages were
printed.
>
> Can anybody help me? I’m new to intermediate drivers (although I
> do understand NDIS and kernel drivers, like the packet.sys sample
> of the DDK).
>
> thank you ever so much,
>
> - Barak
>
> –
> ----------------------------------------------------
> Barak Mandelovich Mercury Interactive ltd.
> xxxxx@conduct.com 19 Shabazi st.
> Tel: +972 3 539 9286 Yehud, 56100
> Fax: +972 3 533 1617 Israel
> ----------------------------------------------------
>


You are currently subscribed to ntdev as:
xxxxx@exchange.microsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)


You are currently subscribed to ntdev as: xxxxx@wirespeed.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2

iQA/AwUBOPDHt+B0WaKgfXz5EQIDQwCgxuyMXZtE0yOHNkf7Rtt3g8Zy9K0An0C/
5ZarSlWOiYo4Wys3JXnQRsq0
=NfT4
-----END PGP SIGNATURE-----