MySQL Bugs: #4687: Problem starting the MySQL service under windows XP Home

Bug #4687	Problem starting the MySQL service under windows XP Home
Submitted:	22 Jul 2004 2:59	Modified:	22 Jul 2004 4:08
Reporter:	Christopher Bird	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	4.0.20a-nt	OS:	Windows (Windows XP)
Assigned to:		CPU Architecture:	Any

Description:
I installed MySQL onto the C: drive of my laptop. I also configured the data directory to be on the C: drive. After installation, I realized that I would have preferred the data directory to be on the D: drive. No problem, I thought. Simply start the server with the --datadir d:/mysql/data option and all will be well. That does work, except I have the following issue:

The installation created a service which is executed on startup. If i try to customize the service by adding the --datadir d:/mysql/data option, in the properties for the service, it does not take permanently. I can stop the service, type in the --datadir d:/mysql/data value into the start parameter field for the service and then do a manual start. It is fine then. But if I try to apply that change and have it do this permanently, no luck.  BTW the service that starts is c:/mysql/bin/mysql-nt.exe.

If I edit the registry to make the --datadir d:/mysql/data a parameter to the service, the start of the service hangs. I don't have an error cod for this, sorry. The event log is cleared now.

Any help would be greatly appreciated.

regards

Chris Bird

How to repeat:
It happens on every startup on my system

Suggested fix:
Make the service accept start parameters

If you want to change the executable location for the service, you
must need to remove the first service installed:

  mysqld-nt --remove or mysqld-nt --remove service_custom_name

and re-install the service from the executable location:

  mysqld-nt --install or mysqld-nt --install custom_service_name

and to edit the my.ini file e.g.:

[mysqld]
basedir=d:/mysql
datadir=d:/mysql/data

Thanks. Worked perfectly