diff --git a/reference/uodbc/book.xml b/reference/uodbc/book.xml
index 763bb3d19a13..f3b655484aa8 100644
--- a/reference/uodbc/book.xml
+++ b/reference/uodbc/book.xml
@@ -10,32 +10,22 @@
  <preface xml:id="intro.uodbc">
   &reftitle.intro;
   <para>
-   In addition to normal ODBC support, the Unified ODBC functions in
-   PHP allow you to access several databases that have borrowed the
-   semantics of the ODBC API to implement their own API.  Instead of
-   maintaining multiple database drivers that were all nearly
-   identical, these drivers have been unified into a single set of
-   ODBC functions.
+   The ODBC extension allows you to use ODBC database drivers from
+   PHP, using the same functions in PHP for any driver.
   </para>
   <para>
-   The following databases are supported by the Unified ODBC
-   functions: <link xlink:href="&url.adabas;">Adabas D</link>,
+   The following drivers and driver managers have direct support:
    <link xlink:href="&url.ibmdb2;">IBM DB2</link>,
-   <link xlink:href="&url.iodbc;">iODBC</link>,
-   <link xlink:href="&url.solid;">Solid</link>, and
-   <link xlink:href="&url.sybase;">Sybase SQL Anywhere</link>.
+   <link xlink:href="&url.iodbc;">iODBC</link>, and
+   <link xlink:href="&url.unixodbc;">unixODBC</link>.
   </para>
   <note>
    <para>
-    With the exception of iODBC, there is no ODBC involved when 
-    connecting to the above databases. The functions that you 
-    use to speak natively to them just happen to share the same 
-    names and syntax as the ODBC functions. However, building PHP 
-    with iODBC support enables you to use any ODBC-compliant 
-    drivers with your PHP applications. More information on iODBC,
-    is available at <link xlink:href="&url.iodbc;">www.iodbc.org</link>
-    with the alternative unixODBC available at 
-    <link xlink:href="&url.unixodbc;">www.unixodbc.org</link>.
+    It is strongly recommended to use a driver manager like iODBC
+    or unixODBC with PHP. While you can use a driver directly with
+    the ODBC extension through building against it directly, a
+    driver manager provides better flexibility and compatibility.
+    On Windows, the system driver manager is always used.
    </para>
   </note>
  </preface>
diff --git a/reference/uodbc/configure.xml b/reference/uodbc/configure.xml
index 0b684f365269..ab8b5e1c990a 100644
--- a/reference/uodbc/configure.xml
+++ b/reference/uodbc/configure.xml
@@ -4,39 +4,6 @@
  &reftitle.install;
  <para>
   <variablelist>
-   <varlistentry xml:id="install.configure.with-adabas">
-    <term>
-     <option role="configure">--with-adabas[=DIR]</option>
-    </term>
-    <listitem>
-     <para>
-      Include Adabas D support. DIR is the Adabas base install directory, 
-      defaults to <filename>/usr/local</filename>.
-     </para>
-    </listitem>
-   </varlistentry>
-   <varlistentry xml:id="install.configure.with-sapdb">
-    <term>
-     <option role="configure">--with-sapdb[=DIR]</option>
-    </term>
-    <listitem>
-     <para>
-      Include SAP DB support. DIR is SAP DB base install directory, 
-      defaults to <filename>/usr/local</filename>.
-     </para>
-    </listitem>
-   </varlistentry>
-   <varlistentry xml:id="install.configure.with-solid">
-    <term>
-     <option role="configure">--with-solid[=DIR]</option>
-    </term>
-    <listitem>
-     <para>
-      Include Solid support. DIR is the Solid base install directory, 
-      defaults to <filename>/usr/local/solid</filename>.
-     </para>
-    </listitem>
-   </varlistentry>
    <varlistentry xml:id="install.configure.with-ibm-db2">
     <term>
      <option role="configure">--with-ibm-db2[=DIR]</option>
@@ -48,41 +15,6 @@
      </para>
     </listitem>
    </varlistentry>
-   <varlistentry xml:id="install.configure.with-empress">
-    <term>
-     <option role="configure">--with-empress[=DIR]</option>
-    </term>
-    <listitem>
-     <para>
-      Include Empress support. DIR is the Empress base install directory, 
-      defaults to <varname>$EMPRESSPATH</varname>. This
-      option only supports  Empress Version 8.60 and above.
-     </para>
-    </listitem>
-   </varlistentry>
-   <varlistentry xml:id="install.configure.with-empress-bcs">
-    <term>
-     <option role="configure">--with-empress-bcs[=DIR]</option>
-    </term>
-    <listitem>
-     <para>
-      Include <literal>"Empress Local Access"</literal> support. DIR is the Empress base 
-      install directory, defaults to <varname>$EMPRESSPATH</varname>.
-      This option only supports Empress Version 8.60 and above.
-     </para>
-    </listitem>
-   </varlistentry>
-   <varlistentry xml:id="install.configure.with-birdstep">
-    <term>
-     <option role="configure">--with-birdstep[=DIR]</option>
-    </term>
-    <listitem>
-     <para>
-      Include Birdstep support. DIR is the Birdstep base install directory, 
-      defaults to <filename>/usr/local/birdstep</filename>.
-     </para>
-    </listitem>
-   </varlistentry>
    <varlistentry xml:id="install.configure.with-custom-odbc">
     <term>
      <option role="configure">--with-custom-odbc[=DIR]</option>
@@ -113,17 +45,6 @@
      </para>
     </listitem>
    </varlistentry>
-   <varlistentry xml:id="install.configure.with-esoob">
-    <term>
-     <option role="configure">--with-esoob[=DIR]</option>
-    </term>
-    <listitem>
-     <para>
-      Include Easysoft OOB support. DIR is the OOB base install directory, 
-      defaults to <filename>/usr/local/easysoft/oob/client</filename>.
-     </para>
-    </listitem>
-   </varlistentry>
    <varlistentry xml:id="install.configure.with-unixodbc">
     <term>
      <option role="configure">--with-unixODBC[=DIR]</option>
@@ -135,29 +56,6 @@
      </para>
     </listitem>
    </varlistentry>
-   <varlistentry xml:id="install.configure.with-openlink">
-    <term>
-     <option role="configure">--with-openlink[=DIR]</option>
-    </term>
-    <listitem>
-     <para>
-      Include OpenLink ODBC support. DIR is the OpenLink base install directory, 
-      defaults to <filename>/usr/local</filename>. This is the same as iODBC.
-     </para>
-    </listitem>
-   </varlistentry>
-   <varlistentry xml:id="install.configure.with-dbmaker">
-    <term>
-     <option role="configure">--with-dbmaker[=DIR]</option>
-    </term>
-    <listitem>
-     <para>
-      Include DBMaker support. DIR is the DBMaker base install directory, 
-      defaults to where the latest version of DBMaker is installed 
-      (such as <filename>/home/dbmaker/3.6</filename>).
-     </para>
-    </listitem>
-   </varlistentry>
   </variablelist>
  </para>
  <simpara>
diff --git a/reference/uodbc/functions/odbc-fetch-array.xml b/reference/uodbc/functions/odbc-fetch-array.xml
index 400cc371b3a5..1c873f1bbec5 100644
--- a/reference/uodbc/functions/odbc-fetch-array.xml
+++ b/reference/uodbc/functions/odbc-fetch-array.xml
@@ -77,7 +77,7 @@
   &reftitle.notes;
   <note>
    <simpara>
-    This function exists when compiled with DBMaker, IBM DB2 or UnixODBC support.
+    This function exists when compiled with IBM DB2, iODBC, or UnixODBC support.
    </simpara>
   </note>
  </refsect1>
diff --git a/reference/uodbc/functions/odbc-fetch-object.xml b/reference/uodbc/functions/odbc-fetch-object.xml
index 318446855c96..1cc3b1c7e0fc 100644
--- a/reference/uodbc/functions/odbc-fetch-object.xml
+++ b/reference/uodbc/functions/odbc-fetch-object.xml
@@ -77,7 +77,7 @@
   &reftitle.notes;
   <note>
    <simpara>
-    This function exists when compiled with DBMaker, IBM DB2 or UnixODBC support.
+    This function exists when compiled with IBM DB2, iODBC, or UnixODBC support.
    </simpara>
   </note>
  </refsect1>