> > I believe it is possible with this configuration: > > > > 1. php*ts.dll, php*apache*.dll, php.ini, *.dll in e.g. C:\PHP\ > > 2. C:\PHP\ in PATH > > 3a. C:\PHP\ in PHPRC (for PHP 4) > > 3b. C:\PHP\ in Registry entry HKLM\Software\PHP\IniFilePath (for PHP 5) > > > > C:\PHP\ in PATH is necessary only for *.dll (such as libmysql.dll). You > > can have these also in other PATH directory (e.g. C:\Windows\System32). > > I think this is the perfect solution!
Microsoft advise against putting application libraries in C:\Windows\System32. And yeah, that was news to me too :I I should add that if you start bringing registry entries into it you're going to alienate a lot of newbies. It's not needed, and I certainly don't see any way it's more straightforward than copying the entire contents of the PHP directory into the toplevel of Apache\bin if you want to have the option of running PHP as a SAPI module. You'd only need to alter httpd.conf to say whether you were using php*apache.dll or the cgi version of php.exe, which could be in a different directory, and could be a different version that uses a different php*ts.dll. The problem with setting a PHP PATH entry is that it excludes the possibility of other installations. - Steph
