Hi Everyone,
Ya I’m using IMSamp deserialize driver only and I tried to run this for SP4 to SP6. The messages are keep appearing on each setup. I’m again sending you a snap of kernel stack and the debug messages from IMSamp. I want a guide to where to concentrate to get the root of this?
Here in the following Debug message I observed a major threat from Packet-Id. In the following Imsamp dump somewhere it is “8083AE78” while in Indication and return it shows “8083AE00”. Any idea or explaination?
------------------ IMSAMP Dump -----------------------
Imsamp: (80849DA8) MPSendPackets: 1 XPORT packets
Imsamp: MPSendPackets: (80849DA8) Adapter: Packets to send = 1
Imsamp: (80849DA8) MPSendPackets: 1 IM packets @ 8083AE78,
Imsamp: ClReceiveIndication (80849DA8) +Adapter:h 2
Imsamp: (80849DA8) CLReceiveIndication: Packet 8083AE00 Packetsize 96
Imsamp: CLReceivePacket: Before NdisMIndicateReceivePacket
Imsamp: CLReceivePacket: After NdisMIndicateReceivePacket
Imsamp: (80849DA8) MPReturnPacket: IM Packet 8083AE00
Imsamp: (80849DA8) -Adapter:a 1
Imsamp: (80849DA8) CLReceiveComplete:
Imsamp: (80849DA8) PacketCompletion: IM Packet 8083AE78, Status: 00000000
---------------------- Kernel Stack Dump -------------------
kd> kp
ChildEBP RetAddr
80184200 80169d42 ntoskrnl!DbgBreakPoint
801842dc fcd0b66f ntoskrnl!RtlAssert+0x96
8018433c fccfe572 NDIS!ethFilterDprIndicateReceivePacket+0x3c
80184364 fccdac9d NDIS!ndisMLoopbackPacketX+0xdd
80184378 fcbf5d41 NDIS!ndisMSendX+0x6a
801843a4 fcbe4677 tcpip!ARPSendBCast+0x269
801843d4 fcbe9339 tcpip!ARPTransmit+0xcd
80184454 fcbf6a96 tcpip!IPTransmit+0x1ef
801844a4 fcbf6430 tcpip!UDPSend+0x246
801844c4 fcbf5fc0 tcpip!TdiSendDatagram+0x112
80184500 fcbe4033 tcpip!UDPSendDatagram+0xa7
80184518 8011c9a9 tcpip!TCPDispatchInternalDeviceControl+0x173
8018453c fcb97582 ntoskrnl!IofCallDriver+0x68
8018455c fcb96995 netbt!TdiSendDatagram+0x1fd
8018459c fcbc3c39 netbt!UdpSendDatagram+0xd3
801845e8 fcba02ca netbt!UdpSendNSBcast+0x34a
80184638 fcb99c1f netbt!MSnodeRegCompletion+0x2b9
8018465c 8012c4ae netbt!TimerExpiry+0xb4
8018475c 8012c3bb ntoskrnl!KiTimerListExpire+0xea
80184788 801784e8 ntoskrnl!KiTimerExpiration+0xdf
Thanks to read and write.
Regards,
– Sumit
----- Original Message -----
From: Michal Vodicka
Subject: [ntdev] Re: NDIS IM Driver on NT
>> ----------
>> From: xxxxx@hotmail.com>
>> NT4 supports deserialized drivers since SP3. Maybe it isn’t documented and “supported”
> Clarification: after NT4 SP3 release Microsoft made available the first NDIS IM driver sample named ImSamp. IIRC it was in July 1997.Best regards,
> Michal Vodicka
____________________________________________________________
eLitecore Technologies Pvt. Ltd.
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com