Wireshark-dev: Re: [Wireshark-dev] Win2000 Error: wireshark.exe is not a valid Win32 applicatio

From: Greg Bell <greg_bell_12@xxxxxxxxx>
Date: Fri, 24 Aug 2007 11:54:25 -0700 (PDT)
I'm assuming when I do the verify_tools step, it confirms that I'm using nmake/cl/link from VS8 based on the output:
 
C:\wireshark>nmake -f Makefile.nmake verify_tools
Microsoft (R) Program Maintenance Utility Version 8.00.50727.42
Copyright (C) Microsoft Corporation.  All rights reserved.
Checking for required applications:
        cl: /cygdrive/c/Program Files/Microsoft Visual Studio 8/VC/BIN/cl
        link: /cygdrive/c/Program Files/Microsoft Visual Studio 8/VC/BIN/link
        nmake: /cygdrive/c/Program Files/Microsoft Visual Studio 8/VC/BIN/nmake
        bash: /usr/bin/bash
        ............

yin sun <sunyin51@xxxxxxxxx> wrote:
the wiki page suggest you ONLY use nmake/cl/link from VS8 (true name of Visual C++ 2005 Express Edition),
but make sure NOT use nmake/cl/link from 2003 server SDK R2 under windows 2000.

Hope this will help.

/Yin

On 8/22/07, Graham Bloice <graham.bloice@xxxxxxxxxxxxx> wrote:
Greg Bell wrote:
> 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"
> correct?
Yes.  You also need to make changes to config.nmake to indicate the use
of VC6.
>
> 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?
>
I guess folks are:

a) Using a combination of EE and SDK that works on W2K
b) Not testing/using on W2K
c) Using VS2005 Pro or better with a different SDK.

We have had several threads in the past few months with this issue, but
no-one who has had the issue has stayed the course until we resolved it.

You may want to buck the trend!

--
Regards,

Graham Bloice

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev


Shape Yahoo! in your own image. Join our Network Research Panel today!