OS/2 Shareware BBS: 36 Tips/36-Tips.zip/WNFXP.FAX

Text File | 1994-11-30 | 6KB | 122 lines

Running WINFAXPRO V3.0 in OS/2 For Wind.         2/10/94

TITLE: 940117 RUNNING WINFAX PRO V3.0 UNDER OS/2 2.1 IS UNSUPPORTED
              EXCEPT FOR SERVICE RELEASE AVAILABLE FROM DELRINA, AND
              WITH TECHNICAL NOTES ON 16550 UARTS AND SIO DRIVERS

DESCRIPTION OF SYMPTOMS:
    1.  Delrina at [phone] doesn't officially support running
        WinFax Pro v3.0 under OS/2 2.1 but does offer a service release.
        See CHGSK PDDB for information on downloading from Compuserve.
    2.  Since Windows exists in other than the Microsoft version,
        WinFax Pro may not run with OS/2 for Windows (Ferengi).

    OS/2 2.1 is a preemptive multitasking operating system that only
    allows Windows or DOS applications to access the serial ports 1000
    times per second. This isn't frequent enough to allow reliable data
    transfer.
    There is a special UART* that has the buffering capability. OS/2
    2.1's serial port driver will use the buffering capability of this
    UART to increase the reliability of data transfers running at 9600
    baud or higher. The type of UART is known as 16550A.
    In order to send or receive data at 9600 baud reliably under OS/2,
    the serial port that the fax modem is connected to must have a
    16550A** UART.
    Internal modems have their UARTs built onto the modem card. Many of
    the high speed internal modems are equipped with 16550A UARTs.
    External modems use an existing serial port in the computer. Most of
    these ports use 16450 UARTs.
    If either the internal modem or the computer's serial port doesn't
    allow for the upgrade of the existing UART to a 16550A, then SIO
    drivers by Ray Gwinn may help.
    If the modem or serial port isn't equipped with a 16550A UART, the
    SIO drivers, which are shareware, are on OS/2 supporting BBS's and
    on Compuserve in the OS/2 file section.
    Version 1.02 was used in testing WinFax.
    3.  When these drivers are installed, some of the WIN-OS/2 settings
        will be removed and replaced with other settings.
    4.  SIO drivers, which are third party drivers, aren't endorsed
        by Delrina and for OS/2 may require changes to the config.sys in
        order to disable the use of the original COM.SYS and VCOM.SYS.
    5.  The SIO drivers enhance the performance of DOS and Windows
        applications running under OS/2 2.1 by doing two things.
        a.  The drivers emulate a 16550 UART through software if one
            isn't installed.
        b.  The drivers allow DOS and Windows applications to make
            better use of the 16550A UART if one is installed. With a
            16550A UART and WIN-OS/2 settings below, the drivers
            probably need not be used for WinFax. However, if
            difficulties are still being experienced after changing the
            settings, the SIO drivers may help.
    *   A UART is essentially the heart of a serial port. It controls
        the transmission and reception of data to and from the computer.
        The 16550A UART can hold up to 16 bytes of information between
        port scancs whereas a conventional UART cannot hold more than
        one byte. The original 16550 had a bug in its handling of its
        16 byte buffer. The 16550A corrected this.
    **  The 16550AFN and 16550AF UARTS are revised versions of the
        16550A UART, and they will work with the settings below.


SUMMARY OF RESOLUTION:
    1.  For Class 1 or 2 modems, change WIN-OS/2 settings as recommended
        below and edit system.ini under .386Enh. section as indicated.
    2.  Note procedures for setting the baud rate (also note CLDXZ
        PDDB).
    3.  Note procedures for using SIO drivers if the need arises.
    4.  WinFax Pro should run in full screen session and be left running
        in the foreground.

DETAILS OF RESOLUTION:
    1.  WIN-OS/2 Settings:
            COM_HOLD            to ON
            HW_TIMER            to ON
            INT_DURING_IO       to ON
            IDLE_SENSITIVITY    to 100
            IDLE_SECONDS        to 60
        Note:   IDLE_SENSITIVITY and IDLE_SECONDS may vary between
                systems, and in many cases can be left to default
                values.
    2.  a.  For 14400 BPS fax modems, edit SYSTEM.INI in the .386Enh.
            section as follows:
                COM?FIFO=0
            where ? is the com number being used.
        b.  If running in an Enhanced Mode Windows session under OS/2
            2.1, edit SYSTEM.INI in the .386Enh. section as follows:
                COM?BUFFER=4096
                COMBOOSTTIME=30
            where ? is the COM number being used. Also refer to CLDXZ
            PDDB.
    3.  With a Class 1 fax modem and a version of WinFax dated April
        1993 or LATER, WinFax allows for speed restrictions on both
        transmissions and receptions. For send sending or receiving
        faxes at 9600 baud or above, edit the .General. section of the
        WINFAX.INI as follows:
        a.  The example is for 7200 bps transmitting and 4800 bps
            receiving:
            MaxTXspeed=7200
            MaxRXspeed=4800
        b.  Valid entries fro MaxTXspeed are 14400, 12000, 9600, 7200
            and 4800 bps.
        c.  Valid variables for MaxRXSpeed are 14400, 9600, 4800 baud.
        Note:   (1) To find the version date of WinFax, select Help,
                    then About from the main WinFax screen.
                (2) There is an update if the WinFax version is January
                    1993 or EARLIER.
    4.  For SIO drivers, REM lines in config.sys that refer to COM.SYS
        and VCOM.SYS.
        Note:   Original serial port drivers should be REMed because the
                SIO drivers aren't an exact replaement for the serial
                port drivers shipped with OS/2 2.1.
    5.  WinFax may not install properly if the SIO drivers are running.
        If this is the case REM the SIO drivers to enable the original
        serial port drivers. Once installation is completed, REM COM.SYS
        and VCOM.SYS, then unREM SIO drivers.






12/31/99