I've set up as modules but there is a problem - IE offers to download the script instead of starting it... Although AddType is done...

By installation of PHP4 (which I did according to the instruction) I was displayed error No such file or directory. After some searches I found in one source that one of the compulsory steps should include switching session.save in your php.ini in order to make it indicate to the really existing temporary files’ directory (for instance, c:/windows/temp or c:/windows/tmp). After this operation it started working properly in the both variants (CGI-executable and as Apache-mode).

About half a year or more ago I installed PHP as module and didn't have any problems. I repeated all the steps today but I've managed nothing (I've dowloaded latest PHP & Apache 1.3 versions)
Module seems to link up but it doesn't do anything... After 30 minutes efforts it proved out that AddModule mod_php4.c should be added into http.conf
Something like this...

Everything works!
Apache 1.3.22 + PHP 4.1.1 as module
Following must be written into httpd.conf:
into the section...
# Dynamic Shared Object (DSO) Support
LoadModule php4_module "d:/web/php/sapi/php4apache.dll"
AddModule mod_php4.c
into the section...
<IfModule mod_mime.c>
AddType application/x-httpd-php .php .phtml .php4
</IfModule>

1) I have such a bug: PHP-scripts work in the site's root catalogue only. How can I strive with it?
2) How to make PHP-scripts send mails?

Thanks for the article! Everything works. But IE 6.0 handles extensions .php, .php4...directly within folder Apache Group\Apache\htdocs\. If you place PHP-file in any other catalogue, browser simply outputs scripts.
At this in the browser's address string http://localhost/*.php is indicated. Any change of PHP-files placement outside of Apache Group\Apache\htdocs\*.php is going to cause error.

Just a small addition: to install PHP+Apache under Win with SSL-support you need module php4apache.dll compiled with /DEAPI option. But it is impossible to found in the net.
Notice that dll from the previous PHP-versions doesn’t suit.

We make following:
We get latest PHP-sources and launch them into PHP sub catalogue.
It is not necessarily to be Win – you may take php-4.3.11.tar.gz as well.
Next to it we launch sources for win apache in php_build\Apache and sources bindlib_w32 and win32build.
We get something like:
\work
\php
\php_build
\apache
\include
\lib
\libexec
\modules
\src
\include
\bindlib_w32
\win32build
Then we take project’s file, for instance
php\sapi\apache\php4apache.dsp or
php\sapi\apache\php4apache.vcproj
and start under visual studio.
We check compiler’s include settings and lib by linker and set up them correctly (if necessary).
Not all lib and include will be set up correctly in the source.
During compilation and link it becomes clear what hasn’t been set up yet – you need to add and install this.
Naturally release should be Release_TS as far as Debug_TS won’t be assembled because of absence of corresponding lib-files with debug-option.
We place latest lib from the PHP-installation into php\lib catalogue.
It should be noticed that Apache-sources (for example, 1.3.33) are sometimes wrong i.e. they don’t contain all the things that go with EAPI which include:
httpd.h
ap_alloc.h
buff.h
http_conf_globals.h
http_config.h
ap_mmn.h
ap_ctx.h
ap_hook.h
ap_mm.h
xmlparse.h.
In such a case you are to take them from the ‘right’ previous Apache-version – it doesn’t really matter for assembling as far as we are assembling PHP not Apache.
We insert /DEAPI (or /D "EAPI") into the additional compiler’s options.
Next Build and from the catalogue php/release_ts we obtain php4apache.dll needed.