https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7833
--- Comment #12 from cheidenreich@xxxxxxxxx 2012-10-15 10:27:12 PDT ---
(In reply to comment #7)
Hi Chris,
I was originally running the 64-bit version. But in the blogs it stated that
if it's a 64 bit, it will use all of the memory resources it can which could
cause the crash. So I switch to the 32-bit since it should look for no more
than 4 gigs. This still didn't not work.
The Hard drive on the pc isn't large enough to host the data coming through.
So I have an external. If I run dumpcap and it's only saving to a temp
directory, it'll crash due to tying up resources there. Is there a way to
redirect the capture to the external drive? Does it also open in Wireshark as
if it was a normal live capture?
> To expand upon Bill's comments a bit ... dumpcap writes packets to a temporary
> capture file in the Temp directory, which you can easily find by starting
> Wireshark, then navigating to Help -> About -> Folders -> Temp. If there's a
> crash, the temporary capture file may still be there, which could aide in
> troubleshooting the problem.
> You can also get information about dumpcap from:
> 1) The man page: http://www.wireshark.org/docs/man-pages/dumpcap.html
> 2) The user guide:
> http://www.wireshark.org/docs/wsug_html_chunked/AppToolsdumpcap.html
> Apart from that, I did notice that you are running the 32-bit version of
> Wireshark on a 64-bit platform. I am wondering if that might be related to the
> problem? In theory, it should work fine, but have you tried running the 64-bit
> version?
> http://wiresharkdownloads.riverbed.com/wireshark/win64/wireshark-win64-1.6.11.exe
> And is there any particular reason why you're still on the "old" stable branch?
> Have you tried the latest stable 1.8.3 version?
> http://wiresharkdownloads.riverbed.com/wireshark/win64/Wireshark-win64-1.8.3.exe
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
