


                            Manual Installation

First create a subdirectory on your OS/2 boot drive named SIO2K. Then place
all of the distribution files into this directory.

Edit your CONFIG.SYS file and REM out all other serial drivers such as
COM.SYS and VCOM.SYS, or SIO.SYS, VSIO.SYS and VX00.SYS.

Applying appropriate modifications, add the following lines to the end of
your CONFIG.SYS:

device=c:\sio2k\uart.sys logfile=c:\sio2k\sio2k.log
device=c:\sio2k\vsio2k.sys logfile=c:\sio2k\vsio2k.log vIrqList(3,4)
device=c:\sio2k\sio2k.sys logfile=c:\sio2k\sio2k.log

NOTE THAT SIO2K.SYS MUST BE THE LAST DRIVER LOADED IN THE SIO2K SET.

The simplest form of loading the drivers is:

device=c:\sio2k\uart.sys
device=c:\sio2k\vsio2k.sys vIrqList(3,4)
device=c:\sio2k\sio2k.sys

If you wish to use Vmodem, see VMODEM.TXT.

The above assumes your boot drive is drive C.  A current kludge, that I
hope to eliminate, is that one must identify the virtual IRQs, that
VSIO2K.SYS (Dos/Windows sessions) is to service, at boot time (in its
command line).  The "vIrqList(3,4)" fragment of the VSIO2K.SYS command line
serves this purpose.  This says that any Dos/Win comm pott is going to use
either virtual IRQ 3, or virtual IRQ 4.  Note that the virtual IRQs have
nothing to do with the real (hardware) IRQs.

Common command line options:
All of the drivers in the sio2k set share some common command line options. 
They are:
     NOPAUSE - This command line option instructs the driver not to pause
     (at boot time) when a command line option error is detected.

     LOGFILE - In the form LogFike=c:\path\filename.log.  This command line
     option tells the driver where to place information that may be useful
     to the user.

VMODEM.SYS - In addition to the common command line options, VMODEM.SYS has
the following command line option(s):

     NPORTS - In the form nPorts=5.  This example informs VMODEM.SYS to
     define 5 virtual modem ports.  If the NPORTS option is missing,
     VMODEM.SYS will define 1 virtual modem port.

UART.SYS - In addition to the common command line options, UART.SYS has the
following command line option(s):

     LEGACYISA - In the form LegacyIsa(0E80,1a0,208), where 0E80, 1a0, and
     208 are the I/O address of uarts.  DO NOT specify legacy ISA ports
     that are at standard addresses like 3f8, 2f8, 3e8 and 2e8 unless these
     ports are not automatically being detected by UART.SYS.  UART.SYS will
     automatically detect the uart type, fifo size and IRQ that the uart is
     using, so only the I/O port address is needed.


The CONFIG file:

The vast majority of users DO NOT need a config file.  The drivers will
probably do a better job of automatically self configuring than you can do.

However, for those of you that insist on complete control, and have self
masochistic tendencies, you can create a config file.  If you choose to use
a config file, then the SIO2K drivers assume almost nothing and you MUST
define everything.

Also, I do not have time to create a config file for you, you are on your
own.  You may however, report errors in the config file processing.

First, install as above (with no config file).  With no config file, you
access COM1 to COM4 at their standard I/O addresses and ports on PCI cards.

After testing using no config file, one can play with additional features
of SIO version 2, by using an optional config file.  Currently, the config
file must be in the same directory that the driver files were loaded from,
and the config file name must be SIO2K.CFG.

Currently, the only documentation for the config file is located in
SAMPLE.CFG.

First, one should simply copy SAMPLE.CFG to SIO2K.CFG, reboot and see what
happens.  If the boot is successful, you can SLOWLY make changes to the
config file (re-booting often) to test/use additional features of SIO
version 2.

If you have a Hayes ESP card (note the ESP is NOT a modem) the change the
AltDriver statement (in the config file) should be AltDriver=esp$,n in
place of AltDriver=uart$,n.  The command line parameters for ESP.SYS are
the same as for UART.SYS.  Note that BOTH UART.SYS and ESP.SYS will have to
be loaded if you have a mixture of normal UARTs and ESP ports.  Also note
that once a Hayes ESP port has been used in enhanced mode, it will not work
correctly in compatibility mode until the computer has been powered off,
then on.

The number ("n") in the AltDriver=xxxx$,n fragment has been confusing to
some.  The "n" need NOT match the "n" in COMn.  For example, it one is
defining a single vmodem port at COM3, then AltDriver=vmodem$,1 would be
used in the definition of COM3 in the config file. A more complete example:

;-----------------------;-----------------------------------------
Os2Device
 Name=com3

 AltDriver=vmodem$,1
;-----------------------;-----------------------------------------

The above config file fragment is specifying that COM3 is the first device
(first vmodem port) in the driver vmodem$.
