bk commit - mysqldoc tree (Mike.Hillyer:1.2891)

[mhillyer]

Below is the list of changes that have just been committed into a local
mysqldoc repository of root. When root does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.2891 05/04/26 09:43:08 Mike.Hillyer@stripped +1 -0
  Updated windows troubleshooting section to remind users that their old config file is breaking their new install.

  Docs/manual.texi
    1.2728 05/04/26 09:43:05 Mike.Hillyer@stripped +14 -1
    Updated windows troubleshooting section to remind users that their old config file is breaking their new install.

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	Mike.Hillyer
# Host:	www.openwin.org
# Root:	/home/mysqldoc/mysqldoc

--- 1.2727/Docs/manual.texi	2005-04-25 05:45:32 -06:00
+++ 1.2728/Docs/manual.texi	2005-04-26 09:43:05 -06:00
@@ -6527,6 +6527,8 @@
 The following are examples of some of the more common error messages you may
 encounter when installing MySQL and starting the server for the first time:
 
+@itemize @bullet
+@item
 @example
 System error 1067 has occurred.
 Fatal error: Can't open privilege tables: Table 'mysql.host' doesn't exist
@@ -6536,7 +6538,13 @@
 privileges database or other critical files. This error is often encountered
 when the MySQL base or data directories are installed in different
 locations than the default locations (@file{C:\mysql} and
-@file{C:\mysql\data}, respectively).
+@file{C:\mysql\data}, respectively). 
+
+One situation when this may occur is when 
+MySQL is upgraded and installed to a new location, but the configuration file
+is not updated to reflect the new install location. In addition there may be old
+and new configuration files that conflict, be sure to delete or rename any 
+old configuration files when upgrading MySQL.
 
 If you have installed MySQL to a directory other than @file{C:\mysql} you
 need to ensure that the MySQL server is aware of this through the use of a
@@ -6578,6 +6586,8 @@
 
 @xref{Windows create option file}.
 
+
+@item
 @example
 Error: Cannot create Windows service for MySql. Error: 0
 @end example
@@ -6599,6 +6609,9 @@
 C:\>sc delete mysql
 [SC] DeleteService SUCCESS
 @end example
+
+
+@end itemize
 
 @node Windows upgrading, Windows vs Unix, Windows troubleshooting, Windows installation
 @subsection Upgrading MySQL on Windows