[Brian Daniel <daniel_brian@xxxxxxxxxxxx>]

Thanks Gerald. I'll see about getting a copy of Visual C++ 2008 when payday rolls around but $ is tight. Is there an open source Win64 compiler you would recommend for Windows Vista 64-bit and Windows 7 beta 64-bit? Or better yet until I can get the compiler, please make the alpha/beta version of the 64-bit binary available for download and we'll test it for you. The first thing I'm looking for is going beyond the RAM limitations of WIN32 compiled WireShark. Then I want to experiment with Skinny SCCP packets on those larger captures.

Thanks,

Brian

On Thu, Mar 5, 2009 at 6:02 PM, Gerald Combs <gerald@xxxxxxxxxxxxx> wrote:

If you're _really_ serious this, I'd suggest:

 - Taking this discussion over to -dev, since that's where all of the
   developers hang out.

 - Reading up on LP64 vs LLP64, e.g.

http://stackoverflow.com/questions/384502/what-is-the-bit-size-of-long-on-64-bit-windows

   Wireshark happily supports 64 bits on LP64 (Linux, OS X, Solaris, etc.)
   but LLP64 (Windows) is going to take some work.

 - Checking out http://anonsvn.wireshark.org/wireshark-win64-libs/trunk/.
   This contains 64-bit versions of some of the that we use.

 - Looking at config.nmake, all of the instances of Makefile.nmake, and
   tools/win32-setup.sh to see where 64-bit support needs to be added.

 - Looking at the NSIS, U3, and PortableApps packaging directores.

 - Bugging me to add a Windows 64 builder and Bugzilla entries.

 - Bugging me to clean up and check in my 64-bit makefile updates.

Brian Daniel wrote:
> How many of you want to use a 64-bit Wireshark?
> I would like to know how to compile Wireshark source for 64-bit Windows
> Vista Home Premium SP1 and 64-bit Windows 7 beta so I can take more
> advantage of my Quad Q6600 2.4GHz Processor and 4GB RAM.
>
> I'm already using the /3GB when I boot to Windows XP Pro but my capture
> size is 1Gig so I'm running out of memory around 750Meg into the capture
> file. My work around solution is to capture 512Meg at a time.
> Here is what I've found in the Wireshark documentation:
>
> "It is recommended to use the binary installer for Windows, until you
> want to start developing Wireshark on the Windows platform."
> http://www.wireshark.org/docs/wsug_html_chunked/ChBuildInstallWinBuild.html
>
> "Thanks to the Win32 API, development on all Windows platforms will be
> done in a very similar way. All Windows platforms referred to as Win32,
> Win or Windows may be used with the same meaning."
> http://www.wireshark.org/docs/wsdg_html_chunked/ChIntroPlatforms.html#id4702778
>
> All help is appreciated.
> Thanks,
> Brian
>
>

> ------------------------------------------------------------------------

>
> ___________________________________________________________________________
> Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives:    http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
>              mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe

--
Join us for Sharkfest’09  |  Stanford University, June 15 – 18
http://www.cacetech.com/sharkfest.09/

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
            mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe