Hi,
There seems to be an annoying bug in Windows that causes this problem
when no Ethernet interface is connected. I've no idea what's causing
that, and hope it will be addressed soon
Thanx,
Jaap
Sent from my iPhone
On 24 jun 2009, at 10:10, "Oliver Keller"
<oliver.keller@xxxxxxxxxxxxx> wrote:
Hi all,
first : thanks to the developers for constant work on that awesome
tool !
I switched to Wireshark 1.2 these days and there is a strange
problem :
Using VMware, I can install and use Wireshark in a guest system
(WinXP)
with no problems at all. However, installing the program on the host
(which
is also XP), I can´t start it without a crash. I switched back to 1.
0.4
(without changing WinPcap) and everything works fine. Reinstalling
1.2.0
gives the same error again. So I guess it´s not the WinPcap library,
but
something else.
Maybe it´s the interfaces, cause the guest has just the emulated AMD
net NIC
while the host features the real card (Broadcom Netlink Gigabit)
plus 5
MS-loopback interfaces. Disabling the loopback interfaces doesn´t he
lp,
plus 1.0.4 has no issues with the loopbacks.
I copied the crashreport but don´t want to clog the mailinglist, I c
an post
it if you think it may help.
Best regards,
Oliver
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx
>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?
subject=unsubscribe
