Archive: The dreaded MySQL again!


The dreaded MySQL again!
Hi folks,
I am new to NSIS having used it sucessfully only last week. I have also read the many messages posted here about MySQL and about reading/writing .ini files.

1.. When MySQL installs it does not create the .ini file in the Windows directory. I can see form teh docs how to read and write an ini file, but how do I create it from NSIS in the first place?

2.. Would it be best if I had an empty .ini file in my distribution and then modified it with NSIS?

3.. I can't control where the user installs MySQL, so how do I find where it is? If I use 'IfFileExists' to find mysql.exe does this cover all drives on the machine?

4.. How do I detect if the machine I am installing on is Windows 98? As there is no 'service' capability on Win98 I will have to figure out how to set ..\mysqld.exe as a start-up option so the server is available.

My apologies for so many questions in one go! I hope someone has a few moments to help me :)

John
(Toronto - Canada)


1. WriteINIStr writes to existing INI files and creates new ones.

2. ...

3. Surely the mySQL installation will store registry entries for the installation location. Try searching your registry for e.g. "mySQL" using RegEdit

4. See NSIS CHM manual, section "Useful Scripts" > "C.5 Get Windows version"

-Stu