Hi.
 
This is a known bug in winpcap 3.0, that was fixed in one of the betas of winpcap 3.1.
This bug is caused by some empty registry keys that remain after you remove some network devices of the system.
The usual suggestion is to update to 3.1beta4. Modifying the registry can be *really dangerous (I never modified the registry for this issue, as  a matter of facts). In case you want to try, go to
 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}
 
and remove all the folders (named 0000, 0001, 0002...) that are empty. No guarantees about it.
 
Regarding GIT, have you tried contacting the GIT developers about this issue with winpcap 3.1beta4? What is the exact problem you are encountering?
 
Have a nice day
GV
 
 
 
----- Original Message -----
Sent: Thursday, January 13, 2005 12:18 PM
Subject: [WinPcap-users] INTERFACE DETECTION FAILED WITH WINPCAP3.0

Programs like Ethereal and GIT don�t see any interfaces with WinPcap 3.0 anymore.

Before it works fine, but after installing and reinstalling some Bluetooth drivers and maybe some other modifications the problem revealed.

(I don�t know exact when and how)

 

I suspect a corrupt link in de register related to my Network Interface and WinPcap3.0.

 

Installing and reinstalling winpcap3.0 and my network interface didn�t work.

 

Interface detection is correct with any higher version of WinPcap (3.1 beta series).

Problem is GIT. It runs only with WinPcap version 3.0. (Ethereal works fine with WinPcap 3.1 beta 4 on my system)

So, I want to get WinPcap3.0 working again.

 

I DON�T WANT TO REINSTALL MY WHOLE SYSTEM TO SOLVE THIS PROBLEM

I want to try to solve it in a less brute way.

 

Question:

What could be the course of preventing winpcap3.0 detecting my network interface?

What are important windows xp registry entry�s which I should check relating to this problem?

 

Please help�.

 

Elwin Nieuwenhuis

([EMAIL PROTECTED])

 

Reply via email to