From 1cf31238ffd9b3320666838578b59d35437e749a Mon Sep 17 00:00:00 2001
From: Jeff Morriss <jeff.morriss@ulticom.com>
Date: Fri, 24 Feb 2012 21:43:48 +0000
Subject: As suggested by multipleinterfaces in
 http://ask.wireshark.org/questions/9194/can-i-recover-a-discarded-capture :

Add the location of the temporary file on Windows 7.

svn path=/trunk/; revision=41183
---
 help/faq.py | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

(limited to 'help')

diff --git a/help/faq.py b/help/faq.py
index 7196e1890c..40f487238f 100755
--- a/help/faq.py
+++ b/help/faq.py
@@ -1352,12 +1352,13 @@ caused the problem; when capturing packets, Wireshark normally writes
 captured packets to a temporary file, which will probably be in
 <tt>/tmp</tt> or <tt>/var/tmp</tt> on UNIX-flavored OSes, <tt>\TEMP</tt>
 on the main system disk (normally <tt>C:</tt>) on Windows 9x/Me/NT 4.0,
-and <tt>\Documents and Settings\</tt><var>your login
-name</var><tt>\Local Settings\Temp</tt> on the main system disk on
-Windows 2000/Windows XP/Windows Server 2003, so the capture file will
-probably be there.  It will have a name of the form,
-<tt>wireshark_iface_YYYYmmddHHMMSS_XXXXXX</tt>.  Please don't send
-a trace file greater than 1 MB when compressed; instead, make it
+<tt>\Documents and Settings\</tt><var>your login name</var>
+<tt>\Local Settings\Temp</tt> on the main system disk on
+Windows 2000/Windows XP/Windows Server 2003, and
+<tt>\Users\<var>your login name</var>\AppData\Local\Temp</tt> on the main system disk on
+Windows 7, so the capture file will probably be there.  It will have a name
+of the form, <tt>wireshark_iface_YYYYmmddHHMMSS_XXXXXX</tt>.  Please don't
+send a trace file greater than 1 MB when compressed; instead, make it
 available via FTP or HTTP, or say it's available but leave it up to a
 developer to ask for it.  If the trace file contains sensitive
 information (e.g., passwords), then please do not send it.
-- 
cgit v1.2.1