https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3808
--- Comment #3 from Tony <tony.stivers@xxxxxxxxx> 2009-08-04 08:51:31 PDT ---
(In reply to comment #0)
> Build Information:
> Version 1.2.1 (SVN Rev 29141)
>
> Copyright 1998-2009 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> Compiled with GTK+ 2.14.7, with GLib 2.18.4, with WinPcap (version unknown),
> with libz 1.2.3, without POSIX capabilities, without libpcre, without SMI,
> without c-ares, without ADNS, with Lua 5.1, without GnuTLS, without Gcrypt,
> without Kerberos, without GeoIP, with PortAudio V19-devel (built Jul 19 2009),
> without AirPcap.
> NOTE: this build doesn't support the "matches" operator for Wireshark filter
> syntax.
>
> Running on Windows Vista, build 7100, with WinPcap version 4.1 beta5
> (packet.dll
> version 4.1.0.1452), based on libpcap version 1.0.0.
>
> Built using Microsoft Visual C++ 9.0 build 30729
>
> Wireshark is Open Source Software released under the GNU General Public
> License.
>
> Check the man page and http://www.wireshark.org for more information.
> --
> This is more or less an issue than a bug, when running under vista, wireshark
> must be run as an administrator, or it will not work, there are no devices
> listed under the interfaces, i already know the fix, which is to set wireshark
> up for UAC compatibility. I would fix the bug, but i'm a Visual Studio
> developer, and not very good with C/C++.
>
ahh, perhaps that is the solution then, no i didn't set it to load at startup
because i thought that was only needed for user accounts that were set to
"limited", and i don't like having more things run at startup than need be, it
isn't really an issue for me i guess because i know how to run it as
administrator. i just figured some users may have trouble with it and thought
i'd submit a bug report to make sure there wasn't already a solution, and if
there was then to let you guys know the issue :)
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.