Once you've found the VCD line, change it to: DEVICE=CAS31VCD.386

The FAXability INSTALL program expects to find the command "DEVICE=*vcd" (as it appears in the Windows for Workgroups version 3.11 SYSTEM.INI file), but in Windows for Workgroups version 3.0x, the command was changed to "DEVICE=vcd.386". Since INSTALL can't find the line, it can't automatically modify it for you.

SatisFAXtion boards using CASMGR (Classic, SatisFAXtion Modem/350 and upgraded SatisFAXtion Classic) work under Windows for Workgroups 3.11 as long as you don't enable the "32-bit File Access" feature. Here is how to make sure the 32-bit File Access feature is not enabled:

1. Choose the "Main" application group in the Program Manager Window.
   
   
2. Double-click on the "Control Panel" icon in the Main window.
   
   
3. Double click on the "386 Enhanced" icon in the Control Panel Window.
   
   
4. Click on the "Virtual Memory" button.
   
   
5. Click on the "Change>>" button.
   
   
6. Find the "Use 32-bit File Access" check box and make sure it does not contain an "x".

WORKAROUND:

If you need 32-bit File Access, there is a work-around solution available. However, the work-around solution causes these side effects:

• You can't send or receive faxes using a DOS application under Windows.
  
  
• You can't receive a fax in Windows while a DOS session is running.
  
  
• Your computer may reboot when you exit Windows.

Follow these instructions to implement the work-around solution. Use the DOS EDIT program or the Windows Notepad program to make these changes.

1. Open your AUTOEXEC.BAT file.
2. Remove or disable the CASMGR command in your AUTOEXEC.BAT file.
3. Save the AUTOEXEC.BAT file.
4. Open or create a file called WINSTART.BAT in the Windows directory.
5. Add the CASMGR command line to the WINSTART.BAT file.
6. Save the WINSTART.BAT file then restart Windows.

STATUS: This is a problem with Windows for Workgroups 3.11 (See Microsoft fax document Q105502). There is no way to change CASMGR to solve this problem without a change to Windows for Workgroups.

NOTE : You can get the Microsoft fax document by calling (206) 635-3105 (number valid as of 1/24/94) and requesting fax document Q105502 to be faxed to you.

When you install FAXability Plus/OCR, INSTALL adds ";C:\FAXABLTY\CAL\BIN" to the PATH statement in your AUTOEXEC.BAT file (assuming you installed FAXability in the C:\FAXABLTY directory). This may make the PATH command longer than the DOS limit of 127 characters. If so, you'll have to delete some directories from your path or rename directories to make the names shorter.

The error "Unable to read task control record" can occur when using FAXability Plus/OCR if you don't have the path "javascript:void(null);" in the PATH statement in your AUTOEXEC.BAT file.

This error can also result from a corrupted file in the \QUEUE directory.

When using FAXability with Class 1 faxmodems make sure the faxmodem's IRQ doesn't conflict with another device in the system. CAS faxmodems (such as the SatisFAXtion faxmodems) do not use a COM port for faxing, so you won't have this problem with those boards.

While some DOS-based programs will operate properly when the faxmodem IRQ conflicts with another IRQ, FAXability won't work. Here's the best way to prevent IRQ conflicts:

1. Temporarily remove your faxmodem (if you already installed it).
   
   
2. Run a diagnostic program that can tell you which IRQs are in use.
   
   Examples of diagnostic programs are:
   
   TESTCOM /S (Included with Intel SatisFAXtion faxmodems)
   COMSTAT /S (Included with intel Faxmodems)
   CASMODEM /D (Included with Intel FAXability software)
   MFT (Included with QEMM 386)
   MSD (Included with Windows 3.1)
   SI (Included in Norton's Utilities)
   
   
3. Configure your faxmodem to use an IRQ that no other device is using. You may have to reconfigure a network adapter, scanner interface, or other such board so the faxmodem can use a unique IRQ.

NOTE: Many computers have two COM ports (or serial ports), but most users don't use both COM ports. If you're not using one of the computer's COM ports, read your computer's documentation to find out how to disable it. After you disable the unused COM port, you can set your faxmodem to use that COM port.

On some systems, it is possible to disable a COM port and its IRQ separately. For the systems that have both options, you have to disable both the port AND the IRQ to free up the port completely. This problem has been observed with some Gateway 2000 desktop computers.

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.

CAS Faxmodems (such as SatisFAXtion faxmodems)

1. Exit Windows.
   
   
2. Unload CASMGR using the command CASMGR /U
   
   
3. Change to the FAX\QUEUE directory.
   
   
4. Type DEL *.Q then press ENTER.
   
   
5. Reload CASMGR.

If the problem persists:

1. Exit Windows.
   
   
2. Unload CASMGR using the command CASMGR /U
   
   
3. Change to the FAX\QUEUE directory.
   
   
4. Delete all the files (DEL *.*).
   
   
5. Reboot your computer.

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

NOTE: If you select a Sendfax modem while installing FAXability, you won't have an "Inbox" log because Sendfax modems can only send, not receive.

NOTE: Net SatisFAXtion users will not have a "Faxmodem:" icon because you don't have a faxmodem board in your own workstation.

A conflict with Symantec Speedrv is one known source of the problem.

This usually indicates that there is an IRQ conflict on the COM port the faxmodem is using.

Sometimes the Inbox/Outbox will get hidden by another window. Here's a quick way to determine if the Inbox/Outbox windows exist in FAXability:

1. Start FAXability.
   
   
2. Select "Window" from the FAXability Manager pull-down menus. If the Inbox/Outbox exists, it will be listed in the bottom portion of this menu. Select "Tile Top to Bottom" to rearrange the open windows and place all icons across the bottom of the FAXability window.

Restoring FAXability Logs:

If one of your logs is actually missing, here's how you can create a new log to take its place.

1. Select "File" from the FAXability Manager pull-down menus.
   
   
2. Select "New Log".
   
   
3. Fill in the "Log Title" with the word "Inbox" or "Outbox" as appropriate.
   
   
4. Click on the "Default Inbox" or "Default Outbox" button.
   
   
5. Click on the "OK" button.

NOTE: When you exit FAXability, it saves the current settings in the FAXABLTY.CFG file.

This error can result from these situations:

• You ran INSTALL by selecting Run from the File menu in the File Manager window.
  
  
• CAS.DLL is not on the diskette.

INSTALL will not run correctly when Run from the File Manager's File menu. There are two correct ways to run INSTALL:

1. Select Run from the File menu in the Program Manager window and enter A:\INSTALL.
   
   
2. Using the File Manager, select drive A and double-click on INSTALL.

If these methods don't work, examine the directory of the FAXability diskette to ensure that it lists the file CAS.DLL.

This can happen if your DOS PATH statement is too long or MANAGER.EXE has been deleted.

On the Intel 14.4EXF Modem, CASMODEM Error (13) mean the EEPROM was not correctly programmed at the factory. In this case the data modem will work correctly (TESTCOM will pass all tests), but the faxmodem will not.

FAXability Plus/OCR can report this error if the DOS PATH statement is too long (longer than 127 characters) or if the XLATSRVR.DLL file is accidentally deleted. This error can be followed by the error "Can't find XRPC.DLL."

Make sure the PATH command in your AUTOEXEC.BAT file includes C:\FAXABLTY\CAL\BIN. If you installed FAXability into a directory other than "javascript:void(null);", use that directory in place of "javascript:void(null);".

Make sure that your path does not exceed the 127 character limit set by DOS. You can count the characters in the PATH command line, or you can type the following command from the DOS prompt:

The active path will be displayed on the screen. Check to see if any part of it is being cut off by the DOS 127 character limit.

This error can occur if the DOS PATH statement is too long (longer than 127 characters) or if the XRPC.DLL file is accidentally deleted.

If you want to install FAXability Plus as a shared resource on a network, you must use FAXability Plus version 1.0n with Intel NET SatisFAXtion version 2.0.

If you don't have NET SatisFAXtion version 2.0, you can still install FAXability on a workstation, but you can't share it across the network. Here's the equipment you need in order to run FAXability Plus or Plus/OCR.

• A computer capable of running Windows in standard or 386 enhanced mode (80286 processor or better).
  
  
• 640K bytes of conventional memory and at least 2Mb of extended memory.
  
  
• A local hard disk with at least 2Mb free for FAXability software, (6Mb for Faxability Plus/OCR), plus 8M bytes more recommended for storing received faxes.
  
  
• EGA, VGA, or Hercules or other compatible monochrome graphics adapter.
  
  
• Microsoft Windows 3.0 or later (standard or 386 enhanced mode) installed and working correctly on the local hard disk. Before installing FAXability, you must be able to invoke Windows programs and print from them. If you have problems doing this, contact Microsoft technical support.
  
  
• A faxmodem installed and working correctly in the workstation that will be sending faxes.

NOTE: Be sure to install the DOS-based SatisFAXtion software before installing FAXability.

This error occurs when you start FAXability if the CASMODEM driver didn't load when your system started up. There are two reasons why CASMODEM doesn't load: either the CASMODEM command doesn't execute or CASMODEM detects a problem while loading. To determine if CASMODEM command executes when your system starts up, use a text editor to view your AUTOEXEC.BAT file. Find a line at or near the bottom of the file that reads:

Intel faxmodems:
C:\FAX\CASMODEM.EXE C:\FAX\CASMODEM.CFG

non-Intel faxmodems:
C:\FAXABLTY\CASMODEM.EXE C:\FAXABLTY\CASMODEM.CFG

NOTE: The FAX and FAXABLTY directory names are the defaults. If you installed the files into a different directory, substitute your directory name.

Place a PAUSE command on the line below the CASMODEM command line. Save the new AUTOEXEC.BAT file and reboot the computer. The PAUSE command will make screen pause after CASMODEM executes so you can see CASMODEM's message.

CASMODEM versions 2.01i and 1.10i accept the following parameters (also called command line switches):

CASMODEM [/R, /U] [/C1, /C2, /SF] [/D] [/V] [/Q] [/Ix] [/Pxxx] [cfgfile]

When you use /R or /U, you don't need to include any other parameters. /R and /U perform exactly the same function: they remove CASMODEM from memory.

If you don't specify the faxmodem type (/C1, /C2, or /SF), CASMODEM automatically performs a test to determine the faxmodem type.

When you use the /D parameter, CASMODEM doesn't load, but performs diagnostic checks on the COM ports in the system. /D will report the addresses and IRQs of all the COM ports in the computer as well as the type of UART each uses. This is very useful in troubleshooting COM port and IRQ conflicts.

If you include "cfgfile" on the CASMODEM command line, you must enter all parameters in front of "cfgfile". CASMODEM ignores any parameters entered after "cfgfile".

It may be easier to edit an existing logo rather than setting all the image attributes from scratch. The Intel FAXability software comes with a ready-made logo called FAXABLTY.PCX. You can load FAXABLTY.PCX into Windows Paintbrush (or other graphics editor) and erase or edit the logo. When you save the image, it will be the same size as the original image.