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

2007-08-30 Thread Greg Bell
gt;> Win32 guide. I tried on a few different Win2K machines and get the same >> error on all of them. One idea: Do you have W2K SP 3 installed? >> SP4 Rgrds, Greg Ulf Lamping <[EMAIL PROTECTED]> wrote: Greg Bell schrieb: > This is what I get when I try and ru

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

2007-08-27 Thread Greg Bell
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 Thanks, /Yin On 8/24/07, Greg Bell <[EMAIL PROTECTED]> wrote:

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

2007-08-24 Thread Greg Bell
On 8/22/07, Graham Bloice <[EMAIL PROTECTED]> 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 File

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

2007-08-22 Thread Greg Bell
Greg 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.e

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

2007-08-22 Thread Greg Bell
TED]> wrote: Greg Bell wrote: > This is what I get when I try and run my wireshark build on Windows > 2000. It works fine on Windows XP and 2003. My build is based off > the 0.99.6 release source. One thing I noticed was that when trying to > install the Visual C++ 2005 Redistrib

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

2007-08-21 Thread Greg Bell
This is what I get when I try and run my wireshark build on Windows 2000. It works fine on Windows XP and 2003. My build is based off the 0.99.6 release source. One thing I noticed was that when trying to install the Visual C++ 2005 Redistributable (during the Wireshark install), it gave a "Erro

Re: [Wireshark-dev] Which install files have changed based on source modifications

2007-06-26 Thread Greg Bell
Hi, This sounds all overly complicated. You could deduce which executable/DLL is affected by you changes by unraveling the build process, but it's much easier to build you own full installer. Thanx, Jaap Greg Bell wrote: > Hello, > > I'd like to make some modifications to

[Wireshark-dev] Which install files have changed based on source modifications

2007-06-25 Thread Greg Bell
Hello, I'd like to make some modifications to Wireshark and package only the modified/new DLL's (or other modified files) in my own installer. This installer would then simply overwrite the original files from a stock install. My question is, how do I know which DLL's I must use base

Re: [Wireshark-dev] simple_dialog not truly modal in win32

2007-05-11 Thread Greg Bell
user input ... } Having a blocking dialog here would be the easiest solution. But I guess if its not possible, then a callback is the only way. Thanks for your help on this! Stephen Fisher <[EMAIL PROTECTED]> wrote: On Fri, May 11, 2007 at 11:44:10AM -0700, Greg Bell wrote: > I'm workin

[Wireshark-dev] simple_dialog not truly modal in win32

2007-05-11 Thread Greg Bell
Hi, I'm working with the simple_dialog (gtk\simple_dialog.c) and even though it is defined as being modal, gtk_window_set_modal(GTK_WINDOW(win), TRUE); in display_simple_dialog(...) the calling code path continues execution after the dialog opens, without waiting for the user