https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4667
--- Comment #5 from Jaap Keuter <jaap.keuter@xxxxxxxxx> 2010-04-14 09:36:33 CEST ---
(In reply to comment #4)
> > IE6? That has been sent to the eternal bitfields. Time to get rid of it.
>
> Trust me, if I had a choice, I would, but that's what my customers are using.
>
I hear you ;)
> > What does Windump do in this case?
>
> windump works, as long as I don't try to use the -w flag, or redirect the
> output using ">". If I do either of those things, then it BSOD's with the same
> error code as the Wireshark BSOD:
>
> Error code 1000007f, parameter1 00000008, parameter2 ba340d70, parameter3
> 00000000, parameter4 00000000
So, that has to do with actual packet capture, not dissection as Wireshark
does.
Then we get to: WinPcap (version), network interface (hardware, firmware),
network card driver (version) and that kind of stuff.
That's more a subject for the WinPcap developers. Have you taken it up with
them?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
