





                               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\sio2k.sys logfile=c:\sio2k\sio2k.log
     device=c:\sio2k\uart.sys logfile=c:\sio2k\sio2k.log
     device=c:\sio2k\vsio2k.sys logfile=c:\sio2k\vsio2k.log vIrqList(3,4)

     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.

     The CONFIG file:

     The vast majority of users will NOT need a configuration file.  If you
     choose to use a config file, then the SIO2K drivers assume almost
     nothing.  If you use a configuration file, then you must specify just
     about everything.

     First, install as above (with no config file).  The above will allow
     one to access COM1 to COM4 at their standard I/O addresses.

     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 (rebooting 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$.

