


1-How can I determine that SIO2K has correctly determined my uart type and
the IRQ it is using.

     In the sio2k distribution zip, there is a program named logger.exe. 
     This program can hook into sio2k.sys and provide an enormous amount of
     information.  However, some information is only available once, when
     the port (uart) is first touched by an application.  For information
     like uart type, fifo depth, and crystal multiplier, you must have
     logger running before the port is touched the first time.  Here is
     how.  Reboot your computer, go to an OS/2 session and execute (for
     info on com1) x:\path\LOGGER COM1.  Then go to another OS/2 session
     and execute MODE COM1.  You can then examine the information produced
     by logger.  Note that LOGGER.EXE has an optional parameter of a disk
     file name.  If a disk file name is given, the information produced by
     logger is written to that file, as well as being displayed.

2-DTR/DSR flow control does not work, I am using a 16650.  

     The 16650 and similar devices do flow control on chip (in hardware) 
     Unfortunately DTR/DSR flow control is not supported.  One can use a
     special cable to achieve the desired flow control.  Simply move the
     wires for the DTR and DSR signals to the RTS and CTS signals at the PC
     end of the cable.  Then specify RTS/CTS flow control.

3-Why is the IRQ not show in the Hardware (Resource) Manager screen(s).

     During boot time, the SIO2K driver set does not always know the IRQ
     that the serial port is going to use. This is especially true with
     legacy ISA serial ports.  However, the first time the port is accessed
     by a program, the IRQ is determined and is reported to the Hardware
     Manager.  So, if you are not seeing the IRQ for COM1 when rmview is
     executed, then do a MODE COM1, and then execute rmview.  The IRQ
     should then show up on the rmview report(s).

4-Why is a message about failing an integrity check being displayed.

     Assuming the drivers have not been otherwise altered, you are probably
     running a disk compression utility.  In order to use the SIO2K
     drivers, they must NOT be altered in any way, which includes
     compression.

5-Why is the FIFO depth shown as 1 for a Hayes ESP when the port is used in
compatibility (16550) mode via uart.sys.

     The 16550 emulation by the Hayes ESP seems to have a few problems. The
     compatibility mode should be avoided if possible, when ESP.SYS is
     loaded.  One of these problems causes the probed FIFO depth to show up
     incorrectly.  However, once uart.sys has detected a FIFOed device, the
     FIFO size will only be increased, not decreased.  Even though the
     probed depth is shown as 1, the 16 byte FIFOs (for a 16550) are still
     used.

6-I am having problems using a Hayes ESP card in compatibility mode.

     Once ANY ESP port has been used in enhanced mode (touched by ESP.SYS),
     power much be cycled before ANY ESP port will again work in
     compatibility mode again.

     If your are not using ESP.SYS, try forcing a 16450 uart for the port
     in the uart.sys section of sio2k.cfg.  If this still fails, you should
     use enhanced mode only, via ESP.SYS.


7-One of my applications complains that the buffers are not large enough.

     Why some people, including some very good programmers, insist on
     believing in the need for large buffers is beyond this writers
     comprehension.  The buffers in the SIO2K drivers are sufficiently
     large enough (and then some) for any application to work well (at top
     speed).

8-I am getting an "In Use" or "Not Ready" error when I try to use one of my
serial ports, even though that port is not being used by another program.

     The serial port may not be in use, but the IRQ the port uses probably
     is in use.  See FAQ number 1 for a description of how to use
     LOGGER.EXE.  Information produced by logger should tell you exactly
     why you are getting the error.

9-Why do the drivers skip assigning hardware to COM2 (or COM3/COM4), then
assigns other hardware to ports after that?

     You probably have PCMCIA.SYS installed.  If the SIO drivers detect
     that PCMCIA.SYS is installed, then a COMn (COM2 through COM4) opening
     must be available for a possible PCMCIA modem being inserted.

10-Why am I getting errors when I use higher bit rates?

     There are several possible reasons:

     1 - The most common reason is a flow control problem.  You should
     always try to use RTS/CTS flow control. Xon/Xoff flow control may
     react too slowly at higher bit rates.  Refer to your application
     manual (or their support) to determine how to set flow control.

     2 - The second most common reason is possibly your serial cable.  If
     you are using a serial cable at high speeds, it must be a good quality
     shielded cable.  Also, the cable should be as short as possible.  The
     longer the cable, the less the bit rate it will be able to pass.

     3 - Last, it could be that your computer is simply not fast enough to
     handle the higher bit rates.

11-Why does my PCMCIA modem not work?

     Try removing, and reinserting the modem card after your system has
     booted.  The PCMCIA drivers seem to only report the existence of a PC
     card modem to the serial drivers when it (the modem) is inserted. If
     the modem is already inserted when the system is booted, the modems
     existence is not reported to the serial drivers.  This may work
     differently on some systems.

12-Does Sio2k support WinModems?

     Currently (10-18-00) no.  I will look into WinModem support as soon as
     time permits.  Watch the history.txt file for information.
