Thank you for taking the time to report a problem with PHP.
Unfortunately you are not using a current version of PHP -- 
the problem might already be fixed. Please download a new
PHP version from http://www.php.net/downloads.php

If you are able to reproduce the bug with one of the latest
versions of PHP, please change the PHP version on this bug report
to the version you tested and change the status back to "Open".
Again, thank you for your continued support of PHP.

PHP 4.3.2 was released already..

Exactly. I misrepresented the version in the body of my text, but you'll see (apologetically) that the version to which I was referring was not 4.3.0, but. 4.3.2.

A quite thorough search of the bug reports did not result in my finding this issue. I am therefore reopening this issue; I don't believe it is bogus. Check the php4ts.dll and you'll see that what I'm saying is still an issue.
Apologies again for this error on my part - I just installed 4.3.2 yesterday; CLEAN. No earlier version on my computer anywhere; complete reformat and reinstall of Win2K prior to install of 4.3.2

Excuse me - addionally, all 3 of the reported install issues (saying 4.3.0 in error), should have been attributed to 4.3.2, not just the issue with the php4\pear path.

You're supposed to set those in php.ini, not bug.

Sorry to be so persistent - but there IS no place in the php.ini to correct the path for PEAR. So why is phpinfo() reading it as php4\pear, and where is it reading it from, if not from php4ts.dll? I assure you it is not in the ini file anywhere.

No offense intended, truly, all of you developers are stunning. But until a php.ini (or php.ini-dist) is supplied with each install that reflects more than 'examples' for a newer user, this is going to be hard to figure out. To me (as a QA Team Leader for a national software product), this is, while not technically a bug in the program, a bug in the documentation/supplied setup materials for new users.

While I do not suppose that phpinfo.php is written to reflect every system variable, it would be good to know why the cgi_force_redirect parameters are not reflected in the phpinfo.php.

I apologize for being so stuffy about this, but QA is my life. The ini should contain all the info needed to get up and running, or, if the system is reflecting configuration (the Pear stuff) that is drawn from elsewhere in the system, then the user needs to know why.

Close this, if you like, but I strongly disagree with this, even if its a Tier3 bug. :D It's still a bug.

with the "new" installer this should be way better now.