Hi.
 
It's not difficult to rename the names of the dlls...
 
...but...
 
...the problem is that if a packet.dll exists on that system, maybe there was WinPcap installed on the system, or another sort of packet capture driver (for example the DDK packet example). Remember that Winpcap is not only two dlls, it is composed also by a kernel driver (packet.sys/vxd or npf.sys/vxd, depending on version and OS), that interacts directly with packet.dll (and with wpcap.dll), so it is not so simple.
 
It is advisable that you understand who (=which program) uses that packet.dll, before trying to compile new WinPcap dlls with different names.
 
GV
----- Original Message -----
From: andrey
Sent: Sunday, May 12, 2002 11:09 AM
Subject: [WinPcap-users] Wpcap conflict.

Hi. Recently, I have developed a project that uses wpcap, but it turned out that a target computer already had
a dll by the name packet.dll and packet32.dll doing some stuff. I wondered if somebody could tell me how to solve the conflict, or, better yet, if somebody could create a wpcap distribution that does not contains these file names.
Please HELP!!!
                                                        Regards
                                                                    Andrey.

Reply via email to