My $.02. I bundle MySQL with another product I sell. To get my distributable packages, I use the raw executables anyway, so the "mysql-4.1.7-win-noinstall.zip" package will work for me. (My product line is still using the 4.0 series.) The old installer never seemed to much more than a self-extracting zip file anyway.

If there is something I think Windows MySQL installers should be annoyed with, it would seem to be the "if you are using MySQL 4.1.5 or earlier, you must UNINSTALL before running this spiffy new installation" statement. That just looks like lazy installation coding.

BTW, here's the page with info about the 4.1 Windows installer if you're interested. (http://dev.mysql.com/tech-resources/articles/4.1/installer.html)

And now I'm just going to go off on my own rant...

People will find in serious production environments will probably find the default location of "C:\Program Files\MySQL\MySQL Server 4.1" annoying. It's common these days to keep the OS on C: and put the DB on a separate D: partition...something which people may feel unwilling to do if the default location is in Program Files.

This quote made me chuckle: "Using 'Developer Machine' will assign 12% of the available memory to MySQL which is quite sufficient for development. " Is it really that common to develop against mickey-mouse tables? And people wonder why their applications don't scale in production...

This quote is kind of disturbing to a fellow who constantly needs to sell MySQL against SQL Server in front of security teams: "Another feature that is available after a new installation is an anonymous account that allows guests to connect to the server. " Thanks, but no thanks, guys.

And finally...will 4.1 finally let me run MySQL as a service under a non-Administator Windows account? That remains the one MySQL-on-Windows security problem which keeps me awake at night, and I didn't see mention of a "run as user" field in the new installer description...

That is all.

At 08:54 AM 12/15/2004, SGr...@unimin.com wrote: