The only thing that could have affected my installation of MySQL is me
trying out another Windows-Apache-MySQL-PHP package (WAMP5 from
http://www.wampserver.com/en/).

Anyway, I thought it would not bother my current installation, because
most of these packages install to a directory local to their package.

Well, before and after removing it, I can fire up MySQL in the same
fashion I always did:

"%windir%\system32\net.exe" start MySql

That command from my editor, fires up the MySQL (the original one), yet
I cannot connect anymore. Error (2003) 10061. I have searched and
researched different fixes at MySQL.com, and still cannot get a
connection to MySQL.

Any recommendations on how I might fix my problem?

--
-Lost
Remove the extra words to reply by e-mail. Don't e-mail me. I am
kidding. No I am not.

"-Lost" <maventheextrawords@techie.com> wrote in message
news:dsqdnfNwWoOwJ9LbnZ2dnUVZ_sWdnZ2d@comcast.com. ..
> The only thing that could have affected my installation of MySQL is me
> trying out another Windows-Apache-MySQL-PHP package (WAMP5 from
> http://www.wampserver.com/en/).
>
> Anyway, I thought it would not bother my current installation, because
> most of these packages install to a directory local to their package.
>
> Well, before and after removing it, I can fire up MySQL in the same
> fashion I always did:
>
> "%windir%\system32\net.exe" start MySql
>
> That command from my editor, fires up the MySQL (the original one), yet I
> cannot connect anymore. Error (2003) 10061. I have searched and
> researched different fixes at MySQL.com, and still cannot get a connection
> to MySQL.
>
> Any recommendations on how I might fix my problem?
>

I have no idea. Sorry.

Make sure mysql is actually started and then make sure the pipe/name didn't
change. Installing other versions on top can screw things up as I recently
had a similar issue with php. I had to uninstall everything and reinstall
it(Which you might try).

What happens is when you install something that and then uninstall it, it
won't restore everything the way it was original(which is also not
necessarily a good thing in some cases). But it can leave dangling
references and stuff that need to be fixed. Chances are that is what
happened.

If you cannot connect at all to mysql but it is running then you need to
make sure the ports and pipe/names have no changed.

Jon

Jon Slaughter wrote:
> "-Lost" <maventheextrawords@techie.com> wrote in message
> news:dsqdnfNwWoOwJ9LbnZ2dnUVZ_sWdnZ2d@comcast.com. ..
>> The only thing that could have affected my installation of MySQL is me
>> trying out another Windows-Apache-MySQL-PHP package (WAMP5 from
>> http://www.wampserver.com/en/).
>>
>> Anyway, I thought it would not bother my current installation, because
>> most of these packages install to a directory local to their package.
>>
>> Well, before and after removing it, I can fire up MySQL in the same
>> fashion I always did:
>>
>> "%windir%\system32\net.exe" start MySql
>>
>> That command from my editor, fires up the MySQL (the original one), yet I
>> cannot connect anymore. Error (2003) 10061. I have searched and
>> researched different fixes at MySQL.com, and still cannot get a connection
>> to MySQL.
>>
>> Any recommendations on how I might fix my problem?
>>
>
> I have no idea. Sorry.
>
> Make sure mysql is actually started and then make sure the pipe/name didn't
> change. Installing other versions on top can screw things up as I recently
> had a similar issue with php. I had to uninstall everything and reinstall
> it(Which you might try).
>
> What happens is when you install something that and then uninstall it, it
> won't restore everything the way it was original(which is also not
> necessarily a good thing in some cases). But it can leave dangling
> references and stuff that need to be fixed. Chances are that is what
> happened.
>
> If you cannot connect at all to mysql but it is running then you need to
> make sure the ports and pipe/names have no changed.

Gotcha! Now, how do I insure that? In php.ini I do have the MySQL
default port setting at 3306; in MySQL's my.ini says port 3306.

I am not entirely sure what you meant by "pipes/names?"

--
-Lost
Remove the extra words to reply by e-mail. Don't e-mail me. I am
kidding. No I am not.

"-Lost" <maventheextrawords@techie.com> wrote in message
news:uvCdnYhNMbzCXdLbnZ2dnUVZ_q2pnZ2d@comcast.com. ..
> Jon Slaughter wrote:
>> "-Lost" <maventheextrawords@techie.com> wrote in message
>> news:dsqdnfNwWoOwJ9LbnZ2dnUVZ_sWdnZ2d@comcast.com. ..
>>> The only thing that could have affected my installation of MySQL is me
>>> trying out another Windows-Apache-MySQL-PHP package (WAMP5 from
>>> http://www.wampserver.com/en/).
>>>
>>> Anyway, I thought it would not bother my current installation, because
>>> most of these packages install to a directory local to their package.
>>>
>>> Well, before and after removing it, I can fire up MySQL in the same
>>> fashion I always did:
>>>
>>> "%windir%\system32\net.exe" start MySql
>>>
>>> That command from my editor, fires up the MySQL (the original one), yet
>>> I cannot connect anymore. Error (2003) 10061. I have searched and
>>> researched different fixes at MySQL.com, and still cannot get a
>>> connection to MySQL.
>>>
>>> Any recommendations on how I might fix my problem?
>>>
>>
>> I have no idea. Sorry.
>>
>> Make sure mysql is actually started and then make sure the pipe/name
>> didn't change. Installing other versions on top can screw things up as I
>> recently had a similar issue with php. I had to uninstall everything and
>> reinstall it(Which you might try).
>>
>> What happens is when you install something that and then uninstall it, it
>> won't restore everything the way it was original(which is also not
>> necessarily a good thing in some cases). But it can leave dangling
>> references and stuff that need to be fixed. Chances are that is what
>> happened.
>>
>> If you cannot connect at all to mysql but it is running then you need to
>> make sure the ports and pipe/names have no changed.
>
> Gotcha! Now, how do I insure that? In php.ini I do have the MySQL
> default port setting at 3306; in MySQL's my.ini says port 3306.
>
> I am not entirely sure what you meant by "pipes/names?"


Not quite sure ;/

When you install the server it usually installs it under MYSQL I think. The
named pipe is something you can use to connect to the server. I do not know
to much about it but when I try to use the utilities like admin or browser I
have to specify the pipe. Its when you log in and if you goto details it
says

"Use named pipe (local host only)

Pipe Name: \\MYSQL
"

Another thing to check is to know if your trying to connect remotely. You
can disable remote requests and stuff.

Try to use MySQL admin to login in since its easier to mess with. If you can
log in there then you know its working. Try using localhost, then 127.0.0.1,
then your LAN IP(if you have one) and then your global IP. Also try to use
the name piped too if that the other stuff doesn't work.

Your final option is to reinstall.

Jon

Jon Slaughter wrote:
> "-Lost" <maventheextrawords@techie.com> wrote in message
> news:uvCdnYhNMbzCXdLbnZ2dnUVZ_q2pnZ2d@comcast.com. ..
>> Jon Slaughter wrote:
>>> "-Lost" <maventheextrawords@techie.com> wrote in message
>>> news:dsqdnfNwWoOwJ9LbnZ2dnUVZ_sWdnZ2d@comcast.com. ..
>>>> The only thing that could have affected my installation of MySQL is me
>>>> trying out another Windows-Apache-MySQL-PHP package (WAMP5 from
>>>> http://www.wampserver.com/en/).
>>>>
>>>> Anyway, I thought it would not bother my current installation, because
>>>> most of these packages install to a directory local to their package.
>>>>
>>>> Well, before and after removing it, I can fire up MySQL in the same
>>>> fashion I always did:
>>>>
>>>> "%windir%\system32\net.exe" start MySql
>>>>
>>>> That command from my editor, fires up the MySQL (the original one), yet
>>>> I cannot connect anymore. Error (2003) 10061. I have searched and
>>>> researched different fixes at MySQL.com, and still cannot get a
>>>> connection to MySQL.
>>>>
>>>> Any recommendations on how I might fix my problem?
>>>>
>>> I have no idea. Sorry.
>>>
>>> Make sure mysql is actually started and then make sure the pipe/name
>>> didn't change. Installing other versions on top can screw things up as I
>>> recently had a similar issue with php. I had to uninstall everything and
>>> reinstall it(Which you might try).
>>>
>>> What happens is when you install something that and then uninstall it, it
>>> won't restore everything the way it was original(which is also not
>>> necessarily a good thing in some cases). But it can leave dangling
>>> references and stuff that need to be fixed. Chances are that is what
>>> happened.
>>>
>>> If you cannot connect at all to mysql but it is running then you need to
>>> make sure the ports and pipe/names have no changed.
>> Gotcha! Now, how do I insure that? In php.ini I do have the MySQL
>> default port setting at 3306; in MySQL's my.ini says port 3306.
>>
>> I am not entirely sure what you meant by "pipes/names?"
>
>
> Not quite sure ;/
>
> When you install the server it usually installs it under MYSQL I think. The
> named pipe is something you can use to connect to the server. I do not know
> to much about it but when I try to use the utilities like admin or browser I
> have to specify the pipe. Its when you log in and if you goto details it
> says
>
> "Use named pipe (local host only)
>
> Pipe Name: \\MYSQL
> "
>
> Another thing to check is to know if your trying to connect remotely. You
> can disable remote requests and stuff.
>
> Try to use MySQL admin to login in since its easier to mess with. If you can
> log in there then you know its working. Try using localhost, then 127.0.0.1,
> then your LAN IP(if you have one) and then your global IP. Also try to use
> the name piped too if that the other stuff doesn't work.

Alright, thanks a bunch. I'll keep trying.

> Your final option is to reinstall.

Oh man, this is where I get a wee bit scared. I installed e-novative's
WAMP package like, years ago... I have no clue how to go about
reinstalling just one aspect of it.

--
-Lost
Remove the extra words to reply by e-mail. Don't e-mail me. I am
kidding. No I am not.

"-Lost" <maventheextrawords@techie.com> wrote in message
news:wuydnUF_C4RdN83bnZ2dnUVZ_hCdnZ2d@comcast.com. ..
> Jon Slaughter wrote:
>> "-Lost" <maventheextrawords@techie.com> wrote in message
>> news:uvCdnYhNMbzCXdLbnZ2dnUVZ_q2pnZ2d@comcast.com. ..
>>> Jon Slaughter wrote:
>>>> "-Lost" <maventheextrawords@techie.com> wrote in message
>>>> news:dsqdnfNwWoOwJ9LbnZ2dnUVZ_sWdnZ2d@comcast.com. ..
>>>>> The only thing that could have affected my installation of MySQL is me
>>>>> trying out another Windows-Apache-MySQL-PHP package (WAMP5 from
>>>>> http://www.wampserver.com/en/).
>>>>>
>>>>> Anyway, I thought it would not bother my current installation, because
>>>>> most of these packages install to a directory local to their package.
>>>>>
>>>>> Well, before and after removing it, I can fire up MySQL in the same
>>>>> fashion I always did:
>>>>>
>>>>> "%windir%\system32\net.exe" start MySql
>>>>>
>>>>> That command from my editor, fires up the MySQL (the original one),
>>>>> yet I cannot connect anymore. Error (2003) 10061. I have searched
>>>>> and researched different fixes at MySQL.com, and still cannot get a
>>>>> connection to MySQL.
>>>>>
>>>>> Any recommendations on how I might fix my problem?
>>>>>
>>>> I have no idea. Sorry.
>>>>
>>>> Make sure mysql is actually started and then make sure the pipe/name
>>>> didn't change. Installing other versions on top can screw things up as
>>>> I recently had a similar issue with php. I had to uninstall everything
>>>> and reinstall it(Which you might try).
>>>>
>>>> What happens is when you install something that and then uninstall it,
>>>> it won't restore everything the way it was original(which is also not
>>>> necessarily a good thing in some cases). But it can leave dangling
>>>> references and stuff that need to be fixed. Chances are that is what
>>>> happened.
>>>>
>>>> If you cannot connect at all to mysql but it is running then you need
>>>> to make sure the ports and pipe/names have no changed.
>>> Gotcha! Now, how do I insure that? In php.ini I do have the MySQL
>>> default port setting at 3306; in MySQL's my.ini says port 3306.
>>>
>>> I am not entirely sure what you meant by "pipes/names?"
>>
>>
>> Not quite sure ;/
>>
>> When you install the server it usually installs it under MYSQL I think.
>> The named pipe is something you can use to connect to the server. I do
>> not know to much about it but when I try to use the utilities like admin
>> or browser I have to specify the pipe. Its when you log in and if you
>> goto details it says
>>
>> "Use named pipe (local host only)
>>
>> Pipe Name: \\MYSQL
>> "
>>
>> Another thing to check is to know if your trying to connect remotely. You
>> can disable remote requests and stuff.
>>
>> Try to use MySQL admin to login in since its easier to mess with. If you
>> can log in there then you know its working. Try using localhost, then
>> 127.0.0.1, then your LAN IP(if you have one) and then your global IP.
>> Also try to use the name piped too if that the other stuff doesn't work.
>
> Alright, thanks a bunch. I'll keep trying.
>
>> Your final option is to reinstall.
>
> Oh man, this is where I get a wee bit scared. I installed e-novative's
> WAMP package like, years ago... I have no clue how to go about
> reinstalling just one aspect of it.
>

I have not used WAMP but surely you can just reinstall Mysql? Its not hard
to do? Just download and run the install program. Its quite easy and it just
asks you a few questions. The only thing to make sure is that if you want to
use mysql as a server that the service is running.

http://www.mysql.com/
http://dev.mysql.com/downloads/gui-tools/5.0.html
http://dev.mysql.com/downloads/mysql/5.0.html

Just download the server and the gui tools(browser and admin atleast)

and install... maybe take about 5min to install and it should be up and
running. Reboot, make sure service is running (ctr-alt-del and see if mysql
is the process list)... it should be, if not then you have to go start the
service or type "net start MySQL" at the cmd line and that should work.


Then run the admin too and you should be able to log in... use the named
pipe MYSQL and use the login name and password use used when you installed
mysql. It shouldn't be that much trouble...

Jon

Jon Slaughter wrote:
> "-Lost" <maventheextrawords@techie.com> wrote in message
> news:wuydnUF_C4RdN83bnZ2dnUVZ_hCdnZ2d@comcast.com. ..
>> Jon Slaughter wrote:
>>> "-Lost" <maventheextrawords@techie.com> wrote in message
>>> news:uvCdnYhNMbzCXdLbnZ2dnUVZ_q2pnZ2d@comcast.com. ..
>>>> Jon Slaughter wrote:
>>>>> "-Lost" <maventheextrawords@techie.com> wrote in message
>>>>> news:dsqdnfNwWoOwJ9LbnZ2dnUVZ_sWdnZ2d@comcast.com. ..
>>>>>> The only thing that could have affected my installation of MySQL is me
>>>>>> trying out another Windows-Apache-MySQL-PHP package (WAMP5 from
>>>>>> http://www.wampserver.com/en/).
>>>>>>
>>>>>> Anyway, I thought it would not bother my current installation, because
>>>>>> most of these packages install to a directory local to their package.
>>>>>>
>>>>>> Well, before and after removing it, I can fire up MySQL in the same
>>>>>> fashion I always did:
>>>>>>
>>>>>> "%windir%\system32\net.exe" start MySql
>>>>>>
>>>>>> That command from my editor, fires up the MySQL (the original one),
>>>>>> yet I cannot connect anymore. Error (2003) 10061. I have searched
>>>>>> and researched different fixes at MySQL.com, and still cannot get a
>>>>>> connection to MySQL.
>>>>>>
>>>>>> Any recommendations on how I might fix my problem?
>>>>>>
>>>>> I have no idea. Sorry.
>>>>>
>>>>> Make sure mysql is actually started and then make sure the pipe/name
>>>>> didn't change. Installing other versions on top can screw things up as
>>>>> I recently had a similar issue with php. I had to uninstall everything
>>>>> and reinstall it(Which you might try).
>>>>>
>>>>> What happens is when you install something that and then uninstall it,
>>>>> it won't restore everything the way it was original(which is also not
>>>>> necessarily a good thing in some cases). But it can leave dangling
>>>>> references and stuff that need to be fixed. Chances are that is what
>>>>> happened.
>>>>>
>>>>> If you cannot connect at all to mysql but it is running then you need
>>>>> to make sure the ports and pipe/names have no changed.
>>>> Gotcha! Now, how do I insure that? In php.ini I do have the MySQL
>>>> default port setting at 3306; in MySQL's my.ini says port 3306.
>>>>
>>>> I am not entirely sure what you meant by "pipes/names?"
>>>
>>> Not quite sure ;/
>>>
>>> When you install the server it usually installs it under MYSQL I think.
>>> The named pipe is something you can use to connect to the server. I do
>>> not know to much about it but when I try to use the utilities like admin
>>> or browser I have to specify the pipe. Its when you log in and if you
>>> goto details it says
>>>
>>> "Use named pipe (local host only)
>>>
>>> Pipe Name: \\MYSQL
>>> "
>>>
>>> Another thing to check is to know if your trying to connect remotely. You
>>> can disable remote requests and stuff.
>>>
>>> Try to use MySQL admin to login in since its easier to mess with. If you
>>> can log in there then you know its working. Try using localhost, then
>>> 127.0.0.1, then your LAN IP(if you have one) and then your global IP.
>>> Also try to use the name piped too if that the other stuff doesn't work.
>> Alright, thanks a bunch. I'll keep trying.
>>
>>> Your final option is to reinstall.
>> Oh man, this is where I get a wee bit scared. I installed e-novative's
>> WAMP package like, years ago... I have no clue how to go about
>> reinstalling just one aspect of it.
>>
>
> I have not used WAMP but surely you can just reinstall Mysql? Its not hard
> to do? Just download and run the install program. Its quite easy and it just
> asks you a few questions. The only thing to make sure is that if you want to
> use mysql as a server that the service is running.
>
> http://www.mysql.com/
> http://dev.mysql.com/downloads/gui-tools/5.0.html
> http://dev.mysql.com/downloads/mysql/5.0.html
>
> Just download the server and the gui tools(browser and admin atleast)
>
> and install... maybe take about 5min to install and it should be up and
> running. Reboot, make sure service is running (ctr-alt-del and see if mysql
> is the process list)... it should be, if not then you have to go start the
> service or type "net start MySQL" at the cmd line and that should work.
>
>
> Then run the admin too and you should be able to log in... use the named
> pipe MYSQL and use the login name and password use used when you installed
> mysql. It shouldn't be that much trouble...

Hrmm... that sounds perfect, except for a few things. One, the package
installs everything in custom folders; has custom settings such as
installing particular MySQL users/passwords; and a slew of other things
like an integrated PEAR handling mechanism, and so on and so on.

Basically, I think I am going to attempt to backup all of my data:

Apache configuration files
MySQL data files
PHP ini

And maybe reinstall the package.

Your ideas are GREAT, mind you. I am just not that comfortable at all,
installing one aspect of a four-part package. I have never installed
any of these things, so you can understand my apprehension.

Thank you though, for all your help.

--
-Lost
Remove the extra words to reply by e-mail. Don't e-mail me. I am
kidding. No I am not.

"-Lost" <maventheextrawords@techie.com> wrote in message
news:UM2dnWUawvPTWs3bnZ2dnUVZ_rSjnZ2d@comcast.com. ..
> Jon Slaughter wrote:
>> "-Lost" <maventheextrawords@techie.com> wrote in message
>> news:wuydnUF_C4RdN83bnZ2dnUVZ_hCdnZ2d@comcast.com. ..
>>> Jon Slaughter wrote:
>>>> "-Lost" <maventheextrawords@techie.com> wrote in message
>>>> news:uvCdnYhNMbzCXdLbnZ2dnUVZ_q2pnZ2d@comcast.com. ..
>>>>> Jon Slaughter wrote:
>>>>>> "-Lost" <maventheextrawords@techie.com> wrote in message
>>>>>> news:dsqdnfNwWoOwJ9LbnZ2dnUVZ_sWdnZ2d@comcast.com. ..
>>>>>>> The only thing that could have affected my installation of MySQL is
>>>>>>> me trying out another Windows-Apache-MySQL-PHP package (WAMP5 from
>>>>>>> http://www.wampserver.com/en/).
>>>>>>>
>>>>>>> Anyway, I thought it would not bother my current installation,
>>>>>>> because most of these packages install to a directory local to their
>>>>>>> package.
>>>>>>>
>>>>>>> Well, before and after removing it, I can fire up MySQL in the same
>>>>>>> fashion I always did:
>>>>>>>
>>>>>>> "%windir%\system32\net.exe" start MySql
>>>>>>>
>>>>>>> That command from my editor, fires up the MySQL (the original one),
>>>>>>> yet I cannot connect anymore. Error (2003) 10061. I have searched
>>>>>>> and researched different fixes at MySQL.com, and still cannot get a
>>>>>>> connection to MySQL.
>>>>>>>
>>>>>>> Any recommendations on how I might fix my problem?
>>>>>>>
>>>>>> I have no idea. Sorry.
>>>>>>
>>>>>> Make sure mysql is actually started and then make sure the pipe/name
>>>>>> didn't change. Installing other versions on top can screw things up
>>>>>> as I recently had a similar issue with php. I had to uninstall
>>>>>> everything and reinstall it(Which you might try).
>>>>>>
>>>>>> What happens is when you install something that and then uninstall
>>>>>> it, it won't restore everything the way it was original(which is also
>>>>>> not necessarily a good thing in some cases). But it can leave
>>>>>> dangling references and stuff that need to be fixed. Chances are that
>>>>>> is what happened.
>>>>>>
>>>>>> If you cannot connect at all to mysql but it is running then you need
>>>>>> to make sure the ports and pipe/names have no changed.
>>>>> Gotcha! Now, how do I insure that? In php.ini I do have the MySQL
>>>>> default port setting at 3306; in MySQL's my.ini says port 3306.
>>>>>
>>>>> I am not entirely sure what you meant by "pipes/names?"
>>>>
>>>> Not quite sure ;/
>>>>
>>>> When you install the server it usually installs it under MYSQL I think.
>>>> The named pipe is something you can use to connect to the server. I do
>>>> not know to much about it but when I try to use the utilities like
>>>> admin or browser I have to specify the pipe. Its when you log in and if
>>>> you goto details it says
>>>>
>>>> "Use named pipe (local host only)
>>>>
>>>> Pipe Name: \\MYSQL
>>>> "
>>>>
>>>> Another thing to check is to know if your trying to connect remotely.
>>>> You can disable remote requests and stuff.
>>>>
>>>> Try to use MySQL admin to login in since its easier to mess with. If
>>>> you can log in there then you know its working. Try using localhost,
>>>> then 127.0.0.1, then your LAN IP(if you have one) and then your global
>>>> IP. Also try to use the name piped too if that the other stuff doesn't
>>>> work.
>>> Alright, thanks a bunch. I'll keep trying.
>>>
>>>> Your final option is to reinstall.
>>> Oh man, this is where I get a wee bit scared. I installed e-novative's
>>> WAMP package like, years ago... I have no clue how to go about
>>> reinstalling just one aspect of it.
>>>
>>
>> I have not used WAMP but surely you can just reinstall Mysql? Its not
>> hard to do? Just download and run the install program. Its quite easy and
>> it just asks you a few questions. The only thing to make sure is that if
>> you want to use mysql as a server that the service is running.
>>
>> http://www.mysql.com/
>> http://dev.mysql.com/downloads/gui-tools/5.0.html
>> http://dev.mysql.com/downloads/mysql/5.0.html
>>
>> Just download the server and the gui tools(browser and admin atleast)
>>
>> and install... maybe take about 5min to install and it should be up and
>> running. Reboot, make sure service is running (ctr-alt-del and see if
>> mysql is the process list)... it should be, if not then you have to go
>> start the service or type "net start MySQL" at the cmd line and that
>> should work.
>>
>>
>> Then run the admin too and you should be able to log in... use the named
>> pipe MYSQL and use the login name and password use used when you
>> installed mysql. It shouldn't be that much trouble...
>
> Hrmm... that sounds perfect, except for a few things. One, the package
> installs everything in custom folders; has custom settings such as
> installing particular MySQL users/passwords; and a slew of other things
> like an integrated PEAR handling mechanism, and so on and so on.
>
> Basically, I think I am going to attempt to backup all of my data:
>
> Apache configuration files
> MySQL data files
> PHP ini
>
> And maybe reinstall the package.
>
> Your ideas are GREAT, mind you. I am just not that comfortable at all,
> installing one aspect of a four-part package. I have never installed any
> of these things, so you can understand my apprehension.
>
> Thank you though, for all your help.
>

Yeah, back everything up then but I think you will find the installation
quite easily just download, run, and fix out a few pieces of data that
pretty much every normal app asks now days. These packages have come quite a
long ways compared to what they used to be and now they act just like normal
apps(no compiling source going or using very strange setup techniques).

Technically you can install the stuff side by side but as you have found
out, these programs don't always get along.

Backup all your data, and then uninstall it if you can. Then download the
latest apache, php and mysql windows binaries as installers(not the source
or binaries but the installer) and install them. Install apache first, then
mysql, then php5.

The only issue I had was wiht php when I installed for the very first time.
It would crash on installation complaining something about some of the
modules... I just didn't install them.

What you should do, if you have that problem, install php with the minimum
number of modules(don't add any extra) and then repair the installation and
add the extra modules you need or manually install them(i.e., just copying
dll to the ext dir and fixing up the php.ini with the extension=dllname).

I think you will find its quite easy... I hope

Jon

Jon Slaughter wrote:
> "-Lost" <maventheextrawords@techie.com> wrote in message
> news:UM2dnWUawvPTWs3bnZ2dnUVZ_rSjnZ2d@comcast.com. ..
>> Jon Slaughter wrote:
>>> "-Lost" <maventheextrawords@techie.com> wrote in message
>>> news:wuydnUF_C4RdN83bnZ2dnUVZ_hCdnZ2d@comcast.com. ..
>>>> Jon Slaughter wrote:
>>>>> "-Lost" <maventheextrawords@techie.com> wrote in message
>>>>> news:uvCdnYhNMbzCXdLbnZ2dnUVZ_q2pnZ2d@comcast.com. ..
>>>>>> Jon Slaughter wrote:
>>>>>>> "-Lost" <maventheextrawords@techie.com> wrote in message
>>>>>>> news:dsqdnfNwWoOwJ9LbnZ2dnUVZ_sWdnZ2d@comcast.com. ..
>>>>>>>> The only thing that could have affected my installation of MySQL is
>>>>>>>> me trying out another Windows-Apache-MySQL-PHP package (WAMP5 from
>>>>>>>> http://www.wampserver.com/en/).
>>>>>>>>
>>>>>>>> Anyway, I thought it would not bother my current installation,
>>>>>>>> because most of these packages install to a directory local to their
>>>>>>>> package.
>>>>>>>>
>>>>>>>> Well, before and after removing it, I can fire up MySQL in the same
>>>>>>>> fashion I always did:
>>>>>>>>
>>>>>>>> "%windir%\system32\net.exe" start MySql
>>>>>>>>
>>>>>>>> That command from my editor, fires up the MySQL (the original one),
>>>>>>>> yet I cannot connect anymore. Error (2003) 10061. I have searched
>>>>>>>> and researched different fixes at MySQL.com, and still cannot get a
>>>>>>>> connection to MySQL.
>>>>>>>>
>>>>>>>> Any recommendations on how I might fix my problem?
>>>>>>>>
>>>>>>> I have no idea. Sorry.
>>>>>>>
>>>>>>> Make sure mysql is actually started and then make sure the pipe/name
>>>>>>> didn't change. Installing other versions on top can screw things up
>>>>>>> as I recently had a similar issue with php. I had to uninstall
>>>>>>> everything and reinstall it(Which you might try).
>>>>>>>
>>>>>>> What happens is when you install something that and then uninstall
>>>>>>> it, it won't restore everything the way it was original(which is also
>>>>>>> not necessarily a good thing in some cases). But it can leave
>>>>>>> dangling references and stuff that need to be fixed. Chances are that
>>>>>>> is what happened.
>>>>>>>
>>>>>>> If you cannot connect at all to mysql but it is running then you need
>>>>>>> to make sure the ports and pipe/names have no changed.
>>>>>> Gotcha! Now, how do I insure that? In php.ini I do have the MySQL
>>>>>> default port setting at 3306; in MySQL's my.ini says port 3306.
>>>>>>
>>>>>> I am not entirely sure what you meant by "pipes/names?"
>>>>> Not quite sure ;/
>>>>>
>>>>> When you install the server it usually installs it under MYSQL I think.
>>>>> The named pipe is something you can use to connect to the server. I do
>>>>> not know to much about it but when I try to use the utilities like
>>>>> admin or browser I have to specify the pipe. Its when you log in and if
>>>>> you goto details it says
>>>>>
>>>>> "Use named pipe (local host only)
>>>>>
>>>>> Pipe Name: \\MYSQL
>>>>> "
>>>>>
>>>>> Another thing to check is to know if your trying to connect remotely.
>>>>> You can disable remote requests and stuff.
>>>>>
>>>>> Try to use MySQL admin to login in since its easier to mess with. If
>>>>> you can log in there then you know its working. Try using localhost,
>>>>> then 127.0.0.1, then your LAN IP(if you have one) and then your global
>>>>> IP. Also try to use the name piped too if that the other stuff doesn't
>>>>> work.
>>>> Alright, thanks a bunch. I'll keep trying.
>>>>
>>>>> Your final option is to reinstall.
>>>> Oh man, this is where I get a wee bit scared. I installed e-novative's
>>>> WAMP package like, years ago... I have no clue how to go about
>>>> reinstalling just one aspect of it.
>>>>
>>> I have not used WAMP but surely you can just reinstall Mysql? Its not
>>> hard to do? Just download and run the install program. Its quite easy and
>>> it just asks you a few questions. The only thing to make sure is that if
>>> you want to use mysql as a server that the service is running.
>>>
>>> http://www.mysql.com/
>>> http://dev.mysql.com/downloads/gui-tools/5.0.html
>>> http://dev.mysql.com/downloads/mysql/5.0.html
>>>
>>> Just download the server and the gui tools(browser and admin atleast)
>>>
>>> and install... maybe take about 5min to install and it should be up and
>>> running. Reboot, make sure service is running (ctr-alt-del and see if
>>> mysql is the process list)... it should be, if not then you have to go
>>> start the service or type "net start MySQL" at the cmd line and that
>>> should work.
>>>
>>>
>>> Then run the admin too and you should be able to log in... use the named
>>> pipe MYSQL and use the login name and password use used when you
>>> installed mysql. It shouldn't be that much trouble...
>> Hrmm... that sounds perfect, except for a few things. One, the package
>> installs everything in custom folders; has custom settings such as
>> installing particular MySQL users/passwords; and a slew of other things
>> like an integrated PEAR handling mechanism, and so on and so on.
>>
>> Basically, I think I am going to attempt to backup all of my data:
>>
>> Apache configuration files
>> MySQL data files
>> PHP ini
>>
>> And maybe reinstall the package.
>>
>> Your ideas are GREAT, mind you. I am just not that comfortable at all,
>> installing one aspect of a four-part package. I have never installed any
>> of these things, so you can understand my apprehension.
>>
>> Thank you though, for all your help.
>>
>
> Yeah, back everything up then but I think you will find the installation
> quite easily just download, run, and fix out a few pieces of data that
> pretty much every normal app asks now days. These packages have come quite a
> long ways compared to what they used to be and now they act just like normal
> apps(no compiling source going or using very strange setup techniques).
>
> Technically you can install the stuff side by side but as you have found
> out, these programs don't always get along.
>
> Backup all your data, and then uninstall it if you can. Then download the
> latest apache, php and mysql windows binaries as installers(not the source
> or binaries but the installer) and install them. Install apache first, then
> mysql, then php5.
>
> The only issue I had was wiht php when I installed for the very first time.
> It would crash on installation complaining something about some of the
> modules... I just didn't install them.
>
> What you should do, if you have that problem, install php with the minimum
> number of modules(don't add any extra) and then repair the installation and
> add the extra modules you need or manually install them(i.e., just copying
> dll to the ext dir and fixing up the php.ini with the extension=dllname).
>
> I think you will find its quite easy... I hope

Hehe. Thanks! I will give it all a go. I have thus far successfully
reinstalled the original package, but that still leaves me without
updates like I initially wanted.

I will go your route and cross my fingers all the way.

--
-Lost
Remove the extra words to reply by e-mail. Don't e-mail me. I am
kidding. No I am not.