   |=========================================================================|
   |                                                                         |
   |              How to Fix the Most Common Modem Problems                  |
   |                                                                         |
   |=========================================================================|


    MY SOFTWARE DOESN'T LIST THE INTEL MODEM

        If your communications program doesn't list your Intel modem in the set
        up screen, try selecting a Hayes compatible configuration.  If the
        problems persits, change the "Initialization String" to match your
        modem type:

            Intel Modem           Initialization String
            -----------------     ----------------------
            SatisFAXtion          AT&F\N0\Q0\J1\V0
            14.4 EX/9600EX        AT&F\N0\Q0\J1\V0"H0-J0
            All 2400 Baud MNP     AT&F\N0\Q0\J1\V0


    14.4EX/9600EX CONNECTS ONLY AT 2400 BPS

        Intel High Speed modems (such as the 14.4EX and 9600EX) connect at 9600
        bps (bits per second) only to modems which support the V.32 standard.
        Many high-speed modems (such as the Hayes V Series or US Robotics HST)
        support industry standards for speeds up to 2400 bps, but use
        proprietary standards at 9600.  Without V.32 support on these modems,
        Intel High Speed modems connect to them at no greater than 2400 bps.

        Other modems (such as the Hayes Ultra 9600 or US Robotics HST Dual
        Standard) support V.32 in addition to the proprietary standard.  With
        V.32 enabled on these modems, Intel High Speed modems can connect to
        them at 9600 bps.


    USING COM3/COM4 UNDER WINDOWS 3.0

        If you have problems using the your modem on COM3 or COM4 under Windows
        3.0, exit Windows and use Intel's TESTCOM.EXE program (which comes with
        all Intel modems) to test your modem.  TESTCOM performs several
        diagnostic tests on the modem and helps you verify the phone line
        connection.  SatisFAXtion board users who need a copy of TESTCOM can
        order document 0018 from Intel's FaxBACK system.  Modem users can
        download TESTCOM from the Fax/Modem section of Intel's BBS.

        Once you know the modem works on COM3 or COM4 outside of Windows, you
        can test the modem with your Windows program.  If you run Windows in
        Enhanced mode, you need edit the Windows SYS.INI file.  Under the
        [386enh] symbol, add these lines:

        COM1BASE=3F8h
        COM2BASE=2F8h
        COM3BASE=3E8h
        COM4BASE=2E8h

        Editing your INI files is risky business.  Carefully read your Windows
        documentation or call Microsoft Microsoft Technical Support if you
        questions or problems.

   ===========================================================================

   February 24, 1992         Intel FaxBACK # 4364                       Page 1
   |=========================================================================|
   |                                                                         |
   |              How to Fix the Most Common Modem Problems                  |
   |                                                                         |
   |================================ (continued) ============================|

        Microsoft Tech Support:  206-454-2030


    ERRATIC RESPONSE TO AT COMMANDS

        Erratic response to AT commands can be attributed to two things: IRQ
        Conflicts and/or COM port overlaps.  You can use the  TESTCOM.EXE
        program can verify modem operation and detect conflicts.

        First ensure that no other devices are using the same IRQ as the modem.
        Modems use IRQs to signal the computer that data has been received or
        sent. For an internal modem, make sure that the COM port it's set to
        does not conflict with a COM port already in the system (whether used
        or not). When in doubt, try another COM port setting.

            Port   I/O   IRQ
            ----   ---   ---
            COM1   3E8    4
            COM2   2E8    3
            COM3   3F8    4
            COM4   2F8    3

        For instance, consider a situation where you add an internal modem to a
        system which has COM1 and COM2 built in. There's a mouse on COM1 and
        nothing on COM2.  You must either:

           Disable the built-in COM2 and address the modem as COM2 (prefered)
           Leave the mouse on COM1 and address the modem as COM4
           Move the mouse to COM2 and address the modem as COM3


    MODEM DIALS BUT DOES NOT CONNECT

        Modem Dials but Does Not Connnect
        This problem commonly results when your modem is set to use MNP but the
        remote modem doesn't support MNP.  It can also happen if the value in
        your modem's  S7 register is too low.  The value in the S7 register
        tells the modem how long  to wait for a carrier signal after dialing.

        To find out if MNP is causing the problem, enter the command:  AT\N0&W.
        If the problem persists, make your modem act like a Hayes modem by
        entering the command for your modem:

            Intel Modem           Command
            -----------------     -----------------------
            SatisFAXtion          AT&F\N0\Q0\J1\V0&W
            14.4EX/9600EX         AT&f\N0\Q0\J1\V0"H-J0&W
            All 2400 Baud MNP     AT&F\N0\Q0\J1\V0&W

        To find out if the value in the S7 register is causing the problem,
        increace the value from its default of 30 seconds. Run the TESTCOM
        program, select the "Terminal emulation mode", then type   ATS7=60&W
        and press ENTER. If this doesn't help, try a higher value (the maximum
        is 255).

   ===========================================================================

   February 24, 1992         Intel FaxBACK # 4364                       Page 2
   |=========================================================================|
   |                                                                         |
   |              How to Fix the Most Common Modem Problems                  |
   |                                                                         |
   |================================ (continued) ============================|


        Here are the common symptoms of an MNP problem:

        Your modem dials, the remote modem answers, the modem tones begin, then
        either:
        a.  your modem hangs up, or
        b.  your modem does nothing while the tones continue.

        If the user still can't connect after disabling MNP, try calling the
        system  yourself. If they're using a SatisFAXtion modem, make sure they
        have the latest software. If not, they can order 0011 from Faxback.


    MODEM WON'T ANSWER THE PHONE

        There are two reasons why the modem won't answer:

        1.  The modem isn't in Auto-Answer mode.
        2.  The modem doesn't see the DTR signal from the computer.

        The command ATS0 controls Auto-Answer mode.  An external modem turns on
        "AA" light on when Auto-Answer mode is enabled.

            ATS0=0    disables Auto-Answer
            ATS0=1    answer after 1 ring

        The command AT&D controls how the modem responds to the computer's DTR
        signal.  An external modem turns on the "TR" light when it sees or is
        set to ignore the DTR signal.  If the "TR" light isn't on, the modem
        won't answer whether Auto-Answer is enabled or not.

            AT&D0     Modem ignores DTR signal
            AT&D2     Modem swtches from data to command mode, hangs up
                      and disables Auto-Answer mode when DTR switches
                      from ON to OFF.

        Use AT&D0 if you serial port doesn't support the DTR signal or if your
        modem cable doesn't connect to it. Otherwise, use AT&D2. DTR is on pin
              20 of a 25-pin connector and on pin 4 of a 9-pin connector.













   ===========================================================================

   February 24, 1992         Intel FaxBACK # 4364                       Page 3