Wireshark-bugs: [Wireshark-bugs] [Bug 4155] Unable to run Wireshark, Fault Module: MSVCR90.dll
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4155
--- Comment #37 from Alex <arotaru@xxxxxxxxxxx> 2009-11-08 05:11:23 PDT ---
(In reply to comment #33)
> (In reply to comment #32)
>
> > Also, why would Wireshark 1.0.10 work if it was really a NIC driver issue? (As
> > per this comment: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4155#c19
> > )
>
> The bug is in the code that draws the little icons in the interface list in the
> upper-left region of the main window in 1.2. Wireshark tries to determine which
> icon to draw using the interface description and name, e.g. "802.11" gets you a
> wireless icon. If the description is empty (that is, if the NIC driver doesn't
> bother to fill in that field) it causes a NULL pointer exception in Wireshark.
>
> Make no mistake -- this is a Wireshark bug. It just happens to be triggered by
> this particular driver.
>
Somehow you've got it working!
Version 1.3.2-SVN-30850 (SVN Rev 30850 from /trunk)
The NIC is still like below:
C:\Tools\Wireshark>tshark -D
1. \Device\NPF_{A677CCD1-FEFF-4CCD-BE91-B0325E7954FF} ()
but I can select the interface in the menu, first shows IPv6 if I click with
the mouse on the IPV6 addr then it changes to my IPv4 addr, capture work on
both.
I've added print screens at attachments, one for default IPv6 the other
changing to IPv4 after mouse selection. As for now I'm happy I can capture :-)
Any more info you'd need from my end please let me know.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
