Log in

View Full Version : problem with softice


The Keeper
June 21st, 2002, 03:06
hello all,

this wasnt happening, but after installing a few programs it started happening, i'll remove all the progs i installed if noone knows the reason this might be happening, well in softice window in the place i type the commands, every time im going to pass a call with F10 this appears

OldTcpipReceiveHandler ==>
OurTcpipTransferDataCompleteHandler ==>
OurTcpipReceiveHandler ==>
==>OurTcpipReceiveHandler.ProtocolBindingContext:C17847D0
OurTcpipReceiveHandler- HeaderBufferSize:E- LookAheadBufferSizeC- PacketSize
C
LookAheadBufferSize:220 >= PacketSize:220
Calling OurTcpipTransferDataCompleteHandler ==>
==>OurTcpipTransferDataCompleteHandler -ProtocolBindingContext:C17847D0- BytesTr
ansfered:220
Call OldReceiveHandler- HeaderSize:14- DataSize:234
==> OldTcpipReceiveHandler. ProtocolBindingContext: C17847D0
OldTcpipReceiveHandler ==>
OurTcpipTransferDataCompleteHandler ==>
OurTcpipReceiveHandler ==>
==>OurTcpipReceiveHandler.ProtocolBindingContext:C17847D0
OurTcpipReceiveHandler- HeaderBufferSize:E- LookAheadBufferSize:2E- PacketSize:2
E
LookAheadBufferSize:46 >= PacketSize:46
Calling OurTcpipTransferDataCompleteHandler ==>
==>OurTcpipTransferDataCompleteHandler -ProtocolBindingContext:C17847D0- BytesTr
ansfered:46
Call OldReceiveHandler- HeaderSize:14- DataSize:60
==> OldTcpipReceiveHandler. ProtocolBindingContext: C17847D0
OldTcpipReceiveHandler ==>
OurTcpipTransferDataCompleteHandler ==>
OurTcpipReceiveHandler ==>
==> OurTcpipReceiveCompleteHandler
OurTcpipReceiveCompleteHandler ==>
==>OurTcpipReceiveHandler.ProtocolBindingContext:C17847D0
OurTcpipReceiveHandler- HeaderBufferSize:E- LookAheadBufferSize:13D- PacketSize:
13D
LookAheadBufferSize:317 >= PacketSize:317
Calling OurTcpipTransferDataCompleteHandler ==>
==>OurTcpipTransferDataCompleteHandler -ProtocolBindingContext:C17847D0- BytesTr
ansfered:317
Call OldReceiveHandler- HeaderSize:14- DataSize:331
==> OldTcpipReceiveHandler. ProtocolBindingContext: C17847D0
==> OurTcpipSendHandler- NdisBindingHandle:C179D540
Call OurTcpipSendPacketHandler- NdisBindingHandle:C179D540 - HeaderSize:E- DataS
ize:36
==> OurTcpipSendPacketHandler
OurTcpipSendPacketHandler ==>
OurTcpipSendHandler ==>
OldTcpipReceiveHandler ==>
OurTcpipTransferDataCompleteHandler ==>
OurTcpipReceiveHandler ==>
==>OurTcpipReceiveHandler.ProtocolBindingContext:C17847D0
OurTcpipReceiveHandler- HeaderBufferSize:E- LookAheadBufferSize:2E- PacketSize:2
E
LookAheadBufferSize:46 >= PacketSize:46
Calling OurTcpipTransferDataCompleteHandler ==>
==>OurTcpipTransferDataCompleteHandler -ProtocolBindingContext:C17847D0- BytesTr
ansfered:46
Call OldReceiveHandler- HeaderSize:14- DataSize:60
==> OldTcpipReceiveHandler. ProtocolBindingContext: C17847D0
OldTcpipReceiveHandler ==>
OurTcpipTransferDataCompleteHandler ==>
OurTcpipReceiveHandler ==>
==>OurTcpipReceiveHandler.ProtocolBindingContext:C17847D0
OurTcpipReceiveHandler- HeaderBufferSize:E- LookAheadBufferSize:2E- PacketSize:2
E
LookAheadBufferSize:46 >= PacketSize:46
Calling OurTcpipTransferDataCompleteHandler ==>
==>OurTcpipTransferDataCompleteHandler -ProtocolBindingContext:C17847D0- BytesTr
ansfered:46
Call OldReceiveHandler- HeaderSize:14- DataSize:60
==> OldTcpipReceiveHandler. ProtocolBindingContext: C17847D0
OldTcpipReceiveHandler ==>
OurTcpipTransferDataCompleteHandler ==>
OurTcpipReceiveHandler ==>
==> OurTcpipReceiveCompleteHandler
OurTcpipReceiveCompleteHandler ==>
==> OurTcpipSendCompleteHandler
OurTcpipSendCompleteHandler ==>
==> OurTcpipSendCompleteHandler

and much more, i have to wait from 30 to 60 seconds til it finish and pass the call, whats it ? where is it from ? anyone got an idea ? im totally lost, it looks like some prog is doing Outputdebugstring but i dont think so, i have only the programs i used to run before when it worked fine *g* im start to get confused, any help is really appreciated,

thanks in advance
The Keeper

NopREtf
June 21st, 2002, 17:37
Maybe in the TOT forum was better

Seems the “ProtocolReceive” function (driver function in NDIS protocols, miniport drivers) .
Do u have some net_proggies which work up ?
Also there are problems related to Realtek-based (e.g., SMC) adapters on the Windows 2000 platform..
Try to remove the network drivers and reinstall them.

ciao
NopREtf

...Sorry my bad english

The Keeper
June 22nd, 2002, 02:50
Hello,

thanks, i found it was a program i had installed other day, it wasnt running but it modified something, when i removed it things came back to normal

Keeper.