setting up mysql

[tonderai76]

I have php and apache set up on my desktop , for my testing server. since port 80 was not accessible, I had to configure my apache server to use port 8080. i have tested these settings and both apache and PHP are working fine. the problem starts with mysql. i have installed mysql to the default C:\MySQL . i can not start mysql.i always get the error "cannot connect to localhost (10061)" . i searched for solutions to this error, but most solutions on the forum didnt work for my particular problem. would this have anything to do with my localhost being localhost:8080, instead of the default localhost on port 80. is there any way of pointing mysql to localhost:8080
I have windows XP,php,apache
i would really appreciate any form of help

[Stephen Philbin]

Why is port 80 not available? If it's because of your router just use port fowarding. ;)

Not reallt sure on the exact process of sorting mysql on windows, but it sounds quite similar to the Linux one. You're using the right user accounts to start and stop the server right? And you set the file ownership to the right users too?

[ray326]

Just because it's installed doesn't mean it's running.

[Stephen Philbin]

Oh yeah. I thought (s)he said (s)he'd started the server. You've got to start it up. Read the instructions fool! *slap* (just havin' fun with ya, relax. ;) )

Yeah just read the instructions that I'm assuming came with it and follow them step by step. Read them properly withought rushing through them and you should have the server running reasonably quickly.

[ray326]

It's not a really obvious step for a newbie. In fact a lot of people with a lot of non-server experience miss that kind of thing; especially on Windows where most servers are installed to auto start.

[Stephen Philbin]

Yup. I didn't even realise the mysql server was a server at first. I'd seen "mysql server" mentioned before, but I assumed it to be an alternative to Apache. Some sort of massive scale server that acted as a sort of http/query hybrid server. I assumed standard mysql was merely an interface type language that just allowed server side languages to create and mainuplate files. I even thought I'd installed the wrong thing when I got to the steps in the instructions that said to start it. I continued anyway, carefully remembering everything I had done and all the intructions etc. It all became clear once I'd finished the whole process.

I know it may seem very boring Tonderai, but try and read as much documentation that came with the server as possible. I used to just install stuff willy-nilly on Windows, never reading any documentation (as we all do because it is rarely needed), but when I stopped and started to read as much as I could (mostly because I had no choice due to being on a strange new operating system), I found I not only learned to swiftly operate my software, but I also picked up handy little tips I could apply to many other things too. :D

It really does pay to read yer docs. Especially when it comes to software like this. When you're a user, rather than an administrator of this stuff it's all too easy to fall into that trap of believing "it just works". Then when we come to administrate it, we wonder why it doesn't. lol

[tonderai76]

thanx guys for your help.
i managed to fix the problem and now my whole WAMP setup is up and running. theproblem was the my.ini file. the standard my.ini file that is created with version 4 mysql wetups, includes info on sarting InoDB tables. in older versions 'like version 3 and below, you had to start up and configure InoDB table support manually. so, i deleted everything in the my.ini file and only put in the basic information. just the location of the mysql server and it started working well. remove all the stuff like bind host name, "port 3306". all you need is

[mysql]
the location of mysql
the location of the data folder

thats all, nothing more