diff --git a/docs/nmap-install.xml b/docs/nmap-install.xml index 6206f3bdc..e4b763b51 100644 --- a/docs/nmap-install.xml +++ b/docs/nmap-install.xml @@ -709,8 +709,8 @@ distributed for each major Nmap release. We support Nmap on Windows 7 and newer, as well as Windows Server 2008 and newer. We also maintain a guide for users -who must run Nmap on earlier Windows releases. While it has improved dramatically, the Windows port is not -quite as efficient as on Unix. Here are the known limitations: +who must run Nmap on earlier Windows releases. +Nmap runs equally well on Windows as on Unix in nearly every way, though there are a couple of known limitations: Windowslimitations of @@ -740,14 +740,14 @@ packets. Windowsperformance of Scan speeds on Windows are generally comparable to those on Unix, though the latter often has a slight performance edge. One -exception to this is connect scan (), which is -often much slower on Windows because of deficiencies in the Windows -networking API. This is a shame, since that is the one TCP scan that -works over all networking types (not just ethernet, like the raw packet scans). -Connect scan performance can be -improved substantially by applying the Registry changes in the -nmap_performance.reg file included with Nmap. By default these changes are applied for you by the Nmap executable installer. This registry file -is in the nmap-version +example of this is connect scan (), which may be +slower on Windows because of different limits in the Windows +networking API. Since this is the one TCP scan that +works over all networking types (not just ethernet, like the raw packet scans), +Nmap includes a collection of Registry changes that substantially improve connect scan performance. +By default these changes are applied for you by the Nmap executable installer, and are also available in the +nmap_performance.reg file +in the nmap-version directory of the Windows binary zip file (for Nmap OEM customers), and nmap-version/mswin32 in the source tarball (where version is the @@ -937,20 +937,14 @@ detailed instructions for users who are unfamiliar with command-line interfaces: -Make sure the user you are logged in as has -administrative privilegesprivileged users -on the computer (user should be a member of the administrators group). -Open a command/DOS Window. Though it can be found in -the program menu tree, the simplest approach is to choose Start --> Run and type cmd<enter>. Opening a Cygwin window (if you installed it) by clicking on the Cygwin icon on the desktop works too, although the necessary commands differ slightly from those shown here. -Change to the directory you installed Nmap into. You can skip this step if Nmap is already in your command path (the Zenmap isntaller adds it there by default). Otherwise, type the following commands. +Open Terminal, PowerShell, or Command Prompt. If you are using MSYS2, Cygwin, or WSL, +the necessary commands differ slightly from those shown here. +Change to the directory you installed Nmap into. You can skip this step if Nmap is already in your command path (the installer adds it there by default). Otherwise, type the following commands. c: cd "\Program Files (x86)\Nmap" -On Windows releases prior to Windows 7, specify \Program Files\Nmap instead. The directory will also be different if you chose to install Nmap in a non-default location. - Execute nmap.exe. is a screen shot showing a simple example. @@ -960,10 +954,10 @@ the program menu tree, the simplest approach is to choose Start - + - +