OK, what if someone has files left from a previous PHP installation? I guess if one inserts the PHP folders onto the start of the PATH, then this is not a problem
It would still be best to go through and remove them. A pain now, but better in the long run.
Yep, I have added this suggestion to the manual, but would still interested in providing a way that would work even if people leave DLLs around inadvertantly.
I am still unsure whether it is better to suggest people to replicate the PHP 5 package structure with PHP 4 (dump the dlls and sapi folder into the main PHP installation folder), so then there is no need to set any environment variables, and everything will work right out of the box:
- the php.ini is searched in the executable (php.exe, php4isapi.dll, etc.) folder - the additional libs are also searched there - the extension dir is set in php.ini so it will work otherwise
This seems to be the easiest way, but I am not entirely sure that the first list item is completely right for all SAPIs. Wez, what is your take on this? The question comes down to what this part adds to the search queue (what does GetModuleFileName() return) in case someone runs an SAPI dll:
http://lxr.php.net/source/php-src/main/php_ini.c#344
IMHO the best would be not to go in detail on setting ENV vars, while we can do everything without them. We would need file move operations for PHP 4 (to replicate the PHP 5 structure), but then everything would work right (at least it seems). I sadly have no Windows to try it out.
Goba
