ID: 38954
User updated by: akaraethon at gmail dot com
Reported By: akaraethon at gmail dot com
Status: Open
Bug Type: MySQL related
Operating System: Windows Server 2003 32bit
PHP Version: 5.1.6
New Comment:
Well I think we just discovered a clue, when I MOVED php.ini to the
d:\Windows, php failed, when I COPIED php.ini back to c:\PHP5 php still
failed to start, but once I DELETED the php.ini file in d:\Windows PHP
Started fine, but still isn't reading the ini info...
Previous Comments:
------------------------------------------------------------------------
[2006-10-04 12:00:13] akaraethon at gmail dot com
.
------------------------------------------------------------------------
[2006-10-04 11:52:01] tony2001@php.net
.
------------------------------------------------------------------------
[2006-10-04 11:44:27] akaraethon at gmail dot com
nope, no good, now PHP wont start at all. all page requests now come
back 404. its not a misconfiguration, there is something else wrong.
------------------------------------------------------------------------
[2006-10-04 09:01:04] edink@php.net
php.ini should be placed in d:\windows as you can see from that
phpinfo() page.
------------------------------------------------------------------------
[2006-10-04 02:54:52] akaraethon at gmail dot com
Everyone I've talked to says this has to be a bug, or an error in the
5.1.6.6 build, I'm not new to PHP/MySQL, I've been at it since PHP was
2 I know what I am doing, take a look at http://dragon-radio.selfip.net
for yourself, you will see on the page itself my phpinfo output as well
as my entire current PHP.ini file (no its not copy and pasted its
generated with the folowing code echo "<br/><br/><pre>";
ob_start();
readfile('c:\php5\php.ini');
$data = ob_get_contents();
ob_end_flush();
echo"</pre>";) you can see for yourself that I have everything in there
right, but PHP is ignoring it.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/38954
--
Edit this bug report at http://bugs.php.net/?id=38954&edit=1