[snip] ...lots of valuable information.... [/snip] >From the offices of "You Ain't Gonna' Beleeeve Dis, Inc." We barked up several trees, but there were no real squirrels. PHP 4.4.1, the version on the server in question, comes with 2 flavors of ini file, the dist and the recommended. I had copied the recommended and renamed it php.ini, which is the one we have been using all day. I am standing in the data center cursing and swearing and the network admin says, "Maybe the ini file is hosed somehow." Of course I said that that could not be the case. What could possibly be bad in the text file to cause this kind of behavior? As the afternoon wore on he kept asking if I could water down the ini file because it was the placement of that file that caused the problem. Even when I went the route of changing the environment variable I had problems. I told him that several of the best minds in the world were working on the problem and that the ini file could not be at fault really. I wanted to prove to him that this could not be the case, so I renamed the recommend->php.ini->php.ini.old and copied the dist version which was renamed to php.ini. I moved it to the WINNT folder. I stopped and started IIS. Lo' and behold, the php pages loaded fine, with no 404 error. I made a change to the ini file. It showed up properly in phpinfo(). Dammit he had a smug look on his faced when I departed the data center. Apparently there is something wrong with the 'recommended' version. I will have to compare them to see the differences so that maybe the problem could be isolated so that furture users do not encounter the several hours of frustration that I have encountered. You're all to be praised for your knowledge and insight. Thank you. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
