Log Message:
-----------
Documentation for Windows.

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        installation.sgml (r1.15 -> r1.16)
        prerequisites.sgml (r1.21 -> r1.22)
        startslons.sgml (r1.11 -> r1.12)

-------------- next part --------------
Index: startslons.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/startslons.sgml,v
retrieving revision 1.11
retrieving revision 1.12
diff -Ldoc/adminguide/startslons.sgml -Ldoc/adminguide/startslons.sgml -u -w -r1.11 -r1.12
--- doc/adminguide/startslons.sgml
+++ doc/adminguide/startslons.sgml
@@ -6,7 +6,11 @@
 
 <para>You need to run one <xref linkend="slon"> instance for each node
 in a &slony1; cluster, whether you consider that node a
-<quote>master</quote> or a <quote>slave</quote>. Since a <command>MOVE
+<quote>master</quote> or a <quote>slave</quote>. On Windows when 
+running as a service things are slightly different. One slon service
+is installed, and a seperate configuration file registered for each
+node to be serviced by that machine. The main service then manages 
+the individual slons itself. Since a <command>MOVE
 SET</command> or <command>FAILOVER</command> can switch the roles of
 nodes, slon needs to be able to function for both providers and
 subscribers.  It is not essential that these daemons run on any
Index: installation.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/installation.sgml,v
retrieving revision 1.15
retrieving revision 1.16
diff -Ldoc/adminguide/installation.sgml -Ldoc/adminguide/installation.sgml -u -w -r1.15 -r1.16
--- doc/adminguide/installation.sgml
+++ doc/adminguide/installation.sgml
@@ -2,6 +2,12 @@
 <sect1 id="installation">
 <title>&slony1; Installation</title>
 
+<para>Note for <trademark>Windows</trademark> users:
+Unless you are planning on hacking the &slony1; code, it is highly
+recommended that you download and install a prebuilt binary 
+distribution and jump straight to the configuration section below.
+</para>
+
 <para>You should have obtained the &slony1; source from the previous
 step. Unpack it.</para>
 
@@ -162,6 +168,39 @@
 
 </sect2>
 
+<sect2>
+<title> Installing the &slony1; service on <trademark>Windows</trademark></title>
+
+<para> On <trademark>Windows</trademark> systems instead of running one
+slon daemon per node, a single slon service is installed which can then be
+controlled through the <program>Services</program> control panel applet, or
+from a command prompt using the <program>net</program> command.</para>
+
+<screen>
+C:\Program Files\PostgreSQL\8.0\bin> slon -regservice my_slon
+Service registered.
+Before you can run Slony, you must also register an engine!
+
+WARNING! Service is registered to run as Local System. You are
+encouraged to change this to a low privilege account to increase
+system security. 
+</screen>
+
+<para> Once the service is installed, individual nodes can be setup
+by registering slon configuration files with the service.</para>
+
+<screen>
+C:\Program Files\PostgreSQL\8.0\bin> slon -addengine c:\node1.conf
+Engine added.
+</screen>
+
+<para>Other, self explanatory commands include <command>slon -unregservice 
+&lt;service name&gt;</command>, <command>slon -listengines 
+&lt;service name&gt;</command> and <command>slon -delengine 
+&lt;service name&gt; &lt;config file&gt;</command>.</para> 
+
+</sect2>
+
 </sect1>
 
 <!-- Keep this comment at the end of the file
Index: prerequisites.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/prerequisites.sgml,v
retrieving revision 1.21
retrieving revision 1.22
diff -Ldoc/adminguide/prerequisites.sgml -Ldoc/adminguide/prerequisites.sgml -u -w -r1.21 -r1.22
--- doc/adminguide/prerequisites.sgml
+++ doc/adminguide/prerequisites.sgml
@@ -8,29 +8,9 @@
 this release are FreeBSD-4X-i368, FreeBSD-5X-i386, FreeBSD-5X-alpha,
 OS-X-10.3, Linux-2.4X-i386 Linux-2.6X-i386 Linux-2.6X-amd64,
 <trademark>Solaris</trademark>-2.8-SPARC,
-<trademark>Solaris</trademark>-2.9-SPARC, AIX 5.1 and
-OpenBSD-3.5-sparc64.</para>
-
-<para>There have been reports of success at running &slony1; hosts
-that are running PostgreSQL on Microsoft
-<trademark>Windows</trademark>.  As of version 1.1.0, the
-<quote>binary</quote> applications (<emphasis>e.g.</emphasis> - <xref
-linkend="slonik">, <xref linkend="slon">) do not run on
-<trademark>Windows</trademark>, but a <xref linkend="slon"> running on
-one of the Unix-like systems has no reason to have difficulty
-connecting to a PostgreSQL instance running on
-<trademark>Windows</trademark>. </para>
-
-<para> It ought to be possible to port <xref linkend="slon"> and <xref
-linkend="slonik"> to run on <trademark>Windows</trademark>; the
-conspicuous challenge is of having a POSIX-like
-<filename>pthreads</filename> implementation for <xref
-linkend="slon">, as it uses that to have multiple threads of
-execution.  There are reports of there being a
-<filename>pthreads</filename> library for
-<trademark>Windows</trademark>, and it is anticipated that
-<trademark>Windows</trademark> support will be introduced in some
-future release.</para>
+<trademark>Solaris</trademark>-2.9-SPARC, AIX 5.1,
+OpenBSD-3.5-sparc64 and <trademark>Windows</trademark> 2000, XP and 
+2003 (32 bit).</para>
 
 <sect2>
 <title> &slony1; Software Dependancies</title>
@@ -99,6 +79,14 @@
 </ulink> along with <ulink url="http://openjade.sourceforge.net/">
 OpenJade.</ulink> </para></listitem>
 
+<listitem><para> On <trademark>Windows</trademark> you will also need the
+same <ulink url=
+"http://www.postgresql.org/docs/faqs.FAQ_MINGW.html">MinGW/Msys 
+Toolset</ulink> used to build PostgreSQL 8.0 and above.
+In addition you will need to install <ulink url=
+"http://sourceware.org/pthreads-win32/">pthreads-win32 2.x</ulink>. 
+</para></listitem>
+
 </itemizedlist> </para>
 
 <para>Also check to make sure you have sufficient disk space.  You