Wireshark-dev: Re: [Wireshark-dev] Win2000 Error: wireshark.exe is not a valid Win32 applicatio
From: Greg Bell <[email protected]>
Date: Wed, 22 Aug 2007 09:30:54 -0700 (PDT)
I guess if I used VS 6.0, I wouldn't need Platform SDK 2003 as its already integrated in the 6.0 compiler package. To use 6.0, I would need to prepare cmd.exe by calling
"C:\Program Files\Microsoft Visual Studio\VC98\Bin\vcvars32.bat"
instead of
"C:\Program Files\Microsoft Visual Studio 8\VC\bin\vcvars32.bat"
This would still not resolve the issue with VC 2005 EE and Platform SDK 2003 R3. I'm surprised this is not a common problem among other Wireshark developers; do people just not use (or test on) Windows 2000 anymore?

Graham Bloice <[email protected]> wrote:
Greg Bell wrote:
> Here are the result of the where nmake/cl/link/mt:
> where nmake
> C:\Program Files\Microsoft Visual Studio 8\VC\bin\nmake.exe
> C:\Program Files\Microsoft Platform SDK for Windows Server 2003
> R2\Bin\nmake.exe
> C:\Program Files\Microsoft Visual Studio\VC98\Bin\NMAKE.EXE
> where cl
> C:\Program Files\Microsoft Visual Studio 8\VC\bin\cl.exe
> C:\Program Files\Microsoft Visual Studio\VC98\Bin\CL.EXE
> where link
> C:\Program Files\Microsoft Visual Studio 8\VC\bin\link.exe
> C:\Program Files\Microsoft Visual Studio\VC98\Bin\LINK.EXE
> where mt
> C:\Program Files\Microsoft Visual Studio 8\VC\bin\mt.exe
> C:\Program Files\Microsoft Platform SDK for Windows Server 2003
> R2\Bin\mt.exe
These look OK, what's the value of your INCLUDE env var?
> I have Visual C++ 6.0 installed on this system as well; would using
> this compiler help? I use Visual 2005 EE because its recommended in
> the Win32 build guide.

As the main win32 build is still produced using 6.0 I would think so. I
stopped using it about 4 months ago so I can't comment myself. You
might still run into the same issue though using the W2K3 SDK.


Graham Bloice

Wireshark-dev mailing list
[email protected]

Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool.