Sophie: php-manual-en-4.3.0-2mdk noarch

php-manual-en-4.3.0-2mdk.noarch.rpm

<HTML
><HEAD
><TITLE
>Installation</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="PHP Manual"
HREF="index.html"><LINK
REL="UP"
TITLE="FAQ: Frequently Asked Questions"
HREF="faq.html"><LINK
REL="PREVIOUS"
TITLE="Database issues"
HREF="faq.databases.html"><LINK
REL="NEXT"
TITLE="Build Problems"
HREF="faq.build.html"><META
HTTP-EQUIV="Content-type"
CONTENT="text/html; charset=ISO-8859-1"></HEAD
><BODY
CLASS="chapter"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>PHP Manual</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="faq.databases.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="faq.build.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="chapter"
><H1
><A
NAME="faq.installation"
>Chapter 48. Installation</A
></H1
><P
>&#13;   This section holds common questions about the way to install
   PHP. PHP is available for almost any OS (except maybe for 
   MacOS before OSX), and almost any web server.
  </P
><P
>&#13;   To install PHP, follow the instructions in the 
   <A
HREF="http://cvs.php.net/co.php/php4/INSTALL"
TARGET="_top"
>INSTALL</A
>
   file located in the distribution. Windows users should also read the 
   <A
HREF="http://cvs.php.net/co.php/php4/win32/install.txt"
TARGET="_top"
>install.txt</A
>
   file. There are also some helpful hints for Windows users
   <A
HREF="install.windows.html"
>here</A
>.
  </P
><DIV
CLASS="qandaset"
><DL
><DT
>1. <A
HREF="faq.installation.html#faq.installation.phpini"
>&#13;      Unix/Windows: Where should my <TT
CLASS="filename"
>php.ini</TT
> file be
      located?
     </A
></DT
><DT
>2. <A
HREF="faq.installation.html#faq.installation.nodata"
>&#13;      Unix: I installed PHP, but every time I load a document, I get the 
      message 'Document Contains No Data'! What's going on here?
     </A
></DT
><DT
>3. <A
HREF="faq.installation.html#faq.installation.processing"
>&#13;      Unix: I installed PHP using RPMS, but Apache isn't processing the 
      PHP pages! What's going on here?
     </A
></DT
><DT
>4. <A
HREF="faq.installation.html#faq.installation.compile"
>&#13;      Unix: I installed PHP 3 using RPMS, but it doesn't compile with
      the database support I need! What's going on here?
     </A
></DT
><DT
>5. <A
HREF="faq.installation.html#faq.installation.frontpage"
>&#13;      Unix: I patched Apache with the FrontPage extensions patch, and
      suddenly PHP stopped working. Is PHP incompatible with the
      Apache FrontPage extensions?
     </A
></DT
><DT
>6. <A
HREF="faq.installation.html#faq.installation.blankscreen"
>&#13;      Unix/Windows: I have installed PHP, but when I try to
      access a PHP script file via my browser, I get a blank screen.
     </A
></DT
><DT
>7. <A
HREF="faq.installation.html#faq.installation.500error"
>&#13;      Unix/Windows: I have installed PHP, but when try to
      access a PHP script file via my browser, I get a
      server 500 error.
     </A
></DT
><DT
>8. <A
HREF="faq.installation.html#faq.installation.undefinedsyms"
> 
      Some operating systems: I have installed PHP without errors,
      but when I try to start apache I get undefined symbol errors:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>[mybox:user /src/php4] root# apachectl configtest
 apachectl: /usr/local/apache/bin/httpd Undefined symbols:
  _compress
  _uncompress</PRE
></TD
></TR
></TABLE
>
     </A
></DT
><DT
>9. <A
HREF="faq.installation.html#faq.installation.cgierror"
>&#13;      Windows: I have installed PHP, but when I to access
      a PHP script file via my browser, I get the error:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>cgi error:
 The specified CGI application misbehaved by not
 returning a complete set of HTTP headers.
 The headers it did return are:</PRE
></TD
></TR
></TABLE
>
     </A
></DT
><DT
>10. <A
HREF="faq.installation.html#faq.installation.phpandiis"
>&#13;      Windows: I've followed all the instructions, but still can't
      get PHP and IIS to work together!
     </A
></DT
><DT
>11. <A
HREF="faq.installation.html#faq.installation.forceredirect"
>&#13;       When running PHP as CGI with IIS, PWS, OmniHTTPD or Xitami,
       I get the following error: <TT
CLASS="literal"
>Security Alert! PHP CGI 
       cannot be accessed directly.</TT
>.
     </A
></DT
><DT
>12. <A
HREF="faq.installation.html#faq.installation.findphpini"
>&#13;      How do I know if my <TT
CLASS="filename"
>php.ini</TT
> is being found and read?  It
      seems like it isn't as my changes aren't being implemented.
     </A
></DT
></DL
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.installation.phpini"
></A
><B
>1. </B
>
      Unix/Windows: Where should my <TT
CLASS="filename"
>php.ini</TT
> file be
      located?
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      By default on UNIX it should be in <TT
CLASS="filename"
>/usr/local/lib</TT
>
      which is <TT
CLASS="filename"
>&#60;install-path&#62;/lib</TT
>.
      Most people will want to change this at compile-time with the 
      <A
HREF="install.configure.html#install.configure.with-config-file-path"
>--with-config-file-path</A
>
      flag. You would, for example, set it with something like:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>--with-config-file-path=/etc</PRE
></TD
></TR
></TABLE
>
      And then you would copy <TT
CLASS="filename"
>php.ini-dist</TT
> from 
      the distribution to <TT
CLASS="filename"
>/etc/php.ini</TT
> and
      edit it to make any local changes you want.
     </P
><P
>&#13;      On Windows the default path for the <TT
CLASS="filename"
>php.ini</TT
> file is the Windows
      directory. If you're using the Apache webserver, <TT
CLASS="filename"
>php.ini</TT
> is first
      searched in the Apaches install directory, e.g. <TT
CLASS="filename"
>c:\program
      files\apache group\apache</TT
>. This way you can have
      different <TT
CLASS="filename"
>php.ini</TT
> files for different versions of Apache on the same
      machine.
     </P
><P
>&#13;     See also the chapter about the <A
HREF="configuration.html#configuration.file"
>configuration file</A
>.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.installation.nodata"
></A
><B
>2. </B
>
      Unix: I installed PHP, but every time I load a document, I get the 
      message 'Document Contains No Data'! What's going on here?
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      This probably means that PHP is having some sort of problem
      and is core-dumping. Look in your server error log to see if
      this is the case, and then try to reproduce the problem with
      a small test case. If you know how to use 'gdb', it is very
      helpful when you can provide a backtrace with your bug report
      to help the developers pinpoint the problem.  If you are using
      PHP as an Apache module try something like:
      <P
></P
><UL
><LI
><P
>&#13;         Stop your httpd processes
        </P
></LI
><LI
><P
>&#13;         gdb httpd
        </P
></LI
><LI
><P
>&#13;         Stop your httpd processes
        </P
></LI
><LI
><P
>&#13;         &#62; run -X -f /path/to/httpd.conf
        </P
></LI
><LI
><P
>&#13;         Then fetch the URL causing the problem with your browser
        </P
></LI
><LI
><P
>&#13;         &#62; run -X -f /path/to/httpd.conf
        </P
></LI
><LI
><P
>&#13;         If you are getting a core dump, gdb should inform you of this now
        </P
></LI
><LI
><P
>&#13;         type: bt
        </P
></LI
><LI
><P
>&#13;         You should include your backtrace in your bug report. This should be submitted to 
         <A
HREF="http://bugs.php.net/"
TARGET="_top"
>http://bugs.php.net/</A
> 
        </P
></LI
></UL
>
     </P
><P
>&#13;      If your script uses the regular expression functions
      (<A
HREF="function.ereg.html"
><B
CLASS="function"
>ereg()</B
></A
> and friends), you should make sure 
      that you compiled PHP and Apache with the same regular 
      expression package. This should happen automatically with
      PHP and Apache 1.3.x
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.installation.processing"
></A
><B
>3. </B
>
      Unix: I installed PHP using RPMS, but Apache isn't processing the 
      PHP pages! What's going on here?
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      Assuming you installed both Apache and PHP from RPM packages, 
      you need to uncomment or add some or all of the following lines
      in your <TT
CLASS="filename"
>http.conf</TT
> file:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
># Extra Modules
AddModule mod_php.c
AddModule mod_php3.c
AddModule mod_perl.c

# Extra Modules
LoadModule php_module         modules/mod_php.so
LoadModule php3_module        modules/libphp3.so     /* for PHP 3 */
LoadModule php4_module        modules/libphp4.so     /* for PHP 4 */
LoadModule perl_module        modules/libperl.so</PRE
></TD
></TR
></TABLE
>
      And add:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>AddType application/x-httpd-php3 .php3    /* for PHP 3 */
AddType application/x-httpd-php .php      /* for PHP 4 */</PRE
></TD
></TR
></TABLE
>
      ... to the global properties, or to the properties of the 
      VirtualDomain you want to have PHP support added to.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.installation.compile"
></A
><B
>4. </B
>
      Unix: I installed PHP 3 using RPMS, but it doesn't compile with
      the database support I need! What's going on here?
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      Due to the way PHP 3 built, it is not easy to build a
      complete flexible PHP RPM.  This issue is addressed in PHP 4.
      For PHP 3, we currently suggest you use the mechanism described in the
      INSTALL.REDHAT file in the PHP distribution.  If you insist on using
      an RPM version of PHP 3, read on...
     </P
><P
>&#13;      The RPM packagers are setting up the RPMS to install
      without database support to simplify installations <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>and</I
></SPAN
>
      because RPMS use /usr/ instead of the standard /usr/local/ directory for
      files. You need to tell the RPM spec file which databases to support
      and the location of the top-level of your database server.
     </P
><P
>&#13;      This example will explain the process of adding support for the
      popular MySQL database server, using the mod installation for Apache.
     </P
><P
>&#13;      Of course all of this information can be adjusted for any database
      server that PHP supports. We will assume you installed MySQL and Apache
      completely with RPMS for this example as well.
      <P
></P
><UL
><LI
><P
>&#13;         First remove mod_php3 : 
         <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>rpm -e mod_php3</PRE
></TD
></TR
></TABLE
>
	      </P
></LI
><LI
><P
>&#13;         Then get the source rpm and INSTALL it, NOT --rebuild
         <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>rpm -Uvh mod_php3-3.0.5-2.src.rpm</PRE
></TD
></TR
></TABLE
>
  	    </P
></LI
><LI
><P
>&#13;	       Then edit the <TT
CLASS="filename"
>/usr/src/redhat/SPECS/mod_php3.spec</TT
> file
	      </P
><P
>&#13;         In the %build section add the database support you want, and the path.
	      </P
><P
>&#13;         For MySQL  you would add
         <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>--with-mysql=/usr \</PRE
></TD
></TR
></TABLE
>
         The %build section will look something like this:
         <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>./configure --prefix=/usr \
	--with-apxs=/usr/sbin/apxs \
	--with-config-file-path=/usr/lib \
	--enable-debug=no \
	--enable-safe-mode \
	--with-exec-dir=/usr/bin \
	--with-mysql=/usr \
	--with-system-regex</PRE
></TD
></TR
></TABLE
>
	      </P
></LI
><LI
><P
>&#13;	       Once this modification is made then build the binary rpm as follows:
         <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>rpm -bb /usr/src/redhat/SPECS/mod_php3.spec</PRE
></TD
></TR
></TABLE
>
	      </P
></LI
><LI
><P
>&#13;	       Then install the rpm
         <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>rpm -ivh /usr/src/redhat/RPMS/i386/mod_php3-3.0.5-2.i386.rpm</PRE
></TD
></TR
></TABLE
>
	      </P
></LI
></UL
>
      Make sure you restart Apache, and you now have PHP 3 with MySQL support
      using RPM's. Note that it is probably much easier to just build
      from the distribution tarball of PHP 3 and follow the instructions in
      <TT
CLASS="filename"
>INSTALL.REDHAT</TT
> found in that distribution.
   	 </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.installation.frontpage"
></A
><B
>5. </B
>
      Unix: I patched Apache with the FrontPage extensions patch, and
      suddenly PHP stopped working. Is PHP incompatible with the
      Apache FrontPage extensions?
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      No, PHP works fine with the FrontPage extensions. The problem
      is that the FrontPage patch modifies several Apache structures,
      that PHP relies on. Recompiling PHP (using 'make clean ; make')
      after the FP patch is applied would solve the problem.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.installation.blankscreen"
></A
><B
>6. </B
>
      Unix/Windows: I have installed PHP, but when I try to
      access a PHP script file via my browser, I get a blank screen.
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      Do a 'view source' in the web browser and you will probably
      find that you can see the source code of your PHP script.
      This means that the web server did not send the script to
      PHP for interpretation. Something is wrong with the server
      configuration - double check the server configuration against
      the PHP installation instructions.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.installation.500error"
></A
><B
>7. </B
>
      Unix/Windows: I have installed PHP, but when try to
      access a PHP script file via my browser, I get a
      server 500 error.
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      Something went wrong when the server tried to run PHP. To
      get to see a sensible error message, from the command line,
      change to the directory containing the PHP executable
      (<TT
CLASS="filename"
>php.exe</TT
> on Windows) and run
      <TT
CLASS="literal"
>php -i</TT
>. If PHP has any problems running,
      then a suitable error message will be displayed which will
      give you a clue as to what needs to be done next. If you
      get a screen full of html codes (the output of the
      <A
HREF="function.phpinfo.html"
><B
CLASS="function"
>phpinfo()</B
></A
> function) then PHP is working,
      and your problem may be related to your server configuration
      which you should double check.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.installation.undefinedsyms"
></A
><B
>8. </B
> 
      Some operating systems: I have installed PHP without errors,
      but when I try to start apache I get undefined symbol errors:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>[mybox:user /src/php4] root# apachectl configtest
 apachectl: /usr/local/apache/bin/httpd Undefined symbols:
  _compress
  _uncompress</PRE
></TD
></TR
></TABLE
>
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      This has actually nothing to do with PHP, but with the MySQL
      client libraries. Some need --with-zlib, others do not. This
      is also covered in the MySQL FAQ.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.installation.cgierror"
></A
><B
>9. </B
>
      Windows: I have installed PHP, but when I to access
      a PHP script file via my browser, I get the error:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
CELLPADDING="5"
><TR
><TD
><PRE
CLASS="programlisting"
>cgi error:
 The specified CGI application misbehaved by not
 returning a complete set of HTTP headers.
 The headers it did return are:</PRE
></TD
></TR
></TABLE
>
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      This error message means that PHP failed to output anything
      at all. To get to see a sensible error message, from the
      command line, change to the directory containing the PHP
      executable (<TT
CLASS="filename"
>php.exe</TT
> on Windows) and run
      <TT
CLASS="literal"
>php -i</TT
>. If PHP has any problems running,
      then a suitable error message will be displayed which will
      give you a clue as to what needs to be done next. If you
      get a screen full of html codes (the output of the
      <A
HREF="function.phpinfo.html"
><B
CLASS="function"
>phpinfo()</B
></A
> function) then PHP is working.
     </P
><P
>&#13;      Once PHP is working at the command line, try accessing the
      script via the browser again. If it still fails then it
      could be one of the following:
     </P
><P
></P
><UL
><LI
><P
>&#13;        File permissions on your PHP script,
        <TT
CLASS="filename"
>php.exe</TT
>, <TT
CLASS="filename"
>php4ts.dll</TT
>,
        <TT
CLASS="filename"
>php.ini</TT
> or any PHP extensions you are trying to load are such
        that the anonymous internet user
        <TT
CLASS="literal"
>ISUR_&#60;machinename&#62;</TT
> cannot access them.
       </P
></LI
><LI
><P
>&#13;        The script file does not exist (or possibly isn't where you
        think it is relative to your web root directory). Note that
        for IIS you can trap this error by ticking the 'check file
        exists' box when setting up the script mappings in the
        Internet Services Manager. If a script file does not exist
        then the server will return a 404 error instead. There is
        also the additional benefit that IIS will do any
        authentication required for you based on the NTLanMan
        permissions on your script file.
       </P
></LI
></UL
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.installation.phpandiis"
></A
><B
>10. </B
>
      Windows: I've followed all the instructions, but still can't
      get PHP and IIS to work together!
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      Make sure any user who needs to run a PHP script has the rights
      to run <TT
CLASS="filename"
>php.exe</TT
>! IIS uses an anonymous user
      which is added at the time IIS is installed. This user needs
      rights to <TT
CLASS="filename"
>php.exe</TT
>. Also, any authenticated
      user will also need rights to execute <TT
CLASS="filename"
>php.exe</TT
>.
      And for IIS4 you need to tell it that PHP is a script engine.
      Also, you will want to read 
      <A
HREF="faq.installation.html#faq.installation.forceredirect"
>this faq</A
>.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.installation.forceredirect"
></A
><B
>11. </B
>
       When running PHP as CGI with IIS, PWS, OmniHTTPD or Xitami,
       I get the following error: <TT
CLASS="literal"
>Security Alert! PHP CGI 
       cannot be accessed directly.</TT
>.
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      You must set the <A
HREF="configuration.directives.html#ini.cgi.force-redirect"
>&#13;      cgi.force_redirect</A
> directive to <TT
CLASS="literal"
>0</TT
>.
      It defaults to <TT
CLASS="literal"
>1</TT
> so be sure the directive
      isn't commented out (with a <TT
CLASS="literal"
>;</TT
>).  Like
      all directives, this is set in <TT
CLASS="filename"
>php.ini</TT
>
     </P
><P
>&#13;      Because the default is <TT
CLASS="literal"
>1</TT
>, it's critical
      that you're 100% sure that the correct <TT
CLASS="filename"
>php.ini</TT
> file is being 
      read.  Read <A
HREF="faq.installation.html#faq.installation.findphpini"
>this faq</A
>
      for details.
     </P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><B
><DIV
CLASS="question"
><P
><A
NAME="faq.installation.findphpini"
></A
><B
>12. </B
>
      How do I know if my <TT
CLASS="filename"
>php.ini</TT
> is being found and read?  It
      seems like it isn't as my changes aren't being implemented.
     </P
></DIV
></B
><DIV
CLASS="answer"
><P
><B
> </B
>
      To be sure your <TT
CLASS="filename"
>php.ini</TT
> is being read by PHP, make a call to
      <A
HREF="function.phpinfo.html"
><B
CLASS="function"
>phpinfo()</B
></A
> and near the top will be a
      listing called <TT
CLASS="literal"
>Configuration File (php.ini)</TT
>.
      This will tell you where PHP is looking for <TT
CLASS="filename"
>php.ini</TT
> and
      whether or not it's being read.  If just a directory PATH exists
      than it's not being read and you should put your <TT
CLASS="filename"
>php.ini</TT
>
      in that directory.  If <TT
CLASS="filename"
>php.ini</TT
> is included within the PATH than 
      it is being read.
     </P
><P
>&#13;      If <TT
CLASS="filename"
>php.ini</TT
> is being read and you're running PHP as a module
      then be sure to restart PHP after making changes to <TT
CLASS="filename"
>php.ini</TT
>
     </P
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="faq.databases.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="faq.build.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Database issues</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="faq.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Build Problems</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>