> I get an error when trying to install the IP Service on my NT 4.0 (SP6). I
> get a "Setup Message" that says, "Registry Service subkey already exists."
http://netgroup-serv.polito.it/winpcap/misc/faq.htm
says:
"Q-1: When I try to install the driver I get the error: "Could
not create Services subkey".
A: This problem seems to appear on NT 4.0 machines with Internet
Explorer 4/5. Currently we do not know any solution to this
problem. Anyway, please send us an email
(analyzer@xxxxxxxxxxxxxxxxxxxxxxx): maybe you can help us to
solve the problem...
This sounds as if it could be a similar problem (or perhaps the same
problem, if the error message changed in different versions of NT or if
both messages get issued on some versions of NT).
Note that "us" refers to the folks at the Politecnico di Torino who did
WinPcap, not to the Ethereal developers; Ethereal, like the
Politecnico's own WinDump port of tcpdump and their Analyzer Windows GUI
capture and analysis program, just uses WinPcap for captures.
The latest Ethereal FAQ says, as part of the answer to question 3.7:
For problems seen when installing the WinPcap driver or library,
or seen when capturing, check the WinPcap FAQ to see if your
problem is mentioned there.
with "the WinPCap FAQ" linking to the aforementioned FAQ; I should
probably add a generic entry to the Ethereal FAQ directing Windows users
to the WinPcap FAQ as well.
> How can I fix this?
I don't know and, I infer, neither do the Politecnico folks who wrote
WinPcap, at this point.
> I do have an installation of SnifferPro 1 and one other
> tool on my PC.
Windows, unlike many flavors of UNIX, doesn't come with a built-in
mechanism to allow applications to capture packets; each packet analyzer
program tends to have its own special drivers for that - Ethereal
happens to use the same WinPcap that some other programs do, but
Sniffer Pro provides its own.
> Suggestion?
Send mail to "analyzer@xxxxxxxxxxxxxxxxxxxxxxx", and be prepared for
them to ask you questions about your machine and to ask you to do things
on your machine to help them figure out why this is happening and to
test fixes (i.e., as with many other software problems, diagnosing and
fixing the problem may require the participation of the person having
the software problem; there won't necessarily be an immediate magic "do
this and your problems will go away" response).
