diff --git a/help/faq.py b/help/faq.py
index cb4c7dce99..aa28d5f544 100755
--- a/help/faq.py
+++ b/help/faq.py
@@ -737,16 +737,6 @@ Similar problems may exist with older versions of GTK+ for earlier
versions of Solaris.
""")
-question("""When I run Wireshark on Windows NT, why does it die with a Dr.
-Watson error, reporting an "Integer division by zero" exception, when I
-start it?""")
-
-answer("""
-In at least some case, this appears to be due to using the
-default VGA driver; if that's not the correct driver for your video
-card, try running the correct driver for your video card.
-""")
-
question("""When I try to run Wireshark, why does it complain about
sprint_realloc_objid being undefined?""")
@@ -1351,12 +1341,11 @@ 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
-(normally C:) on Windows 9x/Me/NT 4.0,
-\\Documents and Settings\\your login name
+(normally \\Documents and Settings\\your login name
\\Local Settings\\Temp on the main system disk on Windows
-2000/Windows XP/Windows Server 2003, and
+Windows XP and Server 2003, and
\\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
+system disk on Windows Vista and later, 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
<fmt> is the capture file format (pcap or pcapng), and <iface> is
@@ -1383,7 +1372,7 @@ Wireshark give me an error if I try to capture on that interface?
""", "capprobwin")
answer("""
-If you are running Wireshark on Windows NT 4.0, Windows 2000, Windows XP,
+If you are running Wireshark on Windows XP,
or Windows Server 2003, and this is the first time you have run a
WinPcap-based program (such as Wireshark, or TShark, or WinDump, or
Analyzer, or...) since the machine was rebooted, you need to run that
@@ -1393,7 +1382,7 @@ such programs until you reboot.
-If you are running on Windows Windows 2000/Windows XP/Windows Server
+If you are running on Windows Windows XP or Windows Server
2003 and have administrator privileges or a WinPcap-based program has
been run with those privileges since the machine rebooted, this problem
might clear up if you completely un-install WinPcap and then
@@ -1411,23 +1400,6 @@ Therefore, if the OS, the WinPcap library, or the WinPcap driver don't
support capturing on a particular network interface device, Wireshark
won't be able to capture on that device.
-
-
-Note that:
-
-