#19423 [Fbk]: Problem with extension_dir in PHP.ini

ID: 19423 Updated by: jmoore@php.net Reported By: cdfisher@swbell.net Status: Feedback Bug Type: *Web Server problem Operating System: Windows 9x/NT/ME/2000/XP PHP Version: 4.2.3 New Comment: No php.ini does not have to be on the c: drive. However please make sure you are using the c:\\ or c:/ syntax. Also make sure that your php.ini file is in the correct location (look at the output of phpinfo()). With the cli and cgi versions you can often get away with putting the php.ini file in the same dir as the executable and it will find it there. - James Previous Comments: ------------------------------------------------------------------------ [2002-09-24 17:03:32] cbrady@sbccd.cc.ca.us Same issue. However, its it a requirement that the php directory be on the c: drive? I have the same problem with any php version I install on the Win2k Server. ------------------------------------------------------------------------ [2002-09-21 14:27:49] iliaa@php.net try changing 'c:\php\extensions' to 'c:\\php\\extensions' or 'c:/php/extensions' and see if it begins to work. ------------------------------------------------------------------------ [2002-09-16 08:32:29] cdfisher@swbell.net Oh yeah, I forgot to add that all the pertinent files for this extension are in the %system% directory! ------------------------------------------------------------------------ [2002-09-16 08:29:45] cdfisher@swbell.net To mficher: If you can give me some cookbook instructions on how to use this tool, then I would be glad to give it a try. It looks as though it needs a running process, but the error occurs when I start IIS. How can I accomplish what you need? ------------------------------------------------------------------------ [2002-09-16 03:24:32] mfischer@php.net Is there a chance to use the strace tool [1] to track what's going on/wrong here? This tool may help tracking down which directory/files are really accessed. [1] http://razor.bindview.com/tools/desc/strace_readme.html ------------------------------------------------------------------------ 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/19423 -- Edit this bug report at http://bugs.php.net/?id=19423&edit=1