Contents:

• Installation Tips
• Three Possible Solutions To Connection Problems
• Microsoft* Mouse Drivers 9.01 And 9.02 And Logitech Mouse 6.23 Conflict With CASMODEM
• Intel® PCMCIA Faxmodem - What Version Of The Card Do I Have?
• INSTALL2 Displays "No Carrier" Error Calling Intel Registration BBS
• Installation Fails When Phoenix 2.22 Software Is Present
• INSTALL2 Dialog Box Says "This Is Not An Intel PCMCIA Faxmodem"
• Intel® PCMCIA Faxmodems 96/96, 14.4 Can't Send Multipage Faxes As Class2
• Intel® Release 3 24/96 Faxmodem Installation Fails... "Not An Intel Card"
• Gateway* 2000 Colorbook Has Problems Sending/Receiving Faxes
• The Card Is Inserted, But INSTALL2 Asks You To Insert It
• Reinstalling Intel PCMCIA Faxmodem Software
• Various Errors Occur When Using Anti-Virus Programs
• "Could Not Open Configuration File" Error
• Card Manager Software Using Invalid IRQ
• No Pop-Up On PC Card Insertions And Removals
• Do Not Insert, Remove, Or Suspend Within Non-Intel Comm Applications
• Cross PC Card Compatibility Issues

This document is designed to help you resolve many common installation problems. The symptoms are defined, along with suggestions for resolving them.

If your Intel® Faxmodem is having trouble connecting to another modem, the problem may be solved by changing the initialization string in your communications software.

Because each software package has its own method for changing the initialization string, please refer to the documentation for your software for help.

These steps are presented in order of effectiveness. Try step 1 and see if it solves the problem. If it persists, try step 2, and then step 3, if necessary.

1. Change the Intel Faxmodem's initialization string to include AT \N0 before dialing the number. This disables the modem's MNP-5 error correction protocol. Some other modems do not have MNP-5 capability and will hang up on an MNP-5 capable modem.
   
   
2. Select a communications speed which both modems can support. The Intel Faxmodem's initialization string should include the command string from the following table.

   Desired Speed (bps)	Command String
   300	N0 S37=2
   1200	N0 S37=5
   2400	N0 S37=6
   4800	N0 S37=7
   7200	N0 S37=8
   9600	N0 S37=9
   12000	N0 S37=10
   14400	N0 S37=11

   Normally, the Intel Faxmodem can auto-baud (detect the maximum speed at which the other modem can transfer data). Some modems do not handle auto-bauding correctly. Disabling this feature corrects the problem.

3. Change the Intel Faxmodem's initialization string to include AT S7=30 before dialing the number. This increases the time the Intel Faxmodem waits for a valid carrier signal from the answering modem to 30 seconds. If 30 seconds isn't long enough for a response, replace 30 with a higher number (40 or 50).

   You can combine command strings in a single initialization string. For instance, the initialization string AT \N0 N0 S37=9 S7=30 disables MNP error correction, manually sets the speed to 9600 bps, and tells the Intel Faxmodem to wait 30 seconds for a response.

Symptom:

MS Mouse driver versions 9.01 and 9.02 and Logitech Mouse driver version 6.23 conflict with CASMODEM, causing problems using the Intel Faxmodem (PCMCIA) 14.4 in DOS. CASMODEM must be in expanded memory (EMS) for this symptom to appear.

NOTE: CASMODEM is required by Intel's FAXability application. If your Intel Faxmodem was shipped with WinFax instead of FAXability, this problem does not occur.

Solution:

Edit AUTOEXEC.BAT so that drivers are loaded in the following order:

CASMODEM
MOUSE
FAXTSR (used only if faxing under DOS)
FAXPOP (used only if faxing under DOS)

Your system may be locking up, making it impossible to edit AUTOEXEC.BAT.

If you have DOS 6.0 or higher:

1. Turn the system's power off, then on again.
2. When the message Starting MS-DOS appears on the screen, press [F5] to bypass CONFIG.SYS and AUTOEXEC.BAT.
3. At the C:\ prompt, type:

EDIT C:\AUTOEXEC.BAT

If you have a previous version of DOS, you need a startup diskette to bypass AUTOEXEC.BAT.

1. Insert the startup diskette and power up the system.
2. At the C:\ prompt, type:

C:\DOS\EDIT C:\AUTOEXEC.BAT

Another possible solution is to use MS Mouse driver version 9.00 or earlier.

There are two different releases of the Intel Faxmodem for PCMCIA. The faxmodem cards in each release have the same capabilities, but they use different versions of the AT Command Set. Here's how to determine whether you're using Release 2 or Release 3 of the Intel ®Card Manager Software.

The Release 2 package:
Has a plastic "bubble pack" for the faxmodem card Is shipped with Intel FAXability and HyperAccess Lite software

The Release 3 package:
Has a flat front with a picture of the faxmodem card Is shipped with WinFax Lite and HyperAccess Lite software OR Delrina 4-in-1

• The card in the Release 2 package is compatible with Release 2 AT commands ONLY.
• The card in the Release 3 package is compatible with Release 3 AT commands ONLY.
• The Cellular Faxmodem is compatible with Cellular Faxmodem AT commands ONLY.
• The International PCMCIA Faxmodem is compatible with International Faxmodem AT commands ONLY.

NOTE: The AT Command Set is built into the faxmodem card, and can not be changed with software. The Intel Card Manager software or other PCMCIA drivers on your system have no effect on the AT command set that your card uses.

Symptom:

An attempt to register the Intel PCMCIA Faxmodem fails, The modem returns a "NO CARRIER" error code, even if the user can hear the Intel Registration BBS answer the call.

CAUSE: The init string that INSTALL2 sends to the calling modem before it dials the registration BBS includes S7=10. In originate mode, this tells the Intel PCMCIA Faxmodem to wait 10 seconds for an answer tone. If the BBS modem can not produce this tone within 10 seconds after the timer starts, the PCMCIA Faxmodem hangs up.

Solution:

Download the self-extracting archive file REGFX.EXE from the Intel's on-line services. Run REGFX to extract the REGFIX.EXE program, which updates INSTALL2.EXE to wait up to 20 seconds for an answer tone.

To use REGFIX, it must be in the same directory as the rest of the Intel Card Manager software (usually the C:\CARDMGR directory).

1. Type at the DOS prompt:
   COPY REGFX.EXE C:\CARDMGR
   CD \CARDMGR
   REGFX
   REGFIX
   
   
2. Continue with INSTALL2.

Symptom:

Intel's INSTALL program fails on systems where Phoenix PCMCIA software version 2.22 has been installed. If you decide to use only the Phoenix PCMCIA drivers, the card does not work with any applications, or operates erratically.

APPEARS ON PCMCIA FAXMODEMS: 14.4/14.4, 96/96. Cellular, International

CAUSE: The Phoenix software is configuring the card so that it generates interrupts wrongly.

Solution:

Edit your CONFIG.SYS file, find the line that includes PCMSCD.EXE and add "/LEVEL" to the end of that line. It should look something like this:

DEVICE=C:\PCMPLUS\PCMSCD.EXE /LEVEL

If there are other parameters on this line, you can leave them there. Save CONFIG.SYS and reboot before installing the Intel Faxmodem.

Symptom:

During installation, the testing dialog box displays the message, "This is not an Intel PCMCIA Faxmodem"?

CAUSE 1: Another card installer in the system could be interfering with INSTALL2.

Solution 1:

Edit CONFIG.SYS to temporarily remark out any other installer. Possible names are:

CAUSE 2: A memory conflict may prevent INSTALL2 from reading the card ID.

Solution 2:

1. Boot the system clean, without using AUTOEXEC.BAT or CONFIG.SYS.
   1. From DOS 5, change the names of the AUTOEXEC.BAT and CONFIG.SYS files and then reboot the system. (After diagnosing the problem, don't forget to change the names back before rebooting again.)
   2. From DOS 6, reboot the system and hold down [F5] so that AUTOEXEC.BAT and CONFIG.SYS are not read.
   
   
   
2. Type CD C:\CARDMGR
   
   
3. Type RTINIT /VI /DEMO
   
   
4. A map of the Upper Memory Area is displayed showing which UMAs are being used and which are available. Note the addresses of the available UMAs.

   Card Manager Software requires three 4K blocks of unmapped UMA to work properly. Each UMA must contain at least 4K of contiguous memory. It does not matter whether the three UMAs are adjacent. If an upper memory conflict occurs, its most likely cause is that the UMA used by the Card Manager software is also being used by something else, such as an EMS provider, RAM, or ROM.

5. Edit the CONFIG.SYS file, adding /MEM=(free UMA range) to the RTINIT.EXE command line in CONFIG.SYS and reboot the system. It may be necessary to exclude UMA ranges from Card Services with the /XMEM={invalid memory range} parameter on the RTINIT.EXE command line in CONFIG.SYS.
   
   
6. For more specific information about your particular system, check the System Compatibility information in document 3421.

Symptom:

An Intel Faxmodem for PCMCIA 96/96 or 14.4/14.4 can not send multiple-page faxes under WinFax (or another non-CAS fax application). Outgoing faxes fail after one or more pages are sent.

CAUSE: The faxmodem and application are configured for CLASS2 operation. CLASS1 is the preferred configuration, because of variations in the implementation of the CLASS2 specification.

Solution:

Reconfigure the Intel Faxmodem for CLASS1 operation.

Symptom:

At the beginning of INSTALL, when the Release 3 24/96 faxmodem is inserted, an error "This is not an Intel Faxmodem Card" appears.

CAUSE: The file FAXCARDS.DAT, which is on the installation disk, contains a coding error.

Solution:

Edit the FAXCARDS.DAT file on the installation disk as follows:

1. Go to the section called [Card 4].
   
   
2. Within the [Card 4] section, edit the line for CardKey to read: CardKey=IntelPCMCIA Faxmodem 24/96MBFM6811
   Note: The error is that 6810 appears at the end of this line; it should be 6811.
   
   
3. Within the [Card 4] section, edit the line for ATIResponse to read: ATIResponse=iNTEL Faxmodem 24/96
   Note: The error is the capitalization of INTEL. INTEL is correct; Intel is not correct.

Symptom:

Gateway* 2000 ColorBooks may lose connections and have problems sending faxes reliably. Symptom details vary.

CAUSE: The system's power save feature is turned on. The power saver slows down the system's processor, and you usually need it to run at full speed to send or receive faxes reliably.

Solution:

You can turn the Gateway* 2000 ColorBook's power saver off and on at any time without having to reboot the system. Because your battery may drain more quickly with the power saver off, Intel recommends turning the power saver on when you are not using the Faxmodem for PCMCIA.

1. Press [FN] and [ESC] together at any time to enter the BIOS Setup.
   
   
2. Select Power Management.
   
   
3. Select Controls.
   
   
4. Move the cursor to High Speed Com Port and press [Enter] to select it (a check mark means the power saver is off.)
   
   
5. Press [ESC] to leave BIOS Setup and then press [Enter] to save the change.

The change takes effect immediately.

Symptom:

During the installation process, the program asks you to insert the card. It tells you to eject the card if it is already in, and to re-insert the card. When you do, nothing happens. Even if you eject and re-insert the card numerous times, the installation program still continues, and tells you to insert the card.

CAUSE 1: The PCMCIA sockets may not be enabled on the computer. If the socket is turned off, our installation program cannot see the card insertion, and applications will never be able to use the card.

Solution 1 :

Enable the PCMCIA sockets.

• For most systems (for example, the Canon NoteJet 486, which ships with the socket turned off), the solution is to get into the BIOS setup for the computer, and to enable the PCMCIA socket. Check the documentation for your system to find out how to get into the BIOS setup, or look in this service's "Intel PCMCIA Faxmodems - Detailed System Compatibility" document for your system. Sometimes this feature is located in the "advanced settings" or in the "power management" area of the BIOS settings. After you have changed the settings, save the changes and restart your system.
  
  
• In other systems (for example, the Compaq Concerto), you can turn the PCMCIA socket off and on with the computer's setup utility under Windows. After changing the settings, save the changes and restart your system.

CAUSE 2: The installation program is looking at the wrong interrupt request line (IRQ) for card insertion/removal events.

SOLUTION 2: Run the RTINIT program to see which interrupt the installation program is trying to use:

1. At the DOS prompt, type CD \CARDMGR.
   
   
2. Then type RTINIT /DEMO /VI.
   
   
3. The Card Status Change IRQ is reported in the upper left corner of the display. This is the highest available IRQ. Write it down and exit RTINIT.
   
   
4. Edit the CONFIG.SYS file. Look for the four device driver lines that have been added by the installation routine. One of these lines will look like this:
   DEVICE=C:\CARDMGR\RTINIT.EXE /IO=260-26F

   (The numbers just after /IO= may be different on your system. If they are, don't change them.)

   At the end of this line, add the /XIRQ={wrong IRQ number} parameter. If the CSC IRQ number was 15, the line will now look like this:
   DEVICE=C:\CARDMGR\RTINIT.EXE /IO=260-26F /XIRQ=15
   
   

5. Save the changes to the CONFIG.SYS file.
   
   
6. Turn the system off, then back on again (a warm boot does not reset the CSC IRQ).
   
   
7. At the DOS prompt, type CD \CARDMGR.
   
   
8. Then type INSTALL2.

   The installation program should use the correct IRQ this time.

9. If it does not, repeat steps 1-7, taking care to add both wrong IRQs to the line in CONFIG.SYS. Separate the wrong IRQs with a comma, like this:
   DEVICE=C:\CARDMGR\RTINIT.EXE /IO=260-26F /XIRQ=10,15

EXPLANATION 2: The pop-up may fail to appear if Card Manager software is using the wrong IRQ to monitor the PCMCIA Socket Status. RTINIT.EXE assigns the CSC IRQ (Card Status Change IRQ, the Interrupt Request line used to notify the system when a PC Card is inserted or removed) to Card Manager software, and RTINIT.EXE always uses the highest available IRQ for the CSC IRQ. Some system manufacturers do not route all the IRQs to the PCMCIA socket controller, so sometimes the wrong IRQ is chosen for the CSC IRQ. Adding the /XIRQ={wrong IRQ} parameter to RTINIT tells it to exclude the wrong IRQ from the list of available IRQs.

If an error occurred while you installed the Intel PCMCIA Faxmodem Software, and you want to re-install it now, you have to remove two files before restarting the installation.

EXCAVOYA.INI

The EXCAVOYA.INI file is a temporary file created in the Windows directory and deleted when the software is successfully installed.

1. From the DOS prompt, type:
   CD \WINDOWS

   (If your Windows files are in another directory, use that directory name.)

2. Type:
   DEL EXCAVOYA.INI

   If EXCAVOYA.INI is not present, do not go to the next step. Instead, follow the procedure for "Removing Intel PCMCIA Faxmodem Software".

3. Open and edit WIN.INI. From the [Intel Card Manager] section, delete the lines,
   [Intel Card Manager]
   InstallPath=CD \CARDMGR

Save WIN.INI and exit the editor.

CARDMGR.EXE

The CARDMGR.EXE file is located in the Intel Card Manager Software directory.

1. From the DOS prompt, type:
   CD \CARDMGR
   
   
2. Type:
   DEL CARDMGR.EXE

You should now be able to re-install the Intel Card Manager software without trouble.

Symptom:

You are getting Card Services errors or other problems when the computer boots up or when you insert/remove the Intel PCMCIA Faxmodem.

Possible errors include:

• "Card Services Allocation Error"
• "Error: configuration file not found"
• "Error: Could Not Open Configuration File"
• "Error using Card Services. Please make sure all software is correctly installed." (INSTALL 2 error)
• Card insertions are not recognized.

Solution 1:

Read your CONFIG.SYS file and look for the Norton Anti-Virus program NAV&.SYS. If NAV&.SYS appears before the Intel Card Manager Software, it will interfere with Card Services. There are several ways to solve this problem by editing CONFIG.SYS:

Solution 2:

If you are using any other resident antivirus program, remark it out of your AUTOEXEC.BAT or CONFIG.SYS file. You can still protect your system adequately by running the antivirus program manually about once a week.

CCMGR.EXE cannot find the CCMGR.CFG file. To correct this problem:

1. Go to the DOS prompt. If you are running Windows, exit Windows completely.
   
   
2. Change directories to where the Card Manager software is stored.
   
3. Type DIR INSTALL* and look for INSTALL2.EXE.
   
   
4. If INSTALL2.EXE is in the directory, type INSTALL2. Otherwise, re-install the Intel Card Manager software.
   
   
5. During installation, insert the Intel PCMCIA Faxmodem when instructed.

• If the insertion is recognized, continue with the INSTALL2 program and register your Intel PCMCIA Faxmodem. You should have no further problems.
• If the insertion is not recognized, the Intel Card Manager software has not been correctly configured for your system.

NOTE: This error has also been seen when Norton Anti-Virus was called by the first line in CONFIG.SYS. Editing CONFIG.SYS fixed the problem.

If you are having trouble installing your Intel PCMCIA Faxmodem, one likely cause is that the Intel Card Manager software is using an invalid IRQ (Interrupt Request line).

NOTE: The following procedure requires you to turn the system's power COMPLETELY off and then on again. Some systems (Toshiba and Zenith, for example), may have the power switch configured to suspend and resume the system instead of simply turning the power off and on. To make the following procedure work, first run the system's BIOS Setup utility and reconfigure the power switch to turn the power on and off. You can change it back, if you wish, after assigning a valid IRQ to the faxmodem.

To find and assign a valid IRQ to the faxmodem:

1. Go to the DOS prompt. If you are running Windows, exit Windows completely.
   
   
2. Change directories to where the Card Manager software is stored.
   
   
3. Run RTINIT /DEMO /VI and see which IRQ is designated as the CSC IRQ. (It appears in the upper left corner of the RTINIT display.) The system is unsuccessfully attempting to use this IRQ for the faxmodem. Remember this IRQ.
   
   
4. Edit your CONFIG.SYS file, appending the parameter

   /XIRQ=[the CSC IRQ]

   to the line DEVICE=C:\CARDMGR\RTINIT.EXE [etc.]
   
   
5. Turn the system COMPLETELY off and then back on again.
   
   
6. Run INSTALL2 again. If it fails again, repeat steps 3-6 until INSTALL2 completes successfully.

NOTE: If you repeat steps 3-6, a different CSC IRQ will appear in the RTINIT display. In step 4, append this IRQ to the /XIRQ parameter so that it reads:

Do not forget the comma between IRQ values.

There are three possible causes why the Intel Card Manager software will not display a pop-up when you insert or remove a PCMCIA Card:

• The DOS pop-up is disabled from within DOS (but is still displayed from Windows) when the CCMGR.EXE command line in AUTOEXEC.BAT has the parameter /D=0 or /DISP=0. Remove this parameter to get the pop-up in DOS.
  
  
• There may be an Upper Memory Area (UMA) conflict. The Intel Card Manager software requires a minimum of 12K of UMA that has not been mapped by RAM, ROM, or an EMS provider. The 12K can consist of three contiguous areas of memory, each containing at least 4K. These areas do not have to be adjacent. If there is no free UMA, the Intel Card Manager software cannot read the PC Card's Card Information String and cannot install the PC Card. Fix this problem by making sure there is at least 12K of free UMA in your system.
  
  
• The PC Card is not supported by the Intel Card Manager software. The Intel Card Manager software only recognizes those PC Cards whose manufacturer's ID code are contained in the CCMGR.CFG file. When shipped from the factory, the Intel Card Manager software will only recognize the Intel PCMCIA Faxmodem that was packaged with the software.

The Intel PCMCIA Faxmodem must be installed before you start any non-Intel supplied communications application. These non-Card Manager aware applications are not designed to handle removable communications hardware. They require the hardware to be present and configured when they are executed and can cause problems if the hardware is not present. It is always a good idea to exit any non-Card Manager aware application before the system goes into suspend mode.

General Procedure for Installing Other Manufacturers' PC Cards: Load the other manufacturer's PC Card drivers and configure the PC Card as described in that PC Card's documentation. Then install the Intel Card Manager software. If the PC Cards still don't work together, try loading the Intel Card Manager software before loading the other manufacturer's PC Card drivers.

Intel has developed a utility called CARDLIST.EXE which tests a PC Card to see if the Intel Card Manager software can install it. If the PC Card passes the test, you can then add that PC Card to the list of PC Cards (maximum of 8) that the Intel Card Manager software will install. Then run the PC Card's device drivers to see if they can recognize the PC Card.

CARDLIST.EXE is available on Intel's on-line services in a self-extracting archive called REL3SW.EXE.

Intel cannot guarantee compatibility with other manufacturers' PC Cards. Many PC Cards cannot tell the Intel Card Manager software what their configuration requirements are, so they cannot be installed. Other PC Cards have device drivers that are incompatible with the Intel Card Manager software, or they require exclusive access to the PCMCIA socket.

This applies to:

Modems and Fax Boards