osmocom
/
wireshark
14
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

system requirements Windows updates: 

- Vista is no longer beta
- disk space min. 75MB
- be a bit more specific about no longer supported NT 4.0
- some editing

svn path=/trunk/; revision=20904
This commit is contained in:
Ulf Lamping 2007-02-23 19:40:27 +00:00
parent a8fb7d24d0
commit bfe862b91e
1 changed files with 17 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
docbook/wsug_src/WSUG_chapter_introduction.xml
View File

@ -192,16 +192,16 @@
<listitem><para>Working with a busy network can easily produce huge
memory and disk space usage! For example: Capturing on a fully saturated
100MBit/s Ethernet will produce ~ 750MBytes/min! Having a fast processor,
lots of memory and disk space is a good idea here.</para></listitem>
lots of memory and disk space is a good idea in that case.</para></listitem>
<listitem><para>If Wireshark is running out of memory it crashes,
see: <ulink url="http://wiki.wireshark.org/KnownBugs/OutOfMemory"/>
for details and workarounds</para></listitem>
<listitem><para>Wireshark won't benefit much from Multiprocessor/Hyperthread
systems (except perhaps during an "Update list of packets in real time"
capture, where capturing traffic runs in one process and dissecting and
displaying packets runs in another process, and the two processes could
run on two processors).</para></listitem>
systems as time consuming tasks like filtering packets are single threaded.
No rule without exception: during an "Update list of packets in real
time" capture, capturing traffic runs in one process and dissecting and
displaying packets runs in another process - which should benefit from two
processors.</para></listitem>
</itemizedlist>
</para>
</section>
@ -210,14 +210,14 @@
<para>
<itemizedlist>
<listitem><para>Windows 2000, XP Home, XP Pro, XP Tablet PC, XP Media
Center or Server 2003 (XP Pro recommended)
Center, Server 2003 or Vista (XP Pro recommended)
</para></listitem>
<listitem><para>32-bit Pentium or alike (recommended: 400MHz or greater),
64-bit processors in WoW64 emulation, see remarks below
64-bit processors in WoW64 emulation - see remarks below
</para></listitem>
<listitem><para>128MB RAM system memory (recommended: 256MBytes or greater)
<listitem><para>128MB RAM system memory (recommended: 256MBytes or more)
</para></listitem>
<listitem><para>60MB available disk space (plus size of user's capture
<listitem><para>75MB available disk space (plus size of user's capture
files, e.g. 100MB extra)
</para></listitem>
<listitem><para>800*600 (1280*1024 or higher recommended) resolution with
@ -242,15 +242,18 @@
Remarks:
<itemizedlist>
<listitem><para>Windows Vista should work, but as it's still beta you
might encounter new bugs
</para></listitem>
<listitem><para>Windows 95, 98, ME and NT won't work with Wireshark.
<listitem><para>Windows 95, 98 and ME will no longer work with Wireshark.
The last known version to work was Ethereal 0.99.0 (which includes
WinPcap 3.1).
The libraries Wireshark depends on are no longer supporting these systems.
BTW: Microsoft no longer supports 98/ME since July 11, 2006!
</para></listitem>
<listitem><para>Windows NT 4.0 will no longer work with Wireshark.
The last known version to work was Wireshark 0.99.4 (which includes
WinPcap 3.1).
The libraries Wireshark depends on are no longer supporting this system.
BTW: Microsoft no longer supports NT 4.0 since December 31, 2005!
</para></listitem>
<listitem><para>Windows CE and the embedded (NT/XP) versions are not
supported!
</para></listitem>