Contents:

• I/O And IRQ Conflicts On SatisFAXtion Modems
• The System Locks Up When Casmodem Loads
• ERROR (11) - Faxmodem Not Responding
• ERROR 13 - Modem Does Not Have FAX Capabilities
• Rebuilding Casmodem'S Queue Using Reindex
• Common Causes Of A Corrupted Queue:

The most common reasons customers call Intel Customer Support stem from I/O address or IRQ conflicts. Usually the conflict results from setting the faxmodem to the I/O address and IRQ used by an existing COM port.

This usually indicates an I/O address/IRQ conflict. Look for other boards (network adapters, scanner interfaces, etc...) using the same address/IRQ as the SatisFAXtion faxmodem. Change the address of the faxmodem or the address of the conflicting device.

Also, make sure that CASMODEM and FAXPOP (if you use FAXPOP) are the last TSR (Terminate Stay Resident) programs to load in the AUTOEXEC.BAT. Always load network drivers before loading CASMODEM.

If you use a memory manager on a 386 (or greater) system, be sure to leave at least 128K of EMS memory free for CASMODEM. If the problems continue, run the SatisFAXtion SETUP program and tell CASMODEM not to use EMS memory. Here's how:

1. Change to the SatisFAXtion software directory (usually C:\FAX), type SETUP , then press ENTER.
   
   
2. At the "Options" menu, select "Advanced setup".
   
   
3. Select "Setup technical software options".
   
   
4. Move the highlight to "CASMODEM EMS Usage" then press ENTER.
   
   
5. Select "don't use EMS" then press ENTER to accept.
   
   
6. Press F10 twice then exit SETUP and reboot your computer to put the changes into effect.

The error "Error 11 - Faxmodem not responding" usually indicates one of these conditions:

• There is an IRQ conflict on the COM port the faxmodem is using.
  
  
• There is no faxmodem on the COM port that was selected during the fax software installation.

Make sure the faxmodem's IRQ doesn't conflict with any other device.

Make sure you selected your faxmodem's COM port and IRQ in SETUP.

This error occurs if CASMODEM's autodetect sequence can't get any faxmodem responses from the device that it's talking to. The most common causes of this problem are:

• IRQ conflicts
  
  
• The modem doesn't have fax capabilities
  
  
• Choosing the wrong COM port during installation

You can try using command line parameters (/C1, /C2, /SF) to force CASMODEM to operate with a Class 1, Class 2 or Sendfax. This is known to help with some non-Intel faxmodems. For example, the command CASMODEM /C1 tells CASMODEM to operate with a Class 1 faxmodem.

If you don't know what type of faxmodem you have, follow the directions under "What Type of Faxmodem Do I Have" elsewhere in this document.

If the problem persists, make sure you have selected the COM port for your faxmodem in the fax software configuration program.

CASMODEM maintains an index file called SUPERQUE, which keeps track of all the fax events that occur on your computer. If files in the QUEUE directory become corrupted or are accidentally deleted, the SUPERQUE will no longer correspond to the contents of the QUEUE and your fax log will display an error.

Follow these instructions for correcting a corrupted CASMODEM queue:

1. Exit Windows (if you're running Windows).
   
   
2. Unload FAXPOP, then unload CASMODEM by typing these commands (be sure to include a space before the /U):
   
   FAXPOP /U
   CASMODEM /U
   
   

   NOTE: You must remove CASMODEM from memory before proceeding! If you can't remove CASMODEM because other programs have loaded, edit your AUTOEXEC.BAT file and insert the characters "REM " (don't add the quotes) in front of the CASMODEM and FAXPOP commands. Save the file, reboot your computer, and then you can continue with the next step.

3. Go to the DOS directory containing the queue data files (usually \FAX\QUEUE).
   
   
4. Rebuild the CASMODEM database by typing: REINDEX
   
   
5. Restart (Ctrl-Alt-Del) your computer to reload the fax software.

If REINDEX doesn't solve the problem and you are using FAXability Plus 2.0, see "Correcting a Corrupted CASMGR QUEUE" in document # 4072. If you are using FAXability 1.0, FAXability Plus 1.x, or FAXability Plus/OCR 1.0, follow these directions.

1. Change to QUEUE directory (usually C:\FAX\QUEUE).
   
   
2. Type: DEL *.* (This will completely delete your send and receive logs)
   
   
3. Reboot your computer and load the fax software.

   NOTE: The DEL *.* command will delete all files in the QUEUE directory, so use it only as a last resort.

Common causes of a corrupted QUEUE:

• Another driver or TSR loading after CASMGR or CASMODEM in the AUTOEXEC.BAT file.
  
  
• Trying to "loadhi" CASMGR or CASMODEM in the AUTOEXEC.BAT file.
  
  
• A shortage of available conventional memory.
  
  
• Invoking or exiting Windows while a fax is being sent or received.

Steps You Can Take To Help Prevent a Corrupted QUEUE:

• Always load the CASMGR or CASMODEM driver after all other TSR (Terminate Stay Resident) programs in the AUTOEXEC.BAT, but before FAXPOP or any command that runs a menu program or starts Windows.
  
  
• Do not load CASMGR or CASMODEM high. Instead, make some EMS (Expanded Memory) available for CASMGR or CASMODEM to use. CASMGR and CASMODEM were designed to load most of their code into Expanded memory if Expanded memory is available.
  
  
• Try to keep at least 530Kb of available conventional memory (over 550Kb available is ideal). To find out how much conventional memory is available, type MEM at a DOS prompt (DOS versions 5.0 and 6.0). The value reported as the "Largest executable program size" is the amount of available conventional memory. If you don't have DOS 5.0 or 6.0, type CHKDSK at the DOS prompt instead.

This applies to:

Modems and Fax Boards