philip Fri Aug 6 15:10:40 2004 EDT
Modified files:
/phpdoc/en/install/windows installer.xml manual.xml
Log:
A fairly major update.
http://cvs.php.net/diff.php/phpdoc/en/install/windows/installer.xml?r1=1.3&r2=1.4&ty=u
Index: phpdoc/en/install/windows/installer.xml
diff -u phpdoc/en/install/windows/installer.xml:1.3
phpdoc/en/install/windows/installer.xml:1.4
--- phpdoc/en/install/windows/installer.xml:1.3 Fri Jul 30 12:26:08 2004
+++ phpdoc/en/install/windows/installer.xml Fri Aug 6 15:10:40 2004
@@ -1,27 +1,28 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.3 $ -->
+<!-- $Revision: 1.4 $ -->
<sect1 id="install.windows.installer">
<title>Windows Installer</title>
<para>
The Windows PHP installer is available from the downloads page at
<ulink url="&url.php.downloads;">&url.php.downloads;</ulink>. This
- installs the <emphasis>CGI version</emphasis> of <literal>PHP</literal>
- and, for IIS, PWS, and Xitami, configures the web server as well.
+ installs the <emphasis>CGI version</emphasis> of PHP and for IIS, PWS,
+ and Xitami, it configures the web server as well. The installer does not
+ include any extra external PHP extensions (php_*.dll) as you'll only find
+ those in the Windows Zip Package and <acronym>PECL</acronym> downloads.
</para>
<note>
<para>
- While the windows installer is an easy way to make
- <literal>PHP</literal> work, it is restricted in many aspects, as
- automatic setup of extensions for example is not supported. The whole set
- of supported extensions is only available by downloading the zip binary
- distribution.
+ While the Windows installer is an easy way to make PHP work, it is
+ restricted in many aspects as, for example, the automatic setup of
+ extensions is not supported. Use of the installer isn't the preferred
+ method for installing PHP.
</para>
</note>
<simpara>
- Install your selected <acronym>HTTP</acronym> server on your system and
- make sure that it works.
+ First, install your selected <acronym>HTTP</acronym> (web) server on your
+ system, and make sure that it works.
</simpara>
<simpara>
@@ -33,14 +34,16 @@
<simpara>
The installation wizard gathers enough information to set up the &php.ini;
- file and configure the web server to use PHP. For IIS and also PWS on NT
- Workstation, a list of all the nodes on the server with script map settings
- is displayed, and you can choose those nodes to which you wish to add the
- PHP script mappings.
+ file, and configure certain web servers to use PHP. With IIS or PWS on
+ a NT Workstation, a list of all the nodes on the server with script map
+ settings is displayed, and you can choose those nodes to which you wish
+ to add the PHP script mappings. One of the web servers the PHP installer
+ does not configure for is Apache, so you'll need to configure it
+ manually.
</simpara>
<simpara>
- Once the installation has completed the installer will inform you if you
+ Once the installation has completed, the installer will inform you if you
need to restart your system, restart the server, or just start using PHP.
</simpara>
http://cvs.php.net/diff.php/phpdoc/en/install/windows/manual.xml?r1=1.11&r2=1.12&ty=u
Index: phpdoc/en/install/windows/manual.xml
diff -u phpdoc/en/install/windows/manual.xml:1.11
phpdoc/en/install/windows/manual.xml:1.12
--- phpdoc/en/install/windows/manual.xml:1.11 Thu Aug 5 08:53:24 2004
+++ phpdoc/en/install/windows/manual.xml Fri Aug 6 15:10:40 2004
@@ -1,32 +1,37 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.11 $ -->
+<!-- $Revision: 1.12 $ -->
<sect1 id="install.windows.manual">
<title>Manual Installation Steps</title>
<para>
- This install guide will help you manually install and configure PHP on your
- Microsoft Windows webserver. You need to download the zip binary distribution
- from the downloads page at
- <ulink url="&url.php.downloads;">&url.php.downloads;</ulink> to get started.
+ This install guide will help you manually install and configure PHP with
+ a web server on Microsoft Windows. To get started you'll need to download
+ the zip binary distribution from the downloads page at
+ <ulink url="&url.php.downloads;">&url.php.downloads;</ulink>.
</para>
<para>
- Although there are all-in-one installation kits and we also distribute an
- installer for Microsoft Windows, we recommend you to take some time and set
- up PHP yourself, since this provides better understanding of the system, and
- enables you to install PHP extensions easily whenever you need.
+ Although there are many all-in-one installation kits, and we also
+ distribute a PHP installer for Microsoft Windows, we recommend you take
+ the time to setup PHP yourself as this will provide you with a better
+ understanding of the system, and enables you to install PHP extensions
+ easily when needed.
</para>
<note id="install.windows.manual.upgrade">
<title>Upgrading from a previous PHP version</title>
<para>
- Previous editions of this manual suggested that you move ini files and DLLs
- around your folders, and thus you might have PHP related files in multiple
- folders on your hard drive. We advise you to remove all these files (php.ini
- from the Windows folder, PHP related DLLs from the Windows system folder),
- before going on with the installation. Make sure you have backups of those
- DLLs, since you might be able to brake your entire system. The old ini file
- might be useful in setting up your new PHP as well.
+ Previous editions of the manual suggest moving various ini and
+ <acronym>DLL</acronym> files into your SYSTEM (i.e.
+ <filename class="directory">C:\WINDOWS)</filename> folder and while this
+ simplifies the installation procedure it makes upgrading difficult. We
+ advise you remove all of these files (like &php.ini; and PHP related
+ DLLs from the Windows SYSTEM folder) before moving on with a new
+ PHP installation. Be sure to backup these files as you might break the
+ entire system. The old &php.ini; might be useful in setting up the new
+ PHP as well. And as you'll soon learn, the preferred method for
+ installing PHP is to keep all PHP related files in one directory and
+ have this directory available to your systems PATH.
</para>
</note>
@@ -36,26 +41,29 @@
If you use Microsoft <emphasis>Windows 98/NT4</emphasis> download the
latest version of the Microsoft Data Access Components (MDAC) for your
platform. MDAC is available at <ulink url="&url.mdac;">&url.mdac;</ulink>.
+ This requirement exists because <link linkend="ref.odbc">ODBC</link> is
+ built into the distributed Windows binaries.
</para>
</note>
<para>
- The following steps should be performed on all installations before any
- server specific instructions:
+ The following steps should be completed on all installations before any
+ server specific instructions are performed:
</para>
<para>
- Extract the distribution file to a directory of your choice, <filename
- class="directory">c:\</filename> is a good start. The zip package
- expands to a foldername like <filename>php-4.3.7-Win32</filename> which
- is assumed to be renamed to <filename>php</filename>. For the sake of
- convenience and to be version independent, the following steps assume
- your extracted version of PHP lives in <filename
- class="directory">C:\php</filename>. You might choose any other location
- but you probably do not want to use a path in which spaces are included.
- Using a folder, like <filename class="directory">C:\Program
- Files\PHP</filename> is not a good idea. Some web servers will crash if
- you do. The structure of your directory you extracted the zip file will
- look like:
+ Extract the distribution file into the directory of your choice,
+ <filename class="directory">c:\</filename> is a good start. The zip
+ package expands to a foldername like <filename>php-4.3.7-Win32</filename>
+ and for the sake of convenience, and to be version independent, the
+ following steps assume you renamed this directory and that the extracted
+ version of PHP lives in <filename class="directory">C:\php</filename>.
+ You may choose a different location but do not have spaces in the path
+ (like <filename class="directory">C:\Program Files\PHP</filename>) as
+ some web servers will crash if you do.
+ </para>
+ <para>
+ The directory structure extracted from the zip is different for PHP
+ versions 4 and 5 and look like as follows:
</para>
<example>
<title>PHP 4 package structure</title>
@@ -123,8 +131,7 @@
</programlisting>
</example>
<para>
- In case you have downloaded and extracted PHP 5, it has a somewhat
- different folder structure:
+ Or:
</para>
<example>
<title>PHP 5 package structure</title>
@@ -177,7 +184,11 @@
|-php.ini-recommended -- recommended php.ini settings
|
|-php5activescript.dll
- |
+ |
+ |-php5apache.dll
+ |
+ |-php5apache2.dll
+ |
|-..
|
|-php5ts.dll -- core PHP DLL
@@ -188,11 +199,14 @@
</programlisting>
</example>
<para>
- Note that PHP 4 and PHP 5 for Windows both have a CGI executable, a CLI
- executable and server modules, but they are located in different folders.
- While PHP 4 packages have the server modules in the sapi folder, these
- are included right in the PHP folder in PHP 5 distributions. The
- supporting DLLs for PHP extensions are also in the main PHP 5 folder.
+ Notice the differences and similarities. Both PHP 4 and PHP 5 have a
+ <acronym>CGI</acronym> executable, a <acronym>CLI</acronym> executable,
+ and server modules, but they are located in different folders and/or have
+ different names. While PHP 4 packages have the server modules in the
+ <filename class="directory">sapi</filename> folder, PHP 5
+ distributions have no such directory and instead they're in the PHP
+ folder root. The supporting DLLs for the PHP 5 extensions are also not
+ in a seperate directory.
</para>
<note>
<para>
@@ -219,7 +233,7 @@
</para></listitem>
<listitem><para>
<filename>sapi/php4isapi.dll (php5isapi.dll)</filename> - ISAPI Module
- for ISAPI compliant webservers like IIS 4.0/PWS 4.0 or newer.
+ for ISAPI compliant web servers like IIS 4.0/PWS 4.0 or newer.
</para></listitem>
<listitem><para>
<filename>sapi/php4nsapi.dll (php5nsapi.dll)</filename> - Sun/iPlanet/Netscape
@@ -232,7 +246,7 @@
</itemizedlist>
</para>
<para>
- Server modules provide significantly better performance and some more
+ Server modules provide significantly better performance and additional
functionality compared to the CGI binary. The CLI version is designed to
let you use PHP for command line scripting. More information about CLI is
available in the chapter about <link linkend="features.commandline">using
@@ -240,32 +254,36 @@
</para>
<warning>
<simpara>
- The SAPI modules have been significantly improved in the 4.1 release,
- however, you may find that you encounter possible server errors or other
- server modules such as ASP failing, in older systems.
+ The SAPI modules have been significantly improved as of the 4.1 release,
+ however, in older systems you may encounter server errors or other
+ server modules failing, such as ASP.
</simpara>
</warning>
<para>
The CGI and CLI binaries, and the web server modules all require the
<filename>php4ts.dll</filename> (<filename>php5ts.dll</filename>) file to
- be available to them. You have to make sure, that this file can be found
+ be available to them. You have to make sure that this file can be found
by your PHP installation. The search order for this DLL is as follows:
<itemizedlist>
- <listitem><para>
- The same directory from where <filename>php.exe</filename> is called,
- or in case you use a SAPI module, the webserver's directory (e.g.
- <filename>C:\Program Files\Apache Group\Apache2\bin</filename>).
- </para></listitem>
- <listitem><para>
- Any directory in your Windows <varname>PATH</varname> environment
- variable.
- </para></listitem>
+ <listitem>
+ <para>
+ The same directory from where <filename>php.exe</filename> is called,
+ or in case you use a SAPI module, the web server's directory (e.g.
+ <filename>C:\Program Files\Apache Group\Apache2\bin</filename>).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Any directory in your Windows <varname>PATH</varname> environment
+ variable.
+ </para>
+ </listitem>
</itemizedlist>
</para>
<para>
To make <filename>php4ts.dll</filename> / <filename>php5ts.dll</filename>
available you have three options: copy the file to the Windows system
- directory, copy the file to the webserver's directory, or add your PHP
+ directory, copy the file to the web server's directory, or add your PHP
directory, <filename class="directory">C:\php</filename> to the
<varname>PATH</varname>. For better maintenance, we advise you to follow
the last option, add <filename class="directory">C:\php</filename> to the
@@ -281,30 +299,46 @@
<filename>php.ini-recommended</filename>. We advise you to use
<filename>php.ini-recommended</filename>, because we optimized the
default settings in this file for performance, and security. Read this
- well documented file carefully and in addition study the <link
- linkend="configuration.file">ini settings</link> and set every element
+ well documented file carefully because it has changes from
+ <filename>php.ini-dist</filename> that will drastically affect your
+ setup. Some examples are <link linkend="ini.display-errors">
+ display_errors</link> being <literal>off</literal> and
+ <link linkend="ini.magic-quotes-gpc">magic_quotes_gpc</link> being
+ <literal>off</literal>. In addition to reading these, study the <link
+ linkend="configuration.file">ini settings</link> and set every element
manually yourself. If you would like to achieve the best security, then
this is the way for you, although PHP works fine with these default ini
- files. Copy your chosen ini-file to a directory where PHP is able to find
+ files. Copy your chosen ini-file to a directory that PHP is able to find
and rename it to &php.ini;. PHP searches for &php.ini; in the following
- places (in order):
+ locations (in order):
<itemizedlist>
- <listitem><para>
- PHPIniDir directive (Apache 2 module only)
- </para></listitem>
- <listitem><para>
- <literal>HKEY_LOCAL_MACHINE\SOFTWARE\PHP\IniFilePath</literal>
- </para></listitem>
- <listitem><para>
- <varname>PHPRC</varname> environment variable
- </para></listitem>
- <listitem><para>
- Directory of PHP (for CLI) or the webserver's dir (for SAPI modules)
- </para></listitem>
- <listitem><para>
- Windows directory (<filename class="directory">C:\windows</filename> or
- <filename class="directory">C:\winnt</filename>)
- </para></listitem>
+ <listitem>
+ <para>
+ PHPIniDir directive (Apache 2 module only)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>HKEY_LOCAL_MACHINE\SOFTWARE\PHP\IniFilePath</literal>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <varname>PHPRC</varname> environment variable
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Directory of PHP (for CLI), or the web server's directory (for
+ SAPI modules)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Windows directory (<filename class="directory">C:\windows</filename>
+ or <filename class="directory">C:\winnt</filename>)
+ </para>
+ </listitem>
</itemizedlist>
</para>
<para>
@@ -312,12 +346,12 @@
directive (read the <link linkend="install.windows.apache2">installation
on Apache 2</link> page), otherwise your best option is to set the
<varname>PHPRC</varname> environment variable. This process is explained
- in a <link linkend="faq.installation.phprc">FAQ entry</link>.
+ in the following <link linkend="faq.installation.phprc">FAQ entry</link>.
</para>
<note>
<simpara>
If you're using NTFS on Windows NT, 2000, XP or 2003, make sure that the
- user running the webserver has read permissions to your &php.ini; (e.g.
+ user running the web server has read permissions to your &php.ini; (e.g.
make it readable by Everyone).
</simpara>
</note>
@@ -329,12 +363,12 @@
Edit your new &php.ini; file.
If you plan to use <link linkend="install.windows.omnihttpd">OmniHTTPd</link>,
do not follow the next step. Set the
- <link linkend="ini.doc-root">doc_root</link> to point to your webservers
- document_root. For example:
+ <link linkend="ini.doc-root">doc_root</link> to point to your
+ web servers document_root. For example:
<informalexample>
<programlisting role="ini">
<![CDATA[
-doc_root = c:\inetpub // for IIS/PWS
+doc_root = c:\inetpub // for IIS/PWS
doc_root = c:\apache\htdocs // for Apache
]]>
@@ -344,7 +378,7 @@
</listitem>
<listitem>
<simpara>
- Choose which extensions you would like to load when PHP starts. See
+ Choose the extensions you would like to load when PHP starts. See
the section about
<link linkend="install.windows.extensions">Windows extensions</link>,
about how to set up one, and what is already built in. Note that on
@@ -362,15 +396,16 @@
<filename>c:\winnt\system32\inetsrv\browscap.ini</filename> on
NT/2000, and
<filename>c:\windows\system32\inetsrv\browscap.ini</filename>
- on XP.
+ on XP. For an up-to-date <filename>browscap.ini</filename>, read the
+ following <link linkend="faq.obtaining.browscap">FAQ</link>.
</simpara>
</listitem>
</itemizedlist>
</para>
<para>
- Following this instructions you are done with the basic steps to setup PHP
- on Windows. The next step is to choose a webserver and enable it to run
- PHP. Pick a webserver from the table of contents.
+ PHP is now setup on your system. The next step is to choose a web
+ server, and enable it to run PHP. Choose a webserver from the table of
+ contents.
</para>
</sect1>
