The second installation created a new network device with the same name
(USB100TX) of the old one:
when winpcap uses this name, it accesses the first of the two devices, that
is no more valid.
This is a common problem of NDIS under Win9x when multiple identical
adapters are installed.
You can try to:
- remove winpcap
- uninstall all the instances of the network adapter from the control panel
- reinstall the adapter
- reinstall winpcap

Loris

> I have a Win98 system, with WinPcap 2.3 installed, and WinDump and
Ethereal.
>
> I had everything working fine, and was able to capture packets and
> diagnose some networking setup problems.  However, at one point I
> decided I needed to remove my network adapter from the system and remove
> the various networking protocols.
>
> After that I reinstalled the adapter (Linksys USB-attached USB100TX),
> reinstalled all the networking protocols I'd had before, and I have all
> the normal software (browsers, news readers, e-mail, Windows file/print
> sharing, etc.) working fine.
>
> I still have a need to do some packet capturing to see some requests
> that are coming in to my system from the Internet, but I cannot get
> WinDump nor Ethereal to work (I've reinstalled both, and WinPcap, too).
>   The indication (from discussion with the Ethereal folks) is a WinPcap
> error.  Whenever I try to do a capture I get an error message
>     Error opening adapter: The system cannot find the file specified.
>
> I didn't see anything obvious in the FAQ or mailing list archive.  Is
> this some obvious problem with some piece of Windows that I'm missing,
> or do I need to do additional diagnosis?
>
> (Actually, looking at Windows Networking info I seem to have that
> adapter installed twice; For some reason occasionally Win98 seems to
> lose it and reinstall it, giving me two.)
>
> The debugging version of packet.dll reported:
>
> ************Packet32: DllMain************
> Packet32: StartPacketDriver
> Found adapter: USB100TX
> Packet32: PacketOpenAdapter, opening USB100TX
> Packet32: PacketDeviceIoControl
> Packet32: unsupported API call return error!
> Packet32: PacketOpenAdapter Could not open adapter, 4
> Error=2
> Found adapter: PPPMAC
> Packet32: PacketOpenAdapter, opening PPPMAC
> Packet32: PacketDeviceIoControl
> Packet32: PacketSetFilter
> Packet32: PacketRequest
> Packet32: PacketRequest
> Packet32: PacketRequest
> Adapter description: PPP Adapter.
> Packet32: PacketCloseAdapter
> Found adapter: USB100TX
> Packet32: PacketOpenAdapter, opening USB100TX
> Packet32: PacketDeviceIoControl
> Packet32: unsupported API call return error!
> Packet32: PacketOpenAdapter Could not open adapter, 4
> Error=2
>
> ************Packet32: DllMain************
> Packet32: StopPacketDriver
>
>
> Thanks,
> Walt
>
>

Reply via email to