Update README.md

[oweals/nmrpflash.git] / README.md

diff --git a/README.md b/README.md
index 468cec0c3c910245030f6735775a6571cc9c3852..bc9a31b4bd11d4b52a1cdd7462cff275c05a5897 100644 (file)
--- a/README.md
+++ b/README.md
@@ -9,6 +9,9 @@ tested with a Netgear EX2700, but is likely to work on many others as well.
 Prebuilt binaries for Linux, OS X and Windows are available
 [here](https://github.com/jclehner/nmrpflash/releases).
 
+To run `nmrpflash` on Windows, install
+[WinPcap](https://www.winpcap.org/install/default.htm).
+
 ````
 Usage: nmrpflash [OPTIONS...]
 
@@ -36,7 +39,7 @@ the Netgear router.
 
 For this example, we'll assume that your network interface is `eth0`.
 First, we have to assign a static IP address to our network interface.
-In this example, we'll use `192.168.1.2`. All available network interfaces 
+In this example, we'll use `192.168.1.2`. All available network interfaces
 can be listed using
 
 ````
@@ -49,6 +52,8 @@ to be a *free* IP address from the same subnet as the one used by your
 network interface. We'll use `192.168.1.254`. The firmware image file
 can usually be downloaded directly from Netgear's FTP servers.
 
+Power on your device immediately after starting `nmrpflash`.
+
 ````
 $ nmrpflash -i eth0 -a 192.168.1.254 -f EX2700-V1.0.1.8.img
 Advertising NMRP server on eth0 ... /
@@ -60,18 +65,18 @@ Remote finished. Closing connection.
 ````
 
 ### Common issues
-###### No suitable network interfaces found.
+###### "No suitable network interfaces found."
 
 If you're *not* on Windows, rerun `nmrpflash -L` using `sudo`. In any case,
 use `-vvvL` to see more detailed messages, and file a bug report if applicable.
 
-###### No response after 60 seconds. Bailing out.
+###### "No response after 60 seconds. Bailing out."
 
 The router did not respond. Try running `nmrpflash` with `-m` and specify
 your router's MAC address. It's also entirely possible that your device does
 not support the NMRP protocol.
 
-###### Timeout while waiting for 0x04.
+###### "Timeout while waiting for 0x04."
 
 After a successful file upload, `nmrpflash` waits for up to 120 seconds for an
 answer from your device. You can increase this by specifying a longer timeout
@@ -89,9 +94,9 @@ $ make && sudo make install
 
 ###### Windows
 
-The repository includes a 
+The repository includes a
 [DevCpp](http://sourceforge.net/projects/orwelldevcpp/)
-project file (`nmrpflash.dev`). Download the latest 
-[WinPcap Developer Pack](http://www.winpcap.org/devel.htm) 
+project file (`nmrpflash.dev`). Download the latest
+[WinPcap Developer Pack](https://www.winpcap.org/devel.htm)
 and extract it into the root folder of the nmrpflash sources.