Hello everybody,
has anybody seen/has a clue of what is going on: NdisSend()
returns SUCCESS (via SendComplete), but the underlying miniport’s Send is
not called?
This happens under NT4.0 in trivial configuration, where a propriatery
protocol stack talks to single miniport, which is driving an FIR
(non-network) device. (Stack/miniport talk only to each other and unrelated
– not bound – to any other miniport/protocol on the system).
The problem seems to be timing related – when enough debug
prints added (especially to miniport’s ISR),
symptom goes away – as it does when code is stepped through.
Anatoly