From 1983b55379ecb9fc5c0cad604297247b895abd35 Mon Sep 17 00:00:00 2001 From: Evan Huus Date: Mon, 18 Mar 2013 18:55:58 +0000 Subject: From Alex Brinister via https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8492 Correctly escape slashes in faq.py so that it will run under python 3.x It still runs fine under 2.x, at least on my machine. svn path=/trunk/; revision=48394 --- help/faq.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'help') diff --git a/help/faq.py b/help/faq.py index 54f356ead6..cb4c7dce99 100755 --- a/help/faq.py +++ b/help/faq.py @@ -1350,12 +1350,12 @@ some platforms (e.g., BSD systems). Also, if at all possible, please send a copy of the capture file that caused the problem. When capturing packets, Wireshark normally writes captured packets to a temporary file, which will probably be in /tmp or -/var/tmp on UNIX-flavored OSes, \TEMP on the main system disk +/var/tmp on UNIX-flavored OSes, \\TEMP on the main system disk (normally C:) on Windows 9x/Me/NT 4.0, -\Documents and Settings\your login name -\Local Settings\Temp on the main system disk on Windows +\\Documents and Settings\\your login name +\\Local Settings\\Temp on the main system disk on Windows 2000/Windows XP/Windows Server 2003, and -\Users\your login name\AppData\Local\Temp on the main +\\Users\\your login name\\AppData\\Local\\Temp on the main system disk on Windows 7, so the capture file will probably be there. If you are capturing on a single interface, it will have a name of the form, wireshark_<fmt>_<iface>_YYYYmmddHHMMSS_XXXXXX, where -- cgit v1.2.3