Petar Nikolich wrote: > Hello Everyone! > > Ok, this config this is driving me crazy. Php works just fine until I > try to specify the path to the php.ini file in the IIS5 script > mapping. > > It would be good to have each virtual server running its own php.ini, > temp area and php binaries (different versions) and all I need to > work out is how to make the '-c path/to/inifile' actually have an > effect within IIS. > [...] > This is the normal line which uses the php.ini in c:\winnt\php.ini > > executable: -> c:\site1\php\php.exe > extension: -> .php > > Adding the extra parameter to the executable line *should* be all > that is needed to make individual .ini files workable like the > following... > > exexcutable: -> c:\site1\php\php.exe -c > c:\site1\php\php-site1.ini extension: -> .php > > But no matter how I pass the line (quotes/no quotes) the additional > parameter is ignored and the c\winnt\php.ini is used. > > Actaully typing the line at a dos prompt does use the new .ini file > so it seems IIS is doing suomething to remove/ingore the extra > paramter when it is entered in IIS script mapping. > > c:\site1\php>php -c c:\site1\php\php-site1.ini -i > ...shows correct path to specified .ini file > > > Has anyone made this work? I would really like to know the 'magic > trick' :-(
Remove php.ini from c:\winnt and then put all the php.ini's into the same directory where php.exe is. This only works with CGI. It should be possible to set per-directory-values over the registry, but I don't know how. Maybe you find something on the web. Look for posts by Daniel Beulshausen who used to work on the windows version or by Shane Caraveo. HTH Christoph -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
