If you are using Vista and having problems with the SpikeWAMP stack we released recently, you should be able to fix the problem manually.
The most annoying bug I am facing with my trials on Vista is the ownership and permissions of files. I am going to fix this one in the installer and run a few more tests. But in the meanwhile, a broken installation can be fixed manually.
The symptom:
The stack installation went through fine, but now the services are not starting. You can see the tray menu icon, but when you click on it, select "Apache" -> "Start Apache Service" (which is not grayed out, btw), nothing happens, Apache does not start.
(Note: If all menu items under "Apache" or "MySQL" are grayed out, right click the tray menu icon, and click on "Exit". Then go to "Start Menu" -> "All Programs" -> "SpikeWAMP" -> "SpikeWAMP Control Panel"; right click and select "Run as Administrator". This time you should be able to start and stop services. Also the service status should be reflected correctly in the tray icon's color.)
The Solution:
The problem is most likely that the permissions of the installation are not set correctly. If you see the error in the service startup in your computers Event Viewer, it will say Cannot open log files or something like that.
Do not despair! Open the Bash Prompt windows as Administrator. Click Start -> All Programs -> SpikeWAMP -> Bash Prompt, then right click and select "Run as Administrator". Then in the opened command window run the following commands:
chown -R "${USER}" /opt/spikesource/*
chmod u+rw -R /opt/spikesource/*
chmod a+r -R /opt/spikesource/*
Don't forget the "-R" option and make sure you stick the trailing "/*" after "/opt/spikesource". Then try starting the services again. It should work this time.