9B) Configure PWS (Personal Web Server) to use PHP ISAPI
(continued...)
In the "Application Configuration" window (M), click on the "App Mappings" tab (N) and click on the "Add" button (O).
In the "Add/Edit Application Extension Mapping" window (P), type .php in the "Extension" box (Q). Don't forget the dot before "php". Make sure "All Verbs" is selected, and "Script engine" and "Check that file exists" check boxes are checked (S). Finally, click on the "Browse" button (T).
In the "Open" window (U), drop down the "Files of Type" to "Dynamic Linked Libraries (*.dll)" (V)
Still in the "Open" window (U), drop-down and browse to "C:\PHP" (W), and click select the php4isapi.dll file (X) and click on the "Open" button (Y).
Back in the "Add/Edit Application Extension Mapping" window (P), check that you have all the needed settings as shown in the screen shot below. The path to the "Executable:" should be to the "php4isapi.dll" file in the PHP folder (T). If this is not the case, then click on the "Browse" button (T) again to correct the path.
If all is well, click on the "OK" button (Z). This will bring
you back to the "Application Configuration" window (M). The last line in the list of "App Mappings"
(N) should now be
".php C:\PHP\php4isapi.dll
(all)" (A). If this is the case, we can click on the
"Apply" button (B) and then click on the "OK" button
(C) to
close this window. Otherwise, back track the steps outlined to correct the
mappings.
![]()
We are almost there... the next step (#10) somehow looks redundant to step
#9. In any future installation with the same environment, we will
definitely check the registry and find out what exactly step #9 does to the
systems registry. If we discover that Steps #9 and #10 do exactly the same
thing, we can obviously drop either one of them. So without having tested
if it is actually so, let's go and do the next step (#10) anyway.
Previous Step: 9A) Configure PWS (Personal Web Server) to use PHP ISAPI
Next Step : 10) Tweak the Window's System Registry