Hi,

I've found that every time WinDump -D skips some device in printed device
list it's connected with specific error code for CreateFile in
PacketOpenAdapter() in Packet.dll.
Usually when CreateFile is used to open device that can't capture packets it
returrns INVALID_HANDLE (no. 6) error code. But sometimes for proper packet
capture device error no 1450 occures (ERROR_NO_SYSTEM_RESOURCES) and that
device isn't printed by WinDump -D.
Do you know the possible reason of that behaviour.
It happens on uni and on dual processor machines.

Regards,
Szymek


Reply via email to