Have you tried winpcap 3.1beta3?
Have a nice day
GV
- Original Message -
From: Craig Carr [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, August 04, 2004 12:49 PM
Subject: RE: [WinPcap-users] Winpcap 3.0 lockup.
The application is on Win2k, the adapter in an Intel 8255xx
Ha
- Original Message -
From: Craig Carr [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 03, 2004 2:28 PM
Subject: [WinPcap-users] Winpcap 3.0 lockup.
Sorry if this type of question has been asked before...but here goes.
We have written a audio recording package, using
Sorry for the previous mail, I hit send too early...
Regarding your problem, have you tried to use winpcap 3.1beta3?
What is the timeout you use when you open the adapter through pcap_openXXX?
What operating system and adapter?
Have a nice day
GV
- Original Message -
From: Craig Carr
Rob,
The memory remains completely static and the applications CPU usage never exceeds ~5%.
Craig.
-Original Message-
From: Rob Henningsgard [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 4 August 2004 12:45 p.m.
To: [EMAIL PROTECTED]
Subject: Re: [WinPcap-users] Winpcap 3.0 lockup.
Craig
Craig,
Can anybody suggest where to start looking?
I hope you meant that: What does Windows Task Manager have to report
about your application's CPU and memory usage, both when you first
launch your package and then after it's been running for a few hours?
Rob---
