daffy wrote:If I use the 7Zip mode and the setup.bat
I get a message Warning Directory mismatch.
The fix is in the following link but the message can be ignored if you prefer not to edit the registry.
viewtopic.php?p=108259#108259Again make sure that no other php.ini file is on your PC other than in the apache\bin folder.
Check that PHPRC is not in your Path variables.
Open the Windows Control Panel, click on the System>Advanced>Environment Variables
Under the heading User variables for [logged in user name] look for the Variable PATH
Click on the line and select Edit.
Look for an entry PHPRC followed by a path
If you find it then delete the entry then OK.
Make sure that a separator (
;) remains between all entries after removing the PHPRC entry
Repeat the above under the
System Variable>Path line (
note the case change). Again delete the whole PHPRC entry if found.
daffy wrote:After some installs everything is there except Mysql.
Sometime Mysql will start as a service sometimes not.
Try starting MySQL using the mysql_start.bat file as it may give a more detailed error message.
daffy wrote:When I do an uninstall the Xampp directory itself will not uninstall or delete unless I restart the computer then delete it.
This is telling you that a component or a file in the xampp folder is currently still in use and the folder can't be deleted if a file is in use.
Try the sc delete fixes in the search link below to clear your registry of any sticking XAMPP services that are failing to be released.
Search for Service ControllerAnd don't start any XAMPP components as a Service unless that is what you want to happen every time you reboot.
Follow the instructions in
this topic to download the Microsoft Visual C++ 2005 Redistributable Package (x86) which may help.
This post has another MS fix for MySQL
viewtopic.php?f=16&t=32617To stop the WinMySQLAdmin issue first don't click on the MySQL Admin button in the XCP and for a more permanent fix read this search link.
Search for WinMySQLAdminAll the above may be worth a try to solve this issue, hopefully.