sigmasternchen/php-doc-en
1
0
Fork 0
mirror of https://github.com/sigmasternchen/php-doc-en synced 2025-03-16 00:48:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

- restructering and rewriting of windows install instructions

Browse source 
- some duplicate information removed
- more verbose instructions which dlls where to copy


git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@122639 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Friedhelm Betz 2003-04-05 13:53:32 +00:00
parent 82829782b4
commit 0d110278bf
1 changed files with 393 additions and 303 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

696
chapters/install.windows.xml
View file

@ -1,11 +1,11 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.28 $ -->
<!-- $Revision: 1.29 $ -->
<sect1 id="install.windows">
<title>Installation on Windows systems</title>
<para>
This section applies to Windows 98/Me and Windows NT/2000/XP. PHP
will not work on 16 bit platforms such as Windows 3.1 and sometimes
we refer to the supported Windows platforms as Win32. Windows 95
we refer to the supported Windows platforms as Win32. Windows 95
is no longer supported as of PHP 4.3.0.
</para>
<para>
@ -29,117 +29,90 @@
<title>Windows InstallShield</title>
<para>
The Windows PHP installer 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>
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.
</para>
<note>
<para>
Also note, that while the InstallShield installer is an easy way to make
While the InstallShield 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.
automatic setup of extensions for example is not supported. The whole set
of supported extensions is only available by downloading the zip binary
distribution.
</para>
</note>
<simpara>
Install your selected <acronym>HTTP</acronym> server on your system
and make sure that it works.
Install your selected <acronym>HTTP</acronym> server on your system and
make sure that it works.
</simpara>
<simpara>
Run the executable installer and follow the instructions provided by
the installation wizard. Two types of installation are supported -
standard, which provides sensible defaults for all the settings it
can, and advanced, which asks questions as it goes along.
Run the executable installer and follow the instructions provided by the
installation wizard. Two types of installation are supported - standard,
which provides sensible defaults for all the settings it can, and advanced,
which asks questions as it goes along.
</simpara>
<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.
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.
</simpara>
<simpara>
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.
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>
<warning>
<para>
Be aware, that this setup of PHP is not secure. If you would
like to have a secure PHP setup, you'd better go on the manual
way, and set every option carefully. This automatically working
setup gives you an instantly working PHP installation, but it is
not meant to be used on online servers.
Be aware, that this setup of PHP is not secure. If you would like to have
a secure PHP setup, you'd better go on the manual way, and set every
option carefully. This automatically working setup gives you an instantly
working PHP installation, but it is not meant to be used on online servers.
</para>
</warning>
</sect2>
</sect2>
<sect2 id="install.windows.manual">
<title>Manual Installation Steps</title>
<simpara>
This install guide will help you manually install and configure
PHP on your Windows webserver. You need to download the
zip binary distribution from the downloads page at
<ulink url="&url.php.downloads;">&url.php.downloads;</ulink>. The
original version of this guide was compiled by &link.bob;, and can be
found at <ulink url="&url.win32install;">&url.win32install;</ulink>.
This install guide will help you manually install and configure PHP on your
Windows webserver. The original version of this guide was compiled by
&link.bob;, and can be found at
<ulink url="&url.win32install;">&url.win32install;</ulink>.
You need to download the zip binary distribution from the downloads page at
<ulink url="&url.php.downloads;">&url.php.downloads;</ulink>.
</simpara>
<para>
This guide provides manual installation support for:
<itemizedlist>
<listitem>
<para>
Personal Web Server 3 and 4 or newer
</para>
</listitem>
<listitem>
<para>
Internet Information Server 3 and 4 or newer
</para>
</listitem>
<listitem>
<para>
Apache 1.3.x
</para>
</listitem>
<listitem>
<para>
OmniHTTPd 2.0b1 and up
</para>
</listitem>
<listitem>
<para>
Oreilly Website Pro
</para>
</listitem>
<listitem>
<para>
Xitami
</para>
</listitem>
<listitem>
<para>
Netscape Enterprise Server, iPlanet
</para>
</listitem>
</itemizedlist>
</para>
<para>
PHP 4 for Windows comes in two flavours - a CGI executable (php.exe),
and several SAPI modules (for example: php4isapi.dll). The latter form
is new to PHP 4, and provides significantly improved performance and
some new functionality. There is also a CLI version which is
further described in the <link linkend="features.commandline">
commandline chapter</link>.
PHP 4 for Windows comes in three flavours - a CGI executable (php.exe), a
CLI executable (sapi/php.exe) and some other SAPI modules:
<simplelist>
<member>
<filename>php4apache.dll</filename> - Apache 1.3.x module
</member>
<member>
<filename>php4apache2.dll</filename> - Apache 2.0.x module
</member>
<member>
<filename>php4isapi.dll</filename> - ISAPI Module for ISAPI compliant
webservers like IIS 4.0/PWS 4.0 or newer.
</member>
<member>
<filename>php4nsapi.dll</filename> - Netscape/iPlanet module
</member>
</simplelist>
The latter form is new to PHP 4, and provides significantly improved
performance and some new functionality. The CLI version is designed to use
PHP for command line scripting. More information about CLI is available in
the chapter about
<link linkend="features.commandline">using PHP from the command line</link>
</para>
<warning>
<simpara>
@ -148,206 +121,284 @@
other server modules such as ASP failing, in older systems.
</simpara>
</warning>
<simpara>
If you choose one of the SAPI modules and use Windows 95, be sure
to download the DCOM update from the <ulink
url="&url.dcom.update;">Microsoft DCOM pages</ulink>. For the
ISAPI module, an ISAPI 4.0 compliant Web server is required
(tested on IIS 4.0, PWS 4.0 and IIS 5.0). IIS 3.0 is
<emphasis>NOT</emphasis> supported. You should download and
install the Windows NT 4.0 Option Pack with IIS 4.0 if you
want native PHP support.
</simpara>
<note>
<title>DCOM and MDAC requirements</title>
<para>
If you choose one of the SAPI modules and use
<emphasis>Windows 95</emphasis>, be sure to download and install the DCOM
update from the <ulink url="&url.dcom.update;">Microsoft DCOM pages</ulink>.
If you use Microsoft <emphasis>Windows 9x/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>.
</para>
</note>
<para>
The following steps should be performed on all installations
before the server specific instructions.
The following steps should be performed on all installations before any
server specific instructions.
<itemizedlist>
<listitem>
<simpara>
Extract the distribution file to a directory of your choice.
<filename>c:\php\</filename> is a good start. You probably
do not want to use a path in which spaces are included (for
example: c:\program files\php is not a good idea). Some
web servers will crash if you do.
Extract the distribution file to a directory of your choice,
<filename>c:\</filename> is a good start. The zip package expands to a
foldername like <filename>php-4.3.1-Win32</filename> which is assumed to
be renamed to <filename>php</filename>. For the sake of convinience and
to be version independant the following steps assume your extracted
version of PHP lives in <filename>c:\php</filename>. You might choose
any other location but you probably do not want to use a path in which
spaces are included (for example:
<filename>c:\program files\php</filename> is not a good idea). Some web
servers will crash if you do. The struture of your directory you
extracted the zip file will look like:
</simpara>
</listitem>
<listitem>
<simpara>
You need to ensure that the DLLs which PHP uses can be found.
The precise DLLs involved depend on which web server you use
and whether you want to run PHP as a CGI or as a server module.
<filename>php4ts.dll</filename> is always used. If you are
using a server module (e.g. ISAPI or Apache) then you will
need the relevant DLL from the <filename>sapi</filename>
folder. If you are using any PHP extension DLLs then you
will need those as well. To make sure that the DLLs can be
found, you can either copy them to the system directory
(e.g. <filename>winnt/system32</filename> or
<filename>windows/system</filename>) or you can make sure
that they live in the same directory as the main PHP
executable or DLL your web server will use (e.g.
<filename>php.exe</filename>, <filename>php4apache.dll</filename>).
</simpara>
</itemizedlist>
<informalexample>
<programlisting>
<![CDATA[
c:\php
|
+--cli
| |
| |-php.exe -- CLI executable - ONLY for commandline scripting
|
|
+--dlls -- support dlls for extensions --> windows system directory
| |
| |-expat.dll
| |
| |-fdftk.dll
| |
| |-...
|
+--extensions -- extension dlls for PHP
| |
| |-php_bz2.dll
| |
| |-php_cpdf.dll
| |
| |-..
|
+--mibs -- support files for SNMP
|
|
+--openssl -- support files for Openssl
|
|
+--pdf-related -- support files for PDF
|
|
+--sapi -- SAPI dlls
| |
| |-php4apache.dll
| |
| |-php4apache2.dll
| |
| |-php4isapi.dll
| |
| |-..
|
|-install.txt
|
|-..
|
|-php.exe -- CGI executable
|
|-..
|
|-php.ini-dist
|
|-php.ini-recommended
|
|-php4ts.dll -- main dll --> windows system directory
|
|-...
]]>
</programlisting>
</informalexample>
</para>
<para>
The CGI binary - <filename>C:/php/php.exe</filename> -, the CLI binary
- <filename>c:\php\cli\php.exe</filename> -, and the SAPI modules
- <filename>c:\php\sapi\*.dll</filename> - rely on the main dll
<filename>c:\php\php4ts.dll</filename>. You have to make sure, that this
dll can be found by your PHP installation. The search order for this dll
is as follows:
<simplelist>
<member>
The same directory from where <filename>php.exe</filename> is called.
In case you use a SAPI module the same directory from where your
webserver loads the dll (e.g. <filename>php4apache.dll</filename>).
</member>
<member>
Any directory in your Windows PATH environment variable.
</member>
</simplelist>
<itemizedlist>
<listitem>
<para>
The PHP binary, the SAPI modules, and some extensions rely on
external DLLs for execution. Make sure that these DLLs in the
distribution exist in a directory that is in the Windows PATH.
For example, if you enable <literal>php_oci8.dll</literal> in
&php.ini; then you'll want to make sure the Oracle home directory
can be seen in PATH so PHP can find <literal>oci.dll</literal>.
</para>
<para>
The best bet to do it is to copy the files below into your
system directory, which is typically:
The best bet is to make <filename>php4ts.dll</filename> available,
regardless which interface (CGI or SAPI module) you plan to use. To do so,
you have to copy this dll to a directory on your Windows path. The best
place is your windows system directory:
<simplelist>
<member>
<filename>c:\windows\system</filename> for Windows 9x/ME
</member>
<member>
<filename>c:\winnt\system32</filename> for Windows NT/2000
<filename>c:\winnt\system32</filename> for Windows NT/2000 or
<filename>c:\winnt40\system32</filename> for NT/2000 server
</member>
<member>
<filename>c:\windows\system32</filename> for Windows XP
</member>
</simplelist>
The files to copy are:
<simplelist>
<member>
<filename>php4ts.dll</filename>, if it already exists there,
overwrite it
</member>
<member>
The files in your distribution's &apos;dlls&apos; directory.
If you have them already installed on your system, overwrite them
only if something doesn't work correctly (Before overwriting them,
it is a good idea to make a backup of them, or move them to
another folder - just in case something goes wrong).
</member>
</simplelist>
</para>
<para>
Download the latest version of the Microsoft Data Access Components
(MDAC) for your platform, especially if you use Microsoft Windows
9x/NT4. MDAC is available at <ulink url="&url.mdac;">&url.mdac;</ulink>.
If you plan to use a SAPI module from <filename>c:\php\sapi</filename>
and do not like to copy dlls to your Windows system directory, you have
the alternative choice to simply copy <filename>php4ts.dll</filename> to
the sapi folder of your extracted zip package,
<filename>c:\php\sapi</filename>.
</para>
</listitem>
<listitem>
<para>
Copy your chosen ini file (see below) to your
&apos;%WINDOWS%&apos; directory on Windows 9x/Me or to your
&apos;%SYSTEMROOT%&apos; directory under Windows NT/2000/XP
and rename it to &php.ini;. Your
&apos;%WINDOWS%&apos; or &apos;%SYSTEMROOT%&apos; directory is
typically:
<simplelist>
<member><filename>c:\windows</filename> for Windows 9x/ME/XP</member>
<member><filename>c:\winnt</filename> or <filename>c:\winnt40</filename> for NT/2000 servers</member>
</simplelist>
</para>
<para>
The next step is to set up a valid configuration file for PHP, &php.ini;.
There are two ini files distributed in the zip file,
<filename>php.ini-dist</filename> and
<filename>php.ini-optimized</filename>. We advise
you to use <filename>php.ini-optimized</filename>,
because we optimized the default settings in this
file for performance, and security. The best is to
study all 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.
<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 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 choosen ini-file to a directory where
PHP is able to find and rename it to &php.ini;. By default PHP searchs
&php.ini; in your Windows directory:
<simplelist>
<member>
On Windows 9x/ME/XP copy your choosen ini file to your
<filename> %WINDIR%</filename>, which is typically
<filename>c:\windows</filename>.
</member>
<member>
On Windows NT/2000 copy your choosen ini file to your
<filename>%WINDIR%</filename> or <filename>%SYSTEMROOT%</filename>,
which is typically <filename>c:\winnt</filename> or
<filename>c:\winnt40</filename> for NT/2000 servers.
</member>
</simplelist>
</para>
</listitem>
<listitem>
<para>
Edit your new &php.ini; file:
<itemizedlist>
<listitem>
<simpara>
You will need to change the 'extension_dir' setting to
point to your php-install-dir, or where you have placed
your <filename>php_*.dll</filename> files. Please do not
forget the last backslash. ex:
<filename>c:\php\extensions\</filename>
</simpara>
</listitem>
<listitem>
<simpara>
If you are using OmniHTTPd, do not follow the next step.
Set the 'doc_root' to point to your webservers
document_root. For example: <filename>c:\apache\htdocs</filename>
or <filename>c:\webroot</filename>
</simpara>
</listitem>
<listitem>
<simpara>
Choose which 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 a new installation
it is advisable to first get PHP working and tested
without any extensions before enabling them in
&php.ini;.
</simpara>
</listitem>
<listitem>
<simpara>
On PWS and IIS, you can set the <filename>browscap.ini</filename>
to point to:
<filename>c:\windows\system\inetsrv\browscap.ini</filename> on
Windows 9x/Me,
<filename>c:\winnt\system32\inetsrv\browscap.ini</filename> on
NT/2000, and
<filename>c:\windows\system32\inetsrv\browscap.ini</filename>
on XP.
</simpara>
</listitem>
<listitem>
<simpara>
Note that the <filename>mibs</filename> directory supplied
with the Windows distribution contains support files for
SNMP. This directory should be moved to
<filename>DRIVE:\usr\mibs</filename> (<filename>DRIVE</filename>
being the drive where PHP is installed.)
</simpara>
</listitem>
<listitem>
<simpara>
If you're using NTFS on Windows NT, 2000 or XP, make sure that
the user running the webserver has read permissions to your
&php.ini; (e.g. make it readable by Everyone).
</simpara>
</listitem>
</itemizedlist>
</para>
</listitem>
<listitem>
<para>
For PWS give execution permission to the webroot:
<itemizedlist>
<listitem>
<simpara>
Start PWS Web Manager
</simpara>
</listitem>
<listitem>
<simpara>
Edit Properties of the "Home"-Directory
</simpara>
</listitem>
<listitem>
<simpara>
Select the "execute"-Checkbox
</simpara>
</listitem>
</itemizedlist>
</para>
</listitem>
<simpara>
If you're using NTFS on Windows NT, 2000 or XP, make sure that
the user running the webserver has read permissions to your
&php.ini; (e.g. make it readable by Everyone).
</simpara>
</listitem>
</itemizedlist>
</para>
<para>
The following steps are optional.
<itemizedlist>
<listitem>
<para>
Edit your new &php.ini; file.
If you plan to use <link linkend="install.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:
<informalexample>
<programlisting role="ini">
<![CDATA[
doc_root = c:\inetpub // for IIS/PWS
doc_root = c:\apache\htdocs // for Apache
]]>
</programlisting>
</informalexample>
</para>
</listitem>
<listitem>
<simpara>
Choose which 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
a new installation it is advisable to first get PHP working and tested
without any extensions before enabling them in &php.ini;.
</simpara>
</listitem>
<listitem>
<simpara>
On PWS and IIS, you can set the
<link linkend="ini.browscap">browscap</link> configuration setting
to point to:
<filename>c:\windows\system\inetsrv\browscap.ini</filename> on
Windows 9x/Me,
<filename>c:\winnt\system32\inetsrv\browscap.ini</filename> on
NT/2000, and
<filename>c:\windows\system32\inetsrv\browscap.ini</filename>
on XP.
</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. Installation instructions for the following webservers are available:
<itemizedlist>
<listitem>
<simpara>
.. the <link linkend="install.iis">Windows server family</link>, Personal
Web server (PWS) 3 and 4 or newer; Internet Information Server (IIS) 3
and 4 or newer.
</simpara>
</listitem>
<listitem>
<simpara>
.. the Apache servers
<link linkend="install.apache.windows">Apache 1.3.x</link>, and
<link linkend="install.apache2.windows">Apache 2.x</link>.
</simpara>
</listitem>
<listitem>
<simpara>
.. the
<link linkend="install.netscape.windows">Netscape/iPlanet</link> servers.
</simpara>
</listitem>
<listitem>
<simpara>
.. the <link linkend="install.omnihttpd">OmniHTTPd</link> server.
</simpara>
</listitem>
<listitem>
<simpara>
.. the <link linkend="install.oreilly">Oreilly Website Pro</link> server.
</simpara>
</listitem>
<listitem>
<simpara>
.. the <link linkend="install.sambar">Sambar</link> server.
</simpara>
</listitem>
<listitem>
<simpara>
.. the <link linkend="install.xitami">Xitami</link> server.
</simpara>
</listitem>
</itemizedlist>
</para>
</sect2>
<sect2 id="install.windows.build">
@ -629,7 +680,7 @@
</itemizedlist>
<simpara>
It is possible to do minor customization to the build process by editing
the <filename>main/config.win32.h.in</filename> file. For example you can
the <filename>main/config.win32.h</filename> file. For example you can
change the builtin extensions, the location of &php.ini; and
</simpara>
<simpara>
@ -661,13 +712,11 @@
<sect2 id="install.windows.extensions">
<title>Installation of Windows extensions</title>
<para>
After installing PHP and a webserver on Windows, you will
probably want to install some extensions for added functionality.
The following table describes some of the extensions available. You
can choose which extensions you would like to load when PHP starts
by uncommenting the: 'extension=php_*.dll' lines in
&php.ini;. You can also load a module dynamically
in your script using <function>dl</function>.
After installing PHP and a webserver on Windows, you will probably want to
install some extensions for added functionality. You can choose which
extensions you would like to load when PHP starts by modifying your
&php.ini;. You can also load a module dynamically in your script using
<function>dl</function>.
</para>
<para>
The DLLs for PHP extensions are prefixed with 'php_' in PHP 4 (and
@ -676,50 +725,91 @@
</para>
<note>
<para>
In PHP 4.3.1 BCMath, Calendar, COM, Ctype, FTP, MySQL, ODBC, Overload,
PCRE, Session, Tokenizer, WDDX, XML and Zlib support is <emphasis>built in</emphasis>.
You don't need to load any additional extensions in order to
use these functions. See your distributions
<filename>README.txt</filename> or <filename>install.txt</filename>
for a list of built in modules.
</para>
</note>
<note>
<para>
Some of these extensions need extra DLLs to work. Couple of them can be
found in the distribution package, in the &apos;dlls&apos; folder but
some, for example Oracle (php_oci8.dll) require DLLs which are
not bundled with the distribution package.
</para>
<para>
Copy the bundled DLLs from &apos;DLLs&apos; folder to your Windows
PATH, safe places are:
<simplelist>
<member>c:\windows\system for Windows 9x/Me</member>
<member>c:\winnt\system32 for Windows NT/2000</member>
<member>c:\windows\system32 for Windows XP</member>
</simplelist>
If you have them already installed on your system, overwrite them
only if something doesn't work correctly (Before overwriting them,
it is a good idea to make a backup of them, or move them to
another folder - just in case something goes wrong).
In PHP 4.3.1 BCMath, Calendar, COM, Ctype, FTP, MySQL, ODBC, Overload,
PCRE, Session, Tokenizer, WDDX, XML and Zlib support is
<emphasis>built in</emphasis>. You don't need to load any additional
extensions in order to use these functions. See your distributions
<filename>README.txt</filename> or <filename>install.txt</filename>
or <link linkend ="install.extensions.overview">this table</link>
for a list of built in modules.
</para>
</note>
<para>
<table>
<title>PHP Extensions</title>
<tgroup cols="3">
<thead>
<row>
<entry>Extension</entry>
<entry>Description</entry>
<entry>Notes</entry>
</row>
</thead>
<tbody>
Edit your &php.ini; file:
<itemizedlist>
<listitem>
<para>
You will need to change the
<link linkend ="ini.extension-dir">extension_dir</link> setting to
point to the directory where your extensions lives, or where you have
placed your <filename>php_*.dll</filename> files. Please do not
forget the last backslash. For example:
<informalexample>
<programlisting role="ini">
<![CDATA[
extension_dir = c:/php/extensions/
]]>
</programlisting>
</informalexample>
</para>
</listitem>
<listitem>
<para>
Enable the extension(s) in &php.ini; you want to use by uncommenting the
'extension=php_*.dll' lines in &php.ini;. This is done by deleting the
leading ; form the extension you want to load.
<example>
<title>enable <link linkend="ref.bzip2">Bzip2</link> extension</title>
<programlisting role="ini">
<![CDATA[
// change the following line from ...
;extension=php_bz2.dll
// ... too
extension=php_bz2.dll
]]>
</programlisting>
</example>
</para>
</listitem>
<listitem>
<para>
Some of the extensions need extra DLLs to work. Couple of them can be
found in the distribution package, in the
<filename>c:\php\dlls\</filename> folder but some, for example Oracle
(<filename>php_oci8.dll</filename>) require DLLs which are not bundled
with the distribution package. Copy the bundled DLLs from
<filename>c:\php\dlls</filename> folder to your Windows PATH, safe
places are:
<simplelist>
<member>c:\windows\system for Windows 9x/Me</member>
<member>c:\winnt\system32 for Windows NT/2000</member>
<member>c:\windows\system32 for Windows XP</member>
</simplelist>
If you have them already installed on your system, overwrite them only
if something doesn't work correctly (Before overwriting them, it is a
good idea to make a backup of them, or move them to another folder -
just in case something goes wrong).
</para>
</listitem>
</itemizedlist>
</para>
<para>
The following table describes some of the extensions available and required
additional dlls.
<table id="install.extensions.overview">
<title>PHP Extensions</title>
<tgroup cols="3">
<thead>
<row>
<entry>Extension</entry>
<entry>Description</entry>
<entry>Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry>php_bz2.dll</entry>
<entry><link linkend="ref.bzip2">bzip2</link> compression functions</entry>