My advise as I mentioned in my post above is not to try and do anything with the system database mysql
or any of those already created in the phpMyAdmin database list, for obvious reasons as the user you are using to access and write new data may not have permissions to do what you want - user pma for example has read only access.
My suggestion of creating a database for your own use still stands and creating a user for that database with permissions for full access and a database user access password may eliminate these errors.
I am not familiar with this error and from the FAQ 2.8 mentioned most items are as they should be in the default Apache installation - this is why I asked if you had changed anything - but please read that linked FAQ in the error message and see if it makes any sense to you.
So I suppose the next line of attack might well be in doing a Google
search for your error message and see if any one else on the Internet knows what's happening - or you could wait for some other forum member with experience of this issue to spot your post and provide a definitive solution - as you can guess my time is limited as this issue needs much more research because I am unable to replicate it for you.
Try checking out the XAMPP bug site to see if there is a known issue:
One of the developers pops in to the forums from time to time, in between coffee breaks perhaps, that may shine more light on the issue.
Just to add, I have known setting these two to have fixed some strange errors when developing, although I have my doubts in this case, but it will do no harm to try when only using localhost for developing - you can always revert if it changes nothing for you:
Turn On register_globals
and turn Off safe_mode
in your xampp\apache\bin\php.ini
Restart Apache and make a backup up of any ini or conf file before editing.
Not sure it will help but having just tried to read the php file in question I spotted a possible solution by doing the above configuration changes.
And last but not least, as I keep adding things as I come across them, go to:
and test all the menu items, as quite a few are database driven to make sure that MySQL is functioning as it should.
Also have you tried switching php to php 4 using the xampp\php-switch.bat
file and selecting 4 to switch, but make sure you have stopped Apache and MySQL before switching, then try doing what you want again, being as you are wanting to do things php4 related?
You can always switch back again using the same procedure but select 5 from the options.
Bear in mind though, that php switching in XAMPP 1.6.5 may have a bug that has been pointed out in recent posts and has been reported to XAMPP Bugs - but by reverting to an older XAMPP version the bug appears not to be evident.