AW: [PHP-WIN] win32 php.ini default behavior better in php executable directory?

Hello Petar, it already works this way. But beware of using different versions of PHP: you have to keep apart the Dll's too, because the interface description of e.g. php4ts.dll changes from time to time. So clean up %WINDIR%, %WINSYSDIR% etc of any PHP stuff and put your basic dlls in the same folder as PHP.EXE. And keep a perfect track of the correct "extension_dir" for every PHP version. Otherwise very very strange things happen because Windows jumps into the DLLs right through the wall. Its not like the new registered versioned COM stuff of M$. -- Sven > -----Ursprüngliche Nachricht----- > Von: Petar [SMTP:petar@escape.net.au] > Gesendet am: Samstag, 28. Dezember 2002 14:02 > An: php-windows@lists.php.net; php-dev@lists.php.net > Betreff: [PHP-WIN] win32 php.ini default behavior better in php executable directory? > > Hi All, > > Sorry about the cross post but I suppose it applies in both areas. > > I raised a few questions about getting an alternate php.ini recognised > when multiple php installs are on a windows 2000 server with no real > solution so far. I noticed 4.3.0 claims to have support for the > "-c /path/to/php.ini" which should allow the cgi version to use an > alternate php.ini file but it does not work under IIS5 and neither > does 4.2.3 > > I propose that the initial location php.exe should look for a php.ini > file is in the directory from which it executes. This would overcome > any issues with individual web servers on a win32 platform and allow > multiple configs/multiple copies of php to be executed without > trickery like the "-c /path/to/php.ini" which doesn't work. > > I could then run a d:\client1\phpbin and e:\client2\phpbin without > any additional support required by the webserver. The size of php > is tiny and would not be an impost to run multiple copies. This system > would allow multiple version to run if required by simply changing the > cirtual directory structure in IIS5. > > To keep the present 'default' behavior just make sure you don't > keep a php.ini in the executable directory and it should then run off > and look in c:\winnt like it does at present. > > Anyone see a downside to this proposition? > > Regards > > ..Petar > > > -- > PHP Windows Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php