2008-02-14 01:57:19 +00:00
|
|
|
|
<HTML>
|
|
|
|
|
|
<HEAD>
|
|
|
|
|
|
<TITLE>sane-scsi.5</TITLE>
|
|
|
|
|
|
</HEAD>
|
2008-02-11 01:50:42 +00:00
|
|
|
|
<BODY BGCOLOR=#FFFFFF TEXT=#000000><H1 ALIGN=CENTER><IMG SRC="/images/sane.png" HEIGHT=117 WIDTH=346></H1>
|
2008-02-14 01:57:19 +00:00
|
|
|
|
<H1>sane-scsi.5</H1>
|
|
|
|
|
|
<HR>
|
|
|
|
|
|
<PRE>
|
|
|
|
|
|
<!-- Manpage converted by man2html 3.0.1 -->
|
|
|
|
|
|
<B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B> SANE Scanner Access Now Easy <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</PRE>
|
|
|
|
|
|
<H2>NAME</H2><PRE>
|
|
|
|
|
|
sane-scsi - SCSI adapter tips for scanners
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</PRE>
|
|
|
|
|
|
<H2>DESCRIPTION</H2><PRE>
|
|
|
|
|
|
This manual page contains various operating-system specific tips and
|
|
|
|
|
|
tricks on how to get scanners with a SCSI interface working.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</PRE>
|
|
|
|
|
|
<H2>GENERAL INFO</H2><PRE>
|
|
|
|
|
|
For scanners with a SCSI interface, it may be necessary to edit the
|
|
|
|
|
|
appropriate backend configuration file before using SANE for the first
|
|
|
|
|
|
time. For most systems, the configuration file should list the name of
|
|
|
|
|
|
the generic SCSI device that the scanner is connected to (e.g., under
|
2012-08-27 01:52:45 +00:00
|
|
|
|
Linux, <B>/dev/sg4</B> or <B>/dev/sge</B> is such a generic SCSI device). It is cus‐
|
2008-02-14 01:57:19 +00:00
|
|
|
|
tomary to create a symlink from <B>/dev/scanner</B> to the generic SCSI device
|
|
|
|
|
|
that the scanner is connected to. In this case, the configuration file
|
|
|
|
|
|
simply lists the line <B>/dev/scanner</B>. For a detailed description of each
|
2012-08-27 01:52:45 +00:00
|
|
|
|
backend's configuration file, please refer to the relevant backend man‐
|
2008-02-14 01:57:19 +00:00
|
|
|
|
ual page (e.g., <B><A HREF="sane-epson.5.html">sane-epson(5)</A></B> for Epson scanners, <B><A HREF="sane-hp.5.html">sane-hp(5)</A></B> for HP
|
|
|
|
|
|
scanners, etc.).
|
|
|
|
|
|
|
|
|
|
|
|
For some operating systems (e.g. Linux and OS/2), there is an alternate
|
2012-08-27 01:52:45 +00:00
|
|
|
|
way of specifying scanner devices. This alternate way allows to iden‐
|
2008-02-14 01:57:19 +00:00
|
|
|
|
tify scanners by the SCSI vendor and model string and/or by the SCSI
|
2012-08-27 01:52:45 +00:00
|
|
|
|
device address (consisting of bus number, channel number, id, and logi‐
|
2008-02-14 01:57:19 +00:00
|
|
|
|
cal unit number). The syntax for specifying a scanner in this way is:
|
|
|
|
|
|
|
|
|
|
|
|
scsi <I>VENDOR</I> <I>MODEL</I> <I>TYPE</I> <I>BUS</I> <I>CHANNEL</I> <I>ID</I> <I>LUN</I>
|
|
|
|
|
|
|
|
|
|
|
|
where <I>VENDOR</I> is the SCSI vendor string, <I>MODEL</I> is the SCSI model string,
|
|
|
|
|
|
<I>TYPE</I> is type SCSI device type string, <I>BUS</I> is the SCSI bus number (named
|
|
|
|
|
|
"host" in /proc/scsi/scsi), <I>CHANNEL</I> is the SCSI channel number, <I>ID</I> is
|
|
|
|
|
|
the SCSI id, and <I>LUN</I> is the logical unit number of the scanner device.
|
|
|
|
|
|
The first two fields are strings which must be enclosed in double-
|
|
|
|
|
|
quotes if they contain any whitespace. The remaining four fields are
|
|
|
|
|
|
non-negative integer numbers. The correct values for these fields can
|
|
|
|
|
|
be found by using operating system specific tools, e.g. for Linux by
|
2012-08-27 01:52:45 +00:00
|
|
|
|
looking at the output of the command "cat /proc/scsi/scsi". To sim‐
|
2008-02-14 01:57:19 +00:00
|
|
|
|
plify configuration, a field's value can be replaced with an asterisk
|
2012-08-27 01:52:45 +00:00
|
|
|
|
symbol (``*''). An asterisk has the effect that any value is allowed
|
2008-02-14 01:57:19 +00:00
|
|
|
|
for that particular field. This can have the effect that a single
|
|
|
|
|
|
scsi-line matches multiple devices. When this happens, each matching
|
|
|
|
|
|
device will be probed by the backend one by one and registered if the
|
|
|
|
|
|
backend thinks it is a compatible device. For example, the line
|
|
|
|
|
|
|
|
|
|
|
|
scsi MUSTEK MFS-06000CX Scanner 0 00 03 00
|
|
|
|
|
|
|
|
|
|
|
|
would attach the Mustek SCSI scanner with the following /proc/scsi/scsi
|
|
|
|
|
|
entry:
|
|
|
|
|
|
|
|
|
|
|
|
Host: scsi0 Channel: 00 Id: 03 Lun: 00
|
|
|
|
|
|
Vendor: MUSTEK Model: MFS-06000CX Rev: 4.04
|
|
|
|
|
|
Type: Scanner ANSI SCSI revision: 0
|
|
|
|
|
|
|
|
|
|
|
|
Usually it's sufficient to use vendor and model strings only or even
|
|
|
|
|
|
only the vendor string. The following example
|
|
|
|
|
|
|
|
|
|
|
|
scsi MUSTEK * * * * * *
|
|
|
|
|
|
|
|
|
|
|
|
would have the effect that all SCSI devices in the system with a vendor
|
|
|
|
|
|
string of MUSTEK would be probed and recognized by the backend.
|
|
|
|
|
|
|
|
|
|
|
|
If the remainder of a scsi-string consists of asterisks only, the
|
2012-08-27 01:52:45 +00:00
|
|
|
|
asterisks can be omitted. For example, the following line is equiva‐
|
2008-02-14 01:57:19 +00:00
|
|
|
|
lent to the one specified previously:
|
|
|
|
|
|
|
|
|
|
|
|
scsi MUSTEK
|
|
|
|
|
|
|
|
|
|
|
|
On some platforms (e.g., OpenStep), SANE device names take a special
|
2012-08-27 01:52:45 +00:00
|
|
|
|
form. This is explained below in the relevant platform-specific sec‐
|
2008-02-14 01:57:19 +00:00
|
|
|
|
tion.
|
|
|
|
|
|
|
|
|
|
|
|
When using a SCSI scanner, ensure that the access permission for the
|
|
|
|
|
|
generic SCSI device is set appropriately. We recommend to add a group
|
|
|
|
|
|
"scanner" to /etc/group which contains all users that should have
|
|
|
|
|
|
access to the scanner. The permission of the device should then be set
|
|
|
|
|
|
to allow group read and write access. For example, if the scanner is
|
|
|
|
|
|
at generic SCSI device <B>/dev/sg0</B>, then the following two commands would
|
|
|
|
|
|
set the permission correctly:
|
|
|
|
|
|
|
|
|
|
|
|
$ chgrp scanner /dev/sg0
|
|
|
|
|
|
$ chmod 660 /dev/sg0
|
|
|
|
|
|
|
|
|
|
|
|
When your system uses the device filesystem (devfs), you have to edit
|
|
|
|
|
|
<B>/etc/devfs/perms.</B> There you should search the line
|
|
|
|
|
|
|
|
|
|
|
|
REGISTER ^sg[^/]* PERMISSIONS root.root 0600
|
|
|
|
|
|
|
|
|
|
|
|
and add a new line (eg. for changing permissions of sg4):
|
|
|
|
|
|
|
|
|
|
|
|
REGISTER ^sg4 PERMISSIONS root.scanner 0660
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</PRE>
|
|
|
|
|
|
<H2>FREEBSD INFO</H2><PRE>
|
|
|
|
|
|
Auto-configuration using the "scsi *" lines in the config files only
|
2012-08-27 01:52:45 +00:00
|
|
|
|
works if the user running the frontend has read/write access to
|
|
|
|
|
|
/dev/xpt0. Instead, you can also set a link <I>/dev/scanner</I> to the appro‐
|
2008-02-14 01:57:19 +00:00
|
|
|
|
priate /dev/uk device.
|
|
|
|
|
|
|
|
|
|
|
|
Adaptec AHA1542CF
|
|
|
|
|
|
Reported to work fine under FreeBSD 2.2.2R with the <B>aha</B>
|
|
|
|
|
|
driver.
|
|
|
|
|
|
|
|
|
|
|
|
Adaptec 2940
|
|
|
|
|
|
Reported to work fine under FreeBSD 2.2.2.
|
|
|
|
|
|
|
|
|
|
|
|
Adaptec 1522
|
|
|
|
|
|
The scanner probes ok but any attempt to access it <I>hangs</I>
|
|
|
|
|
|
the entire system. It looks like something is disabling
|
|
|
|
|
|
interrupts and then not re-enabling them, so it looks
|
|
|
|
|
|
like a bug in the FreeBSD <B>aic</B> driver.
|
|
|
|
|
|
|
|
|
|
|
|
Adaptec 1505
|
|
|
|
|
|
Works on FreeBSD 2.2.5R and 3.0 using the <B>aic</B> driver,
|
|
|
|
|
|
provided that Plug-and-Play support is disabled on the
|
2012-08-27 01:52:45 +00:00
|
|
|
|
card. If there are no <I>uk</I> devices, just do a ``sh MAKEDEV
|
2008-02-14 01:57:19 +00:00
|
|
|
|
uk0'' in the <B>/dev</B> directory. The scanner should then be
|
|
|
|
|
|
accessible as <B>/dev/uk0</B> <B>if</B> <B>it</B> <B>was</B> <B>probed</B> during boot.
|
|
|
|
|
|
|
|
|
|
|
|
Tekram DC390
|
|
|
|
|
|
Reported to work fine under FreeBSD 2.2.2R with the <B>amd</B>
|
|
|
|
|
|
driver.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</PRE>
|
|
|
|
|
|
<H2>LINUX INFO</H2><PRE>
|
|
|
|
|
|
First, make sure your kernel has SCSI generic support enabled. In
|
2012-08-27 01:52:45 +00:00
|
|
|
|
``make xconfig'', this shows up under ``SCSI support->SCSI generic sup‐
|
2008-02-14 01:57:19 +00:00
|
|
|
|
port''.
|
|
|
|
|
|
|
|
|
|
|
|
To keep scanning times to a minimum, it is strongly recommended to use
|
|
|
|
|
|
a large buffer size for the generic SCSI driver. From SG driver version
|
|
|
|
|
|
2.0 on, the maximum buffer size can be changed at program run time, and
|
|
|
|
|
|
there is no restriction in size. This driver version is part of the
|
|
|
|
|
|
Linux kernels from version 2.2.7 on. If the new SG driver is available
|
|
|
|
|
|
some backends (e.g. sane-umax, sane-mustek, sane-sharp) automatically
|
|
|
|
|
|
request larger scsi buffers. If a backend does not automatically
|
|
|
|
|
|
request a larger scsi buffer, set the environment variable
|
2012-08-27 01:52:45 +00:00
|
|
|
|
<B>SANE_SG_BUFFERSIZE</B> to the desired buffer size in bytes. It is not rec‐
|
|
|
|
|
|
ommended to use more than 1 MB, because for large values the probabil‐
|
|
|
|
|
|
ity increases that the SG driver cannot allocate the necessary buf‐
|
|
|
|
|
|
fer(s). For ISA cards, even 1 MB might be a too large value. For a
|
2008-02-14 01:57:19 +00:00
|
|
|
|
detailed discussion of memory issues of the SG driver, see
|
|
|
|
|
|
http://www.torque.net/sg.
|
|
|
|
|
|
|
|
|
|
|
|
For Linux kernels before version 2.2.7 the size of the buffer is only
|
|
|
|
|
|
32KB. This works, but for many cheaper scanners this causes scanning
|
|
|
|
|
|
to be slower by about a factor of four than when using a size of 127KB.
|
|
|
|
|
|
Linux defines the size of this buffer by macro <B>SG_BIG_BUFF</B> in header
|
|
|
|
|
|
file <I>/usr/include/scsi/sg.h</I>. Unless a system is seriously short on
|
|
|
|
|
|
memory, it is recommended to increase this value to the maximum legal
|
|
|
|
|
|
value of 128*1024-512=130560 bytes. After changing this value, it is
|
|
|
|
|
|
necessary to recompile both the kernel (or the SCSI generic module) and
|
|
|
|
|
|
the SCSI backends. Keep in mind that this is only necessary with older
|
|
|
|
|
|
Linux kernels.
|
|
|
|
|
|
|
|
|
|
|
|
A common issue with SCSI scanners is what to do when you booted the
|
|
|
|
|
|
system while the scanner was turned off? In such a case, the scanner
|
|
|
|
|
|
won't be recognized by the kernel and SANE won't be able to access it.
|
|
|
|
|
|
Fortunately, Linux provides a simple mechanism to probe a SCSI device
|
|
|
|
|
|
on demand. Suppose you have a scanner connected to SCSI bus 2 and the
|
|
|
|
|
|
scanner has a SCSI id of 5. When the system is up and running and the
|
|
|
|
|
|
scanner is turned on, you can issue the command:
|
|
|
|
|
|
|
|
|
|
|
|
echo "scsi add-single-device 2 0 5 0" > /proc/scsi/scsi
|
|
|
|
|
|
|
|
|
|
|
|
and the kernel will probe and recognize your scanner (this needs to be
|
|
|
|
|
|
done as root). It's also possible to dynamically remove a SCSI device
|
2012-08-27 01:52:45 +00:00
|
|
|
|
by using the ``remove-single-device'' command. For details, please
|
2008-02-14 01:57:19 +00:00
|
|
|
|
refer to to the SCSI-2.4-HOWTO.
|
|
|
|
|
|
|
|
|
|
|
|
Scanners are known to work with the following SCSI adapters under
|
|
|
|
|
|
Linux. This list isn't complete, usually any SCSI adapter supported by
|
|
|
|
|
|
Linux should work.
|
|
|
|
|
|
|
|
|
|
|
|
Acard/Advance SCSI adapters
|
|
|
|
|
|
Some old versions of the kernel driver (atp870u.c) cut
|
|
|
|
|
|
the inquiry information. Therefore the scanner couldn't
|
|
|
|
|
|
be detected correctly. Use a current kernel.
|
|
|
|
|
|
|
|
|
|
|
|
Adaptec AHA-1505/AHA-1542/AHA-2940
|
|
|
|
|
|
Reported to work fine with Linux since v2.0. If you
|
|
|
|
|
|
encounter kernel freezes or other unexpected behaviour
|
|
|
|
|
|
get the latest Linux kernel (2.2.17 seems to work) or
|
|
|
|
|
|
reduce SCSI buffer size to 32 kB.
|
|
|
|
|
|
|
|
|
|
|
|
ASUS SC200
|
|
|
|
|
|
Reported to work fine with Linux v2.0.
|
|
|
|
|
|
|
|
|
|
|
|
BusLogic BT958
|
|
|
|
|
|
To configure the BusLogic card, you may need to follow
|
|
|
|
|
|
these instructions (contributed by Jeremy
|
|
|
|
|
|
<jeremy@xxedgexx.com>): During boot, when your BusLogic
|
|
|
|
|
|
adapter is being initialized, press Ctrl-B to enter your
|
|
|
|
|
|
BusLogic adapter setup. Choose the address which your
|
|
|
|
|
|
BusLogic containing your scanner is located. Choose
|
2012-08-27 01:52:45 +00:00
|
|
|
|
``SCSI Device Configuration''. Choose ``Scan SCSI Bus''.
|
2008-02-14 01:57:19 +00:00
|
|
|
|
Choose whatever SCSI id that contains your scanner and
|
2012-08-27 01:52:45 +00:00
|
|
|
|
then choose ``View/Modify SCSI configuration''. Change
|
|
|
|
|
|
``Negotiation'' to ``async'' and change ``Disconnect'' to
|
|
|
|
|
|
``off''. Press Esc, save, and Esc again until you are
|
2008-02-14 01:57:19 +00:00
|
|
|
|
asked to reboot.
|
|
|
|
|
|
|
|
|
|
|
|
NCR/Symbios 53c400/53c400a or Domex DTC3181E/L/LE (DTCT436/436P)
|
|
|
|
|
|
ISA SCSI card
|
|
|
|
|
|
This card is supplied by Mustek (and other vendors). It's
|
2012-08-27 01:52:45 +00:00
|
|
|
|
supported since Linux 2.2. The SCSI cards are supported
|
|
|
|
|
|
by the module g_NCR5380. It's necessary to tell the ker‐
|
2008-02-14 01:57:19 +00:00
|
|
|
|
nel the io port and type of card. Example for a 53c400a:
|
2012-08-27 01:52:45 +00:00
|
|
|
|
``modprobe g_NCR5380 ncr_addr=0x280 ncr_53c400a=1''.
|
|
|
|
|
|
Once the kernel detects the card, it should work all
|
2008-02-14 01:57:19 +00:00
|
|
|
|
right. However, while it should work, do not expect good
|
2012-08-27 01:52:45 +00:00
|
|
|
|
performance out of this card---it has no interrupt line
|
|
|
|
|
|
and therefore while a scan is in progress, the system
|
|
|
|
|
|
becomes almost unusable. You may change the values of
|
|
|
|
|
|
the USLEEP macros in drivers/scsi/g_NCR5380.c. Some doc‐
|
2008-02-14 01:57:19 +00:00
|
|
|
|
umentation is in this file and NCR5380.c.
|
|
|
|
|
|
|
|
|
|
|
|
NCR/Symbios 810
|
2012-08-27 01:52:45 +00:00
|
|
|
|
For some scanners it may be necessary to disable discon‐
|
|
|
|
|
|
nect/reconnect. To achieve this use the option
|
|
|
|
|
|
ncr53c8xx="disc:n". Some people reported that their scan‐
|
2008-02-14 01:57:19 +00:00
|
|
|
|
ner only worked with the 53c7,8xx driver, not the
|
|
|
|
|
|
ncr53c8xx. Try both if you have trouble.
|
2012-08-27 01:52:45 +00:00
|
|
|
|
For Linux kernels before 2.0.33 it may be necessary to
|
|
|
|
|
|
increase the SCSI timeout. The default timeout for the
|
|
|
|
|
|
Linux kernels before 2.0.33 is 10 seconds, which is way
|
2008-02-14 01:57:19 +00:00
|
|
|
|
too low when scanning large area. If you get messages of
|
2012-08-27 01:52:45 +00:00
|
|
|
|
the form ``restart (ncr dead ?)'' in your /var/log/mes‐
|
|
|
|
|
|
sages file or on the system console, it's an indication
|
|
|
|
|
|
that the timeout is too short. In this case, find the
|
|
|
|
|
|
line ``if (np->latetime>10)'' in file ncr53c8xx.c (nor‐
|
|
|
|
|
|
mally in directory /usr/src/linux/drivers/scsi) and
|
|
|
|
|
|
change the constant 10 to, say, 60 (one minute). Then
|
2008-02-14 01:57:19 +00:00
|
|
|
|
rebuild the kernel/module and try again.
|
|
|
|
|
|
|
|
|
|
|
|
Tekram DC315
|
2012-08-27 01:52:45 +00:00
|
|
|
|
The driver can be downloaded from
|
|
|
|
|
|
http://www.garloff.de/kurt/linux/dc395/. For some older
|
|
|
|
|
|
scanners it may be necessary to disable all the more
|
2008-02-14 01:57:19 +00:00
|
|
|
|
advanced features by using e.g. modprobe dc395x_trm
|
|
|
|
|
|
dc395x_trm=7,5,1,32.
|
|
|
|
|
|
|
|
|
|
|
|
Tekram DC390
|
2012-08-27 01:52:45 +00:00
|
|
|
|
Version 1.11 of the Tekram driver seems to work fine
|
|
|
|
|
|
mostly, except that the scan does not terminate properly
|
2008-02-14 01:57:19 +00:00
|
|
|
|
(it causes a SCSI timeout after 10 minutes). The generic
|
|
|
|
|
|
AM53C974 also seems to work fine and does not suffer from
|
|
|
|
|
|
the timeout problems.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</PRE>
|
|
|
|
|
|
<H2>SOLARIS, OPENSTEP AND NEXTSTEP INFO</H2><PRE>
|
2012-08-27 01:52:45 +00:00
|
|
|
|
Under Solaris, OpenStep and NeXTStep, the generic SCSI device name
|
|
|
|
|
|
refers to a SCSI bus, not to an individual device. For example,
|
|
|
|
|
|
<B>/dev/sg0</B> refers to the first SCSI bus. To tell SANE which device to
|
|
|
|
|
|
use, append the character 'a'+target-id to the special device name.
|
2008-02-14 01:57:19 +00:00
|
|
|
|
For example, the SCSI device connected to the first SCSI controller and
|
|
|
|
|
|
with target-id 0 would be called <B>/dev/sg0a</B>, and the device with target-
|
|
|
|
|
|
id 1 on that same bus would be called <B>/dev/sg0b,</B> and so on.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</PRE>
|
|
|
|
|
|
<H2>ENVIRONMENT</H2><PRE>
|
|
|
|
|
|
<B>SANE_DEBUG_SANEI_SCSI</B>
|
2012-08-27 01:52:45 +00:00
|
|
|
|
If the library was compiled with debug support enabled, this
|
|
|
|
|
|
environment variable controls the debug level for the generic
|
|
|
|
|
|
SCSI I/O subsystem. E.g., a value of 128 requests all debug
|
|
|
|
|
|
output to be printed by the backend. A value of 255 also prints
|
|
|
|
|
|
kernel messages from the SCSI subsystem (where available).
|
2008-02-14 01:57:19 +00:00
|
|
|
|
Smaller levels reduce verbosity.
|
|
|
|
|
|
|
|
|
|
|
|
<B>SANE_SCSICMD_TIMEOUT</B>
|
2012-08-27 01:52:45 +00:00
|
|
|
|
sets the timeout value for SCSI commands in seconds. Overriding
|
|
|
|
|
|
the default value of 120 seconds should only be necessary for
|
2008-02-14 01:57:19 +00:00
|
|
|
|
very slow scanners.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</PRE>
|
|
|
|
|
|
<H2>SEE ALSO</H2><PRE>
|
|
|
|
|
|
<B><A HREF="sane.7.html">sane(7)</A></B>, <B><A HREF="sane-find-scanner.1.html">sane-find-scanner(1)</A></B>, <B>sane-"backendname"</B>(5), <B><A HREF="sane-usb.5.html">sane-usb(5)</A></B>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
</PRE>
|
|
|
|
|
|
<H2>AUTHOR</H2><PRE>
|
|
|
|
|
|
David Mosberger
|
|
|
|
|
|
|
2009-05-03 21:14:31 +00:00
|
|
|
|
14 Jul 2008 <B><A HREF="sane-scsi.5.html">sane-scsi(5)</A></B>
|
2008-02-14 01:57:19 +00:00
|
|
|
|
</PRE>
|
|
|
|
|
|
<HR>
|
|
|
|
|
|
<ADDRESS>
|
|
|
|
|
|
Man(1) output converted with
|
|
|
|
|
|
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
|
|
|
|
|
|
</ADDRESS>
|
|
|
|
|
|
</BODY>
|
|
|
|
|
|
</HTML>
|
