<listitem><para>Error correction via Microcom Network Protocol (MNP) classes
1-4</para>
</listitem>
<listitem><para>Error correction via the V.42 error correction standard</para>
</listitem>
<listitem><para>MNP class 5 for up to 2x data compression</para>
</listitem>
<listitem><para>V.42bis for up to 4x data compression</para>
</listitem>
<listitem><para>"Adaptive Rate Negotiation" which provides for "Fallback /
Fallforward" as line quality deteriorates or improves</para>
</listitem>
</itemizedlist>
<para>Your modem contains 56K technology. To take advantage of this
technology, you must first make sure that your Internet Service
Provider (ISP) supports a 56K modem protocol. Significantly
higher modem connection speeds, up to 56kbps, require all-digital
transmission connections from your ISP to the line card in the
central office from which your phone line is connected. The
actual connection rate may be limited by the quality of your
telephone lines. Telephone line quality may vary from location to location.
Current regulations limit maximum trasfer rates to 53K. While
your modem contains 56K technology, typical maximum connection
rates in the receive direction may be significantly less than
56K. Currently, 56K capability is for the receive direction
only. The transmit direction uses V.34 technology.
</para>
</sect2>
</sect1>
<sect1 ID="Startup">
<title>Compilation, Installation, and Startup</title>
<sect2 ID="Prerequisites">
<title>Prerequisites</title>
<itemizedlist>
<listitem>
<para>A 2.2.16 series (or later) Linux kernel source tree</para>
</listitem>
<listitem>
<para>An appropriate set of module utilities</para>
</listitem>
<listitem>
<para>gcc version 2.7.x or later</para>
</listitem>
</itemizedlist>
<para>If you are building the ACP Modem driver along with the user space application,
you need to have a complete Linux source tree for your
kernel, not just an up-to-date kernel image.</para>
</sect2>
<sect2 ID="Building">
<title>Building and Installing Source</title>
<orderedlist>
<listitem><para>Use <command>tar xzvf</command> <filename>mwavem-yyyymmdd.tar.gz</filename> to unpack the distribution.</para></listitem>
<listitem><para>Change directories with <command>cd <filename>mwavem-yyyymmdd</filename></command></para></listitem>
<listitem><para>Use the <command>./configure</command> command to configure the build options. Issue <command>./configure --help</command> to view all of the options. The defaults are probably okay though.</para>
<note><title>NOTE</title> <para>As of mwavem-1.0.3 you must give ./configure the --enable-mwavedd argument in order to build the driver with the user space application.</para></note></listitem>
<listitem><para>Use the <command>make</command> command to build all of the ACP Modem binaries.</para>
<note><title>NOTE</title> <para>Your gcc package should be at least at the 2.7.x level.
Check your <filename>/usr/src/linux/Documentation/Changes</filename> file for
the minimum version information.</para>
</note></listitem>
<listitem><para>Use <command>make install</command> to install the <filename>mwavem</filename> binary, <filename>mwavem.conf</filename> configuration, the extra binary (mostly .dsp) files, and module device driver
(if you specified that it must be built) and to create the <filename>/dev/modems/mwave</filename> device node. </para></listitem>
</orderedlist>
</sect2>
<sect2 ID="Setup">
<title>Setting Things Up</title>
<para>In the [WORLDTRADE] section of your <filename>mwavem.conf</filename> file, set the Country=
parameter to your country access code.</para>
<note><title>NOTE</title> <para>The <filename>mwavem.conf</filename> file is installed in the <filename>/usr/local/etc</filename> directory unless you specified otherwise during the build process</para></note>
<para>Country information (including access codes) are listed in the
<filename>mwavem.conf</filename> file. For example, for France the following section is present:</para>
<programlisting>
[Telephony\Country List\33]
CountryCode=00000021
Name=France
SameAreaRule=0FG
LongDistanceRule=0FG
InternationsalRule=00EFG</programlisting>
<para>To set France to be your configured country in the [WORLDTRADE] section of
<para>An initialization script has been provided which may be used to
to start, stop, or check the status of the ACP Modem driver and application. It has been successfully run on the Debian, Slackware, SuSE, and Red Hat distributions and should run on any of their derivitives. If you are using
the runtime script, it will load the mwave device driver module, configure the serial port, and start the mwave manager for you.
All of the options which can be passed to the device driver module, along with some options for the script itself,
can be configured by uncommenting and editing the appropriate
variables at the beginning of the script.
</para>
<para>The <command>mwaved</command> startup script can be found in the <filename>src/mwavem</filename> directory of the source distribution. If you are running the Red Hat distribution, you can copy the script to your <filename>/etc/rc.d/init.d</filename> directory and issue the <command>ntsysv</command> command in order to enable it at boot time.
If not using Red Hat, see the documentation for your distribution for information on how to set this up to run at boot time.
</para>
<para>It is recommended that you use the provided <command>mwaved</command> script. If you are not using
the script, however, the following sections will describe how to manually start the device driver and application.</para>
<sect3 ID="Load">
<title>Loading the ACP device driver</title>
<para>To load the mwave device driver use
<screen>insmod mwave</screen> or
<screen>modprobe mwave</screen></para>
<para>The following arguments may be supplied with the <command>insmod</command> command:</para>
<note><title>NOTE</title><para> The following arguments are not persistent from boot to boot
(i.e. We are not saving them in the BIOS).</para></note>
<note><title>NOTE</title><para>The <command>mwave</command> is unable to check for resource conflicts. It is
your responsibility to ensure that none of the resources specified conflict with other (commonly PCMCIA) devices.</para></note>
<para>You can use the tpctl package on Linux or the Thinkpad™ configuration utility on Windows NT or DOS
to manage the configuration of Thinkpad™ related resources.</para>
</sect3>
<sect3 ID="execute">
<title>Running ACP Modem Application</title>
<orderedlist>
<listitem><para>Once the ACP device driver is loaded successfully, use the
<command>mwavem</command> command to execute the application.
<note><title>NOTE</title><para>The location of the <filename>mwavem.conf</filename> file
can be specified as an argument to the mwavem application. If not specified the
default location is assumed to be <filename>/usr/local/etc/mwavem.conf</filename> unless otherwise changed during the build process.</para></note></para></listitem>
<listitem><para>Setup the serial driver to recognize the UART provided by the
ACP driver.</para>
<screen>setserial /dev/ttyS0 autoconfig</screen>
<note><title>NOTE</title><para>Substitute /dev/ttyS0 to match the serial port you have
configured the DSP to use.</para></note>
<note><title>NOTE</title><para>You may wish to create a symbolic link from your modem device to your serial device for convenience. Example: <command>ln -s /dev/ttyS0 /dev/modem</command></para></note>
</listitem>
</orderedlist>
<para>The ACP Modem is now available for use by your favorite dialing application.</para>
</sect3>
</sect2>
</sect1>
<sect1 ID="problems">
<title>Resolving Installation and Configuration Problems</title>
<para>The following sections list solutions to possible problems you may experience.</para>
<sect2 ID="nostart">
<title>DSP Does Not Start</title>
<para>In order to recognize memory above 64 Meg, it may be necessary to append the "mem=" option to the kernel command line.
If you are using LILO for your boot loader, you would do this in the <filename>lilo.conf</filename> file.
For example, if you had a machine with 128 Meg you would type:</para>
<screen>append="mem=130496K"</screen>
<note><title>NOTE</title><para>Your statement must reflect 576K less than you actually
have. Specifying the full amount of memory will prevent the DSP from starting. In the above
example, the formula used to arrive at the proper number was 1024 * nMB - 576 = nK.</para></note>
<para>If you forget to run the Thinkpad™ utility to enable the ACP
Modem and you didn't specify any command line arguments when
inserting the mwave module (or it didn't work), you will receive a message in the syslog,