path: root/help
diff options
authorEvan Huus <eapache@gmail.com>2013-03-18 18:55:58 +0000
committerEvan Huus <eapache@gmail.com>2013-03-18 18:55:58 +0000
commit1983b55379ecb9fc5c0cad604297247b895abd35 (patch)
tree8b404b8b75d2c329603106a28ac372a9a73a83ca /help
parent847fb4ef0a67e235d5822373eb2c8f7b648b5c98 (diff)
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
Diffstat (limited to 'help')
1 files changed, 4 insertions, 4 deletions
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 <tt>/tmp</tt> or
-<tt>/var/tmp</tt> on UNIX-flavored OSes, <tt>\TEMP</tt> on the main system disk
+<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,
-<tt>\Documents and Settings\</tt><var>your login name</var>
-<tt>\Local Settings\Temp</tt> on the main system disk on Windows
+<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
+<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. If you
are capturing on a single interface, it will have a name of the form,
<tt>wireshark_&lt;fmt&gt_&lt;iface&gt;_YYYYmmddHHMMSS_XXXXXX</tt>, where