Problems with XAMPP and Vista

[killgasm]

I cant seem to get XAMPP to work on my desktop with Windows Vista! It just wont start the apache and MySQL services, and trying 'localhost' doesnt find a page.

Ive tried the manual install aswell and still have had no luck! Here is an image displaying my problem.

http://69.16.196.116/~inspin/files/apacheProblem.jpg

You can see how my control panel looks after trying to start apache and MySQL. Also, you can see how entering localhost into a web browser does not bring up the default XAMPP page.

I've also been sure to not install it under Program Files

Has anyone else had this problem??

[alladeen]

http://127.0.0.1 is workin but http://localhost is not

[gambler]

I am having a similar problem.

It looks like it may have something to do with multiple hosts being open at once.

Also, make sure that UAC is off.

[jawa500]

I have a similar problem with http://localhost not working but http://127.0.0.1 working fine.

I have Vista Home Premium, XAMPPLITE 1.63a and Firefox 2.0.0.11 (also tried IE 7)

Everything was fine when I last used it over a week ago but localhost is broken today.

The only thing I can think of that would have affected this were 10 automatic Vista updates that were installed a few days ago.

One thing I did spot was that the Firefox status bar changed from "Waiting for localhost" to "waiting for www.localhost.com" after a couple of seconds and then I got the message "The connection to the server was reset while the page was loading".

I have no problem with now using http://127.0.0.1 but if anyone can shed any light as to why it is trying to find www.localhost.com then I would be most interested.

[LeeHunter]

I'd been using XAMPP on Vista for three or months without a problem. Yesterday it stopped working (I could run MySQL but Apache wouldn't start) and reinstalling or using the portable version from the desktop or thumbdrive didn't fix it.
The solution was to disable the User Access Control from the Control Panel.

It was probably an "improvement" introduced by a Windows automatic update.

[LeeHunter]

Actually after a little more investigation (the problem came back) it's looking like Skype might be the culprit as per this site: http://www.likertland.com/blog/2007/09/ ... and-skype/