more updated to reflect install location changes

diff --git a/win32utils/readme1st.txt b/win32utils/readme1st.txt
index 2e3f1b058f4a77b7200a67d7bb20a49e27e2d1a2..7528527e0b5778bc9d8e6c2bbe7778d42934c17b 100644 (file)
--- a/win32utils/readme1st.txt
+++ b/win32utils/readme1st.txt
@@ -40,14 +40,14 @@ required for the "named" account.
 
 It is important that on Windows the directory directive is used in
 the options section to tell BIND where to find the files used in
-named.conf (default %ProgramFiles%\ISC BIND 9\etc\named.conf). For
+named.conf (default "%ProgramFiles%\ISC BIND 9\etc\named.conf"). For
 example:
 
        options {
                directory "C:\Program Files (x86)\ISC BIND 9\etc";
        };
 
-for a 32 bit BIND on a 64 bit US Domestic indows system.
+for a 32 bit BIND on a 64 bit US Domestic Windows system.
 Messages are logged to the Application log in the EventViewer.
 
 CONTROLLING BIND:
@@ -56,22 +56,23 @@ Windows uses the same rndc program as is used on Unix systems.  The
 rndc.conf file must be configured for your system in order to work.
 You will need to generate a key for this. To do this use the
 rndc-confgen program. The program will be installed in the same
-directory as named: dns\bin.  From the DOS prompt, use the command
-this way:
+directory as named: "%ProgramFiles%\ISC BIND 9\bin".  From the DOS
+prompt, use the command this way:
 
 rndc-confgen -a
 
-which will create a rndc.key file in the dns\etc directory. This will
-allow you to run rndc without an explicit rndc.conf file or key and
-control entry in named.conf file. See section 3.4.1.2 of the ARM for
-details of this. An rndc.conf can also be generated by running:
+which will create a rndc.key file in the "%ProgramFiles%\ISC BIND 9\etc"
+directory. This will allow you to run rndc without an explicit
+rndc.conf file or key and control entry in named.conf file. See
+section 3.4.1.2 of the ARM for details of this. An rndc.conf can
+also be generated by running:
 
 rndc-confgen > rndc.conf
 
 which will create the rndc.conf file in the current directory, but
-not copy it to the dns\etc directory where it needs to reside. If
-you create rndc.conf this way you will need to copy the same key
-statement into named.conf.
+not copy it to the "%ProgramFiles%\ISC BIND 9\etc" directory where
+it needs to reside. If you create rndc.conf this way you will need
+to copy the same key statement into named.conf.
 
 The additions look like the following:
 
@@ -124,7 +125,7 @@ named-checkzone, named-compilezone, named-journalprint,
 dnssec-importkey, dnssec-keygen, dnssec-signzone, dnssec-dsfromkey,
 dnssec-keyfromlabel, dnssec-revoke, dnssec-settime and
 dnssec-verify.  The latter tools are for use with DNSSEC.  All tools
-are installed in the dns\bin directory.
+are installed in the %ProgramFiles%\"ISC BIND 9"\bin directory.
 
 IMPORTANT NOTE ON USING THE TOOLS:
 
@@ -134,9 +135,9 @@ information. However, if you do create a resolv.conf file as follows,
 the tools will use it in preference to the registry name server
 entries.
 
-Place resolv.conf the "ISC BIND 9"\etc directory. It must
-contain a list of recursive server addresses.  The format of this
-file is:
+Place resolv.conf the "%ProgramFiles%\ISC BIND 9\etc" directory.
+It must contain a list of recursive server addresses.  The format
+of this file is:
 
 nameserver 1.2.3.4
 nameserver 5.6.7.8