Building the 32-bit version of Wireshark in the same environment
(Windows 7, VS2010EE), the resulting Wireshark.exe runs correctly on Vista.
So now I'm starting to think either (a) VS2010EE 64-bit executables can
only be run on Windows 7 [at least if built on Windows 7], or (b) my
setup for building 64-bit on Windows 7 isn't quite correct. And since
the 64-bit Wireshark runs just fine on Windows 7, I'm leaning toward (a)
above.
My understanding is that the Wireshark build machine for 64-bit is using
VS2010, not VS2010EE. Is that correct?
On 11/14/2012 08:32 AM, David Ameiss wrote:
Interesting... Dependency Walker indicates that IESHIMS.DLL is missing
on both Windows 7 and Vista, for both the official 1.8.2 build and the
one I'm building. But both (official and local-built) run on Window 7,
and only the official build runs on Vista.
One difference I *am* seeing is that the official build is digitally
signed, but my build is not - as seen in View->Properties from
Dependency Walker. Don't know if this is a red herring or not. And I
can't seem to find anywhere in Vista that would control whether or not
non-digitally-signed programs can run.
On 11/14/2012 07:46 AM, David Ameiss wrote:
"file wireshark-gtk2/wireshark.exe" returns "PE32+ executable (GUI)
x86-64, for MS Windows"
I believe the stackoverflow article is essentially the instructions
found in
http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html, which
I followed. It's certainly possible I missed a step somewhere, but (1)
the generated installer installs fine on Windows 7, and installs into
the "Program Files" directory (rather than "Program Files (x86)",
implying that it's a 64-bit app), and (2) it runs on Windows 7 with no
problems.
Dependency Walker is my next step.
On 11/13/2012 09:42 PM, Gerald Combs wrote:
On 11/14/12 11:39 AM, Gerald Combs wrote:
Do you have the Cygwin "file" package installed on your build
system? If
so, what does "file wireshark-gtk2/wireshark.exe" return? Also, are you
trying to build a 64-bit executable using Visual C++ 2010EE? If so,
that
might require extra effort:
http://stackoverflow.com/questions/1865069/how-to-compile-a-64-bit-application-using-visual-c-2010-express
I forgot to add that you might also try opening wireshark.exe in
Dependency Walker on the XP and Vista machines to try to figure out why
it won't run.
http://www.dependencywalker.com/
___________________________________________________________________________
Sent via: Wireshark-dev mailing list<wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
--
David Ameiss
netshark@xxxxxxxxxxxxx
