Bug #12219 mysqld-nt.exe usage verses mysqld-max-nt.exe usage during WinXP MSI Install

Description:
When following the MSI Installer configuration instructions, when asked to have MySQL Installed upon a computer which will be dedicated as a MySQL server only [not a mixed apache server and MySQL server, etc...], the installation installs MySQL with all of the other options correctly.  It runs fine.  However, when using MySQL Administrator in tandem with MySQL Server, and upon opening the Service Control=>Configure Service pane, the very bottom field=> Path to Binary:   has an entry in it as follows => c:\w\s\mySql\1_Server\5.0.7b_server\bin\mysqld-max-nt     This entry seems to be pointing to an expected file named mysqld-max-nt.exe located in the bin subdir.   The aforementioned MSI installation only installs a close matching file named   mysqld-nt.exe   however.   The MySQL service crashes without this expected mysqld-max-nt.exe file co-resident in the bin subdir.   Do you know how we can get a copy of this needed file?

To fix this "bug", we simply copied the original file named mysqld-nt.exe and made an exact copy of it in the bin subdir using the name mysqld-max-nt.exe   and the MySQL server works fine.   However, we expect that your designers intended some sort of extra performance from the ACTUAL mysqld-max-nt.exe  file so that a MySQL server running upon a computer dedicated solely to MySQL service support would have better performance from more memory, more cache, etc., etc., etc.  

Background Reason for request for assistance:
We have upgraded from MySQL 3.xxx to your latest 5.0.7b version and are very pleased with your new MySQL Administrator.   We use MySQL databases to perform virtual web hosting "operating system" configuration management for php applications.   Each client request results in our server side php OS performing about 850 milliseconds of background operations using various MySQL databases.   The php scripts consume about 4 megabytes of memory during execution creating a large array of uni-vector databases and cloned-databases upon our servers.  As well as running comprehensive  function trace diagnostics.   Databases not created are created on the fly from structural config files which can be cloned if desired.   Rigorous client AND server crypto-key authentication occurs to assure our server and to assure our clients that each of us is who the other thinks it should be.   Every web request is logged in MySQL databases with comprehensive information about the client.   Given the popularity of phishing and pharming hacking today, we felt this extra overhead performance penalty was required for our virtual web hosting clients.   Then, finally, a session relevant web page is either dynamically generated or copied from cache and sent to the client computer.   So you can see how we would want to squeeze every bit of performance out of your binary=> mysqld-max-nt.exe 

Thanks.

 

How to repeat:
Use windows XP Installer and Install MySQL with the "max" option selected in order to allow MySQL to utilize the computer's resources to the maximum.

Test it with any php mysql code.

Then install MySQL Administrator and use the "configuration" pane as described above.

When "saving" the changes as noted above, the MyQL Service will use windows "automatic" service to restart upon computer bootup and will crash.

Suggested fix:
To fix this "bug", we simply copied the original file named mysqld-nt.exe and made an exact copy of it in the bin subdir using the name mysqld-max-nt.exe   and the MySQL server works fine.   However, we expect that your designers intended some sort of extra performance from the ACTUAL mysqld-max-nt.exe  file so that a MySQL server running upon a computer dedicated solely to MySQL service support would have better performance from more memory, more cache, etc., etc., etc.

I tested this issue with a newest server 5.0.XX and I recommend you
to do too.
However I was unable to repeat the issue you reported or I missed
something from you. Below  what I did:

- Installed the package with the installer and mysql-nt.exe was installed
  and started.
- Launched MySQL Administrator.
- Stopped the service with Service Control -> Start/Stop service
- Then in Configure Service -> Path To Binary selected:
  E:\TestInstall\bin\mysqld-max-nt
  using the ... button at right side.
- Applied the changes

and below the successful log:

Trying to stop the server ...

Server was stopped.

Trying to start the server ...

Could not re-connect to the MySQL Server.
Server was started.

Done by MySQL Administrator.

Thank you for taking the time to report a problem.  Unfortunately
you are not using a current version of the product your reported a
problem with -- the problem might already be fixed. Please download
a new version from http://www.mysql.com/downloads/

If you are able to reproduce the bug with one of the latest versions,
please change the version on this bug report to the version you
tested and change the status back to "Open".  Again, thank you for
your continued support of MySQL.

Additional info:

I've just reinstalled latest 5.0.11 several times on different XP machines (in a manner very close to those you described), and I have mysqld-max-nt.exe in the bin subdirectory of the installation directory I selected.