I'm not sure about all that stuff that appeared in the log file. I dont have
any idea what those programs are for.
Has what Todd said helped?

The question about "GET /phpinfo.php HTTP/1.1" 200 33: GET means that the
browser told apache to GET /phpinfo.php.  HTTP/1.1 is the way in which the
file was transferred and the 200 means everything was ok.I'm not sure about
the second number but i'm pretty sre it's not important.
If a file can't be found, you'd see 404 instead of 200.



"Todd Williamsen" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> don't remove the html extension!
>
> Do this, this is from the Install.txt file
>
> Edit your php.ini file:
>
>    You will need to change the 'extension_dir' setting to
>    point to your php-install-dir, or where you have placed
>    your 'php_*.dll' files. ex: c:\php
>
>    If you are using OmniHTTPd, do not follow the next step.
>    Set the 'doc_root' to point to your webservers
>    document_root. ex: c:\apache\htdocs or c:\webroot
>
>    Choose which extensions you would like to load when PHP
>    starts, noting that several extensions are already built
>    into the Windows release, see the section about
>    Windows extensions for details of the built in extensions.
>    You can uncomment the: 'extension=php_*.dll' lines
>    in php.ini to load these extensions.
>    Some extensions require you to have additional libraries
>    installed on your system for the module to work correctly.
>    The PHP FAQ at www.php.net/FAQ.php has more information on
>    where to get supporting libraries. You can also load a
>    module dynamically in your script using dl. See the section
>    about Windows extensions.
>
>    Note that on a new installation it is advisable to first get
>    PHP working and tested without any extensions before enabling
>    them in php.ini.
> -----------------------------------------------------------------------
>
> Now do this:
>
> =======================
>
>  Installing PHP on Windows with Apache 1.3.x
>
>   There are two ways to set up PHP to work with Apache 1.3.x
>   on Windows. One is to use the CGI binary (php.exe),
>   the other is to use the Apache module dll. In either case
>   you need to stop the Apache server, and edit your
>   srm.conf or httpd.conf to configure Apache to work with PHP.
>
>   Although there can be a few variations of configuring PHP
>   under Apache, these are simple enough to be used by the
>   newcomer. Please consult the Apache Docs for further
>   configuration directives.
>
>   If you unzipped the PHP package to C:\PHP\ as desribed
>   above, you need to insert these lines to your Apache conf
>   file to set up the CGI binary:
>
>    ScriptAlias /php/ "c:/php/"
>    AddType application/x-httpd-php .php
>    Action application/x-httpd-php "/php/php.exe"
>
>   Remember to restart the server, for example,
>    NET STOP APACHE
>   followed by
>    NET START APACHE
>
>   If you would like to use PHP as a module in Apache,
>   you should move php4ts.dll to the windows/system (for Windows 9x/Me)
>   or winnt/system32 (for Windows NT/2000) directory, overwriting any
>   older file. Then you should add the following two lines to you Apache
>   conf file:
>
>    LoadModule php4_module c:/php/sapi/php4apache.dll
>    AddType application/x-httpd-php .php
>
>   Remember to restart the server, for example,
>    NET STOP APACHE
>   followed by
>    NET START APACHE
>
>   To use the source code highlighting feature, simply create a PHP
>   script file and stick this code in:
>    <?php show_source("original_php_script.php"); ?>
>   Substitute original_php_script.php with the name of the
>   file you wish to show the source of. (This is the only way of
>   doing so).
>
>   On Win-Apache all backslashes in a path statement such
>   as: "c:\directory\file.ext", must be converted to
>   forward slashes.
>
>
>



-- 
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to