Thanks. I didn't catch that. It's still unclear, but I will look at the link and follow along.
I do have that issue, but also a totally separate issue: Can someone please clarify why a "blank page" shows up, after I run the ".msi" (non-thread-safe) installer on Win XP Pro, SP2, IIS 5.1.(php-5.2.9-2-nts-Win32-VC6-x86.msi - this is the one I ran).
The WebPI did not appear to run exactly right, so I downloaded the actual .msi and ran that. Maybe the WebPI ran okay - so it could be my imagination on that part.
Nobody seems to have a consensus on the "test.php" <? phpinfo(); ?> 'blank page' issue. When right-clicking in IIS mgr, Web sites, Properties, Home Directory, Configuration, here is the ".php" entry: C:\Windows\System32\inetsrv\fcgiext.dll
I've seen various steps regarding various install instructions which bother me:
For example, one person has a 5-step process for installing PHP5 for IIS5.x:
http://www.iis-aid.com/articles/how_to_guides/installing_php_5_on_iis_in_5_simple_steps
It references the "ts" (thread-safe) model. It also mentions that you must separately download some PECL32 portion, put that in the PHP\ext folder, and do some magic. :)
Also, per "Mr 5-Step," you must create "sessions," "upload" and "log" folders, and create a blank php.log in the log folder.
Anyway, I think you can get my point: If there is this wonderful installer, why is all this manual stuff still needed (the PECL piece, and the creating the additional folders, etc.)? Granted, he is showing the "manual method," but the fact that your installer does not have some of the things he references is rather unsettling.
I ran your installer, and it does not create those 3 folders mentioned, so I'm guessing that needs to be added to your WebPI and/or .msi installer package. Or... are those folders not needed; are they only for a specific version? There seems to be a LOT of 'disconnect' regarding what IS needed; and what is NOT needed - and maybe that would be a good "article" for one of you 'gurus' to write for us n00bs. Even a very nice "matrix" chart showing exactly what's needed and what isn't. For example, you say a certain "fast cgi" dll is needed; and Vista SP1 is needed; so, apparently that particular DLL is only regarding IIS7/Vista SP1. Whereas, after I ran your installer on an XP Pro SP2 system, I get the "C:\Windows\System32\inetsrv\fcgiext.dll" entry; BUT, "Mister 5-Step" says I need to point to "php5isapi.dll;" which your installer does not even extract to the PHP folder. So, again, you can see how all this might be a bit confusing.
Also, does it matter C:\PHP vs. C:\Program Files\PHP? (Someone mentioned the 'space' in the "Program Files" folder name, but that may have been in reference to an older o/s - i.e., changing some reference to "C:\Progra~1\PHP" [maybe in the Environment variables?]).
It just does not seem like it should be this difficult to get PHP to run on XP Pro SP2, with IIS 5.1. And maybe it [IS] "running," but it's certainly not displaying the "info" when I run the infamous "phpinfo()" directive - it just gives a blank page (view source shows the phpinfo() directive, so obviously IIS is trying to serve up the page, in some form or fashion).
Maybe it's just me but, when I see that a package has an "installer," I expect that, once the install is completed, I should be able to see the package work, without having to be a contortionist. And again, maybe it [IS] working, and I just am confused.
Thanks for any info and help.