Hi All, We have developed a monitoring service which uses the winpcap 4.0. The MonitorService will be installed in the PC's with automatic mode and will be started during the boot up of the machine.
In the main thread of the service we have a call to pcap_start_oem() function. After that we have the call to find the list of network adapters. When the service is set to Automatic start mode we see a delay of 80 seconds to execute the function pcap_start_oem() during the boot up of the machine as below. 18:29:39.325 2152 MonitorService - Calling pcap_start_oem 18:31:13.420 2152 MonitorService - Out of pcap_start_oem However after booting up the machine, if we start the Monitor service manually it does takes only few milliseconds to execute this function. 18:27:29.199 1564 MonitorService - Calling pcap_start_oem 18:27:29.324 1564 MonitorService - Out of pcap_start_oem Since by default we have the service set to Automatic mode, the boot up of the windows machine takes more time. My understanding is while the system boots up, the time taken to initialize the packet filter kernel mode driver also adds up to the function call execution time. Please correct me if I am wrong. Is there any settings to overcome this issue? Is this expected? Do you have any suggestions to overcome this delay? I need to reduce the time taken during boot up. Need your help in achieving the same. Thanks in advance. With Regards, Rajesh Kumar R _______________________________________________ Winpcap-users mailing list [email protected] https://www.winpcap.org/mailman/listinfo/winpcap-users
