* doc/release_notes_2.0.2.txt: Update for final release

* doc/guide.tex: Windows binary installer requires MSVC++ 5
* doc/guide.html: Likewise

SVN Revision: 1548

diff --git a/ChangeLog b/ChangeLog
index 56963eb7085abb0c217bfb434585abf43a5093a3..112621ed8f76b26bb3998473ef47665d246e197a 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+2008-08-26  Badlop  <badlop@process-one.net>
+
+       * doc/release_notes_2.0.2.txt: Update for final release
+
+       * doc/guide.tex: Windows binary installer requires MSVC++ 5
+       * doc/guide.html: Likewise
+
 2008-08-26  Christophe Romain  <christophe.romain@process-one.net>
 
        * src/mod_pubsub/mod_pubsub.erl: get_items bugfix (EJAB-716)

diff --git a/doc/guide.html b/doc/guide.html
index 95111ef00c6614f5b255474931a98b977d9e04c4..960e8e6daee786f3c2e4cb75bd784d7121cb755f 100644 (file)
--- a/doc/guide.html
+++ b/doc/guide.html
@@ -290,7 +290,13 @@ go to the Windows service settings and set ejabberd to be automatically started.
 Note that the Windows service is a feature still in development, 
 and for example it doesn&#X2019;t read the file ejabberdctl.cfg.</P><P>On a *nix system, if you want ejabberd to be started as daemon at boot time, 
 copy <TT>ejabberd.init</TT> from the &#X2019;bin&#X2019; directory to something like <TT>/etc/init.d/ejabberd</TT>
-(depending on your distribution) and call <TT>/etc/inid.d/ejabberd start</TT> to start it.</P><P>If <TT>ejabberd</TT> doesn&#X2019;t start correctly and a crash dump is generated,
+(depending on your distribution) and call <TT>/etc/inid.d/ejabberd start</TT> to start it.</P><P>If <TT>ejabberd</TT> doesn&#X2019;t start correctly in Windows,
+try to start it using the shortcut in desktop or start menu.
+If the window shows error 14001, the solution is to install:
+"Microsoft Visual C++ 2005 SP1 Redistributable Package".
+You can download it from
+<A HREF="http://www.microsoft.com/">www.microsoft.com</A>.
+Then uninstall <TT>ejabberd</TT> and install it again.</P><P>If <TT>ejabberd</TT> doesn&#X2019;t start correctly and a crash dump is generated,
 there was a severe problem.
 You can try starting <TT>ejabberd</TT> with
 the script <TT>bin/live.bat</TT> in Windows,

diff --git a/doc/guide.tex b/doc/guide.tex
index b6d317ae62314e423a999bc0ef0c650ee3c13871..389cd2305855ffbf51892fae6831c8c3bb816e43 100644 (file)
--- a/doc/guide.tex
+++ b/doc/guide.tex
@@ -241,6 +241,14 @@ On a *nix system, if you want ejabberd to be started as daemon at boot time,
 copy \term{ejabberd.init} from the 'bin' directory to something like \term{/etc/init.d/ejabberd}
 (depending on your distribution) and call \term{/etc/inid.d/ejabberd start} to start it.
 
+If \term{ejabberd} doesn't start correctly in Windows,
+try to start it using the shortcut in desktop or start menu.
+If the window shows error 14001, the solution is to install:
+"Microsoft Visual C++ 2005 SP1 Redistributable Package".
+You can download it from
+\footahref{http://www.microsoft.com/}{www.microsoft.com}.
+Then uninstall \ejabberd{} and install it again.
+
 If \term{ejabberd} doesn't start correctly and a crash dump is generated,
 there was a severe problem.
 You can try starting \term{ejabberd} with

diff --git a/doc/release_notes_2.0.2.txt b/doc/release_notes_2.0.2.txt
index 876a0836a8ee47bc819198041a9d305c3b179498..94df3cc8a6a4d35de8f64d297baafe5ee686ad93 100644 (file)
--- a/doc/release_notes_2.0.2.txt
+++ b/doc/release_notes_2.0.2.txt
@@ -1,11 +1,11 @@
 
                               Release Notes
-                             ejabberd 2.0.2-beta1
-                               1 August 2008
+                             ejabberd 2.0.2
+                             27 August 2008
 
   ejabberd 2.0.2 is the second bug fix release for ejabberd 2.0.x branch.
 
-  ejabberd 2.0.2 includes a new feature, 5 improvements and 30 bugfixes.
+  ejabberd 2.0.2 includes many bugfixes and a few improvements.
   A complete list of changes can be retrieved from:
      http://redir.process-one.net/ejabberd-2.0.2
 
@@ -26,9 +26,9 @@
 - Binary installers: SMP on Windows; don't remove config when uninstalling.
 
 
-  Bugs report
+  Bug reports
 
-  You can officially report bugs on Process-one support site:
+  You can officially report bugs on ProcessOne support site:
   http://support.process-one.net/
 
 END