The driver I sent you is the most recent version that we have on our CVS. It fixes some bugs that were present in WinPcap version 3.0, among which:
- a wrong allocation of the packet filter memory that caused blue screens with nmap to a couple of other users - a synchronization issue in the buffered write functionality: in some cases the 3.0 driver returns from a write before all the packets are sent. As a result, if the application modifies or releases the packet buffer, inconsistent packets are sent to the wire and blue screens can happen. If you continue to use nmap, can you let me know the results (also if you don't notice any BSOD) within some days from now? It would help me to understand if these fixes solve your problem or if the driver needs further debugging. Loris > "Loris Degioanni" <[EMAIL PROTECTED]> said: > > > Can you try the driver attached to this message and tell me if the bug > > persists? > > I've tried it and ran nmap approx 10 times w/o any BSODs. But I'm > not convinced it's stable. What exactly did you change? > > --gv > > > > ================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] ==================================================================
