|
Contents:
CASMGR DOS ERROR: Disk Full
| Cause: |
Your hard drive has no more (or too little) room to store files. |
| Cure: |
Delete any unnecessary files. Copy important but seldom-used files to floppy disks before deleting them form the hard disk. |
CASMGR DOS WARNING: File Not Found
Intel has identified these causes of this error message:
- The QUEUE subdirectory is corrupt. See "Correcting a Corrupted CASMGR QUEUE" in this document.
- In Novell network workstations, this error can occur if the network drivers IPX and NETX are being loaded after CASMGR in the AUTOEXEC.BAT file and you attempt to send a file that is located on a network drive. Try loading IPX and NETX before CASMGR.
- CASMGR is looking for a file and can't find it.
CASMGR DOS ERROR: General Failure
Cause: The disk is probably not formatted.
Cure: Format the disk. CASMGR DOS ERROR: <FILENAME> Invalid Data
| Cause: |
The file mentioned in the message has been corrupted. |
| Cure: |
If it is a configuration (.CFG) file, delete all CFG files from your FAX directory and rerun SETUP. If it is a PCX or DCX file, use your graphics application to regenerate the file.
Otherwise, use this command to delete all files in the FAX program's QUEUE directory that have the .Q extension:
ERASE C:\FAX\QUEUE\*.Q
If the problem persists, use these commands to clear the problem:
ERASE C:\FAX\QUEUE\*.Q
ERASE C:\FAX\QUEUE\*.LOG |
NOTE: Erasing *.LOG will delete all your log entries. CASMGR DOS ERROR: Internal Error, Task Switch Failed
This error results when CASMGR loads into EMS (expanded) memory provided by an expanded memory manager which is not 100% compatible with LIM EMS 4.0 specification. IBM's XMA2EMS.SYS is one such expanded memory manager. This could also be true of expanded memory emulators.
Run SETUP and set the "CASMGR EMS Memory usage" to "Never use EMS". If the error goes away, you have either of two problems:
- Your expanded memory manager is not 100% LIM 4.0 compatible.
- Your expanded memory manager is in conflict with another device in your computer.
100% compatible expanded memory managers include: Intel's EMM.SYS (for Above Board)
and ILIM386.SYS (for Inboard 386 & 386/PC)
Microsoft's EMM386.EXE and EMM386.SYS
Qualitas's 386 to the MAX
Quarterdeck's QEMM 386
CASMGR DOS ERROR: Invalid Data
This error can be caused when a fax is trying to be received, but the hard disk is being used for a long time doing another task (even printing a fax). CASMGR DOS ERROR: Invalid Drive Specified
| Cause: |
You specified a drive that doesn't exist or that you don't have access to. |
| Cure: |
Specify a valid drive. |
CASMGR DOS ERROR: Path Not Found
There three reasons this error message comes up:
- Our software is looking for a file and can't find it.
- Corruption of the Queue subdirectory. In this case you should make sure that there are no pending events and no unread receives. Next delete all the files in the Queue subdirectory and reboot the system.
- Sending a file from/saving a file to a network drive when either:
- You're using a CASMGR version earlier than 1.20 or,
- The network software loaded after CASMGR.
You must use CASMGR 1.20 to fax/save files across a network and you must always load the network software before CASMGR. CASMGR DOS ERROR: Sharing Violation
| Cause: |
Another application opened a file that the FAX program needs. |
| Cure: |
Quit the other application(s) you are running. |
CASMGR DOS WARNING: Access Denied
This error occurs when a file or directory is inaccessible. CASMGR DOS WARNING: Device Not Ready
| Cause: |
The door on the disk drive is open. |
| Cure: |
Close the door. | CASMGR DOS WARNING: Disk Full
| Cause: |
Your hard disk is full. |
| Cure: |
Remove unnecessary files from your hard disk. |
CASMGR DOS WARNING: Too Many Open Files
This errors means you specified too small a value on the FILES= line in your CONFIG.SYS file. Increase the value to resolve the problem.
SatisFAXtion Classic Only:
SatisFAXtion software version 1.00 would leave files open so you would get this message after 7 current connections. This problem was fixed in version 1.01. CASMGR ERROR: At Least One Sub-Event Failed
| Cause: |
At least one event in the group event failed (an individual's destination hardware may be busy, etc.). |
| Cure: |
Look in the log to see which event(s) failed (use the FAX program's Events Status/Logged events screens to get to the log). Resend the event. |
CASMGR ERROR: Bad PCX File Header
| Cause: |
A PCX or DCX file was scheduled to be sent, but it was damaged before it was sent, was a color image, or was scanned at a resolution greater than 200 by 200 dots per inch (dpi). |
| Cure: |
Use a graphics application to make sure the file is a black-and-white image with a resolution is 200 by 200 dpi or less. Then resend the file. |
CASMGR ERROR: Bad Phone Number
| Cause: |
CASMGR didn't recognize the phone number. |
| Cure: |
Edit the phone book entry associated with this number to make sure it is a valid number. |
CASMGR ERROR: Event Not Found
| Cause: |
This is an internal fax software error. |
| Cure: |
Turn off your computer, turn it on again, and try again. |
CASMGR ERROR: File Already Exists
| Cause: |
The FAX program tried to save a file with a file name that already exists, or you tried to create a phone book with a name already used by another phone book. |
| Cure: |
If you were saving a received file, you'll be asked if you want to overwrite the existing file. If you were creating a phone book, you must specify a different name. |
CASMGR ERROR: SatisFAXtion Command Set Error
| Cause: |
The fax board is not operating correctly. |
| Cure: |
Turn off your computer, turn it on again, and choose Run diagnostics from the FAX program's Options screen. |
CASMGR ERROR: SatisFAXtion Is Busy
This error can result when a disk caching program (such as Super PC-KWIK) loads after CASMGR in the AUTOEXEC.BAT file. Always load your disk cache before loading CASMGR.
Also, disable the "Write Cache" (also called "Delayed Write") feature of your disk cache. CASMGR ERROR: Satisfaxtion Isn't Responding
This error could be caused by several things:
- I/O address conflict.
- Software Conflict
- Installing a Rev. 009 SatisFAXtion MCA board into a cost-reduced IBM Model 70 motherboard. Rev. 010 SatisFAXtion boards work fine.
- Bad slot.
- Bad board.
- Turn off your computer, turn it on again, and choose Run diagnostics from the FAX program's Options screen.
- Check that the fax board's I/O address isn't being used by another board in the computer.
- Move the fax board to another expansion slot.
CASMGR ERROR: Manual Connect Posted Too Long
| Cause: |
You tried to use the current connection as the phone number, but too much time elapsed while waiting for an open connection. |
| Cure: |
Establish the connection before choosing Send (from the Select Send Options menu). |
CASMGR ERROR: More Than 1023 Pages Of Receive
| Cause: |
The fax board tried to receive more data than it can handle. |
| Cure: |
Have the sender resend the information in more than one event. |
CASMGR ERROR: Phone Line Disconnected During Event
| Cause: |
The phone connection was broken while the fax board was sending or receiving.
It is also possible that you attempted to send a fax in fine mode to a fax machine that only accepts standard mode transmissions. This error can also occur if you try to send using Current Connection while using the upgraded SatisFAXtion Classic with DOWNLOAD.200 version 2x08. |
| Cure: |
If you were receiving files, have the sender resend them. If you were sending files, resend them. Try sending in standard mode if fine mode doesn't work. |
CASMGR ERROR: Unexpected End Of File
The error "unexpected end of file" can occur if you send a fax from Microsoft Excel when the paper orientation settings of Excel and FAXability are different (one is portrait and the other is landscape). Make sure you set both Excel and FAXability to the same paper orientation before sending a fax from Excel.
With SatisFAXtion Classic software earlier than 1.20, this error can be caused by using the BUFFERS /x command in DOS 4.XX. There are three ways to correct this problem:
- Updating to version 1.20 of the SatisFAXtion Classic software.
- Removing the /x from the BUFFERS command line.
- Prohibiting the SatisFAXtion software from using EMS (expanded) memory.
CASMGR Is Busy, Can't Remove CASMGR From Memory
| Cause: |
You tried to uninstall CASMGR while the SatisFAXtion was sending or receiving, or while a "to be polled" event was waiting. |
| Cure: |
Either wait for all events to complete, or cancel all events, then uninstall CASMGR. |
CASMGR (Is) NOT INSTALLED
| Cause: |
You tried to run the FAX program or uninstall CASMGR when CASMGR was not installed in memory. |
| Cure: |
Enter CD \FAX to change to the FAX directory. If you copied the FAX software into a different directory, change to that directory. Then type CASMGR and press ENTER.
If CASMGR loads, examine your AUTOEXEC.BAT file. SETUP inserts the CASMGR command at the end of the AUTOEXEC.BAT file. If you use a menu program, your menu may run before CASMGR loads. Always insert the CASMGR command before the command that starts your menu program. If CASMGR doesn't load, write down the error message and look it up in Appendix A of the Intel SatisFAXtion Board User's Guide. Once you've solved the problem, try loading CASMGR again. |
CASMGR UNKNOWN ERROR: 13554
This error can occur when you run SatisFAXtion's FAX.EXE program if you loaded the LANSelect after CASMGR. If you try to load LANSelect before CASMGR, CASMGR will report that it's already installed. Upgrade your LANSelect program to version 1.6 or later.
See LANSelect in the Software Compatibility section for more information on this problem. CASMGR WARNING: File Was Sent, But Might Contain Errors
| Cause: |
The communications hardware found errors or bad phone lines when it was sending, but it completed the send anyway. |
| Cure: |
Check the documents that the destination received, and, if damaged, resend them. |
CASMGR WARNING: Image File Is Corrupted
| Cause: |
Part of a received file has been corrupted. |
| Cure: |
Have the sender send the file again. |
CASMGR WARNING: Invalid Or Missing Logo File
| Cause: |
The logo file associated with this event was deleted or damaged between the time it was selected and the time it was sent. |
| Cure: |
Make sure the logo file exists or choose another. You might also try sending the logo file separately as a file to a fax machine. If you receive the "Image too wide to send" error when you do this, you'll know that the logo file is too big to send or has a resolution greater than 200 by 200 dots per inch (dpi). |
| Cause: |
This error can also occur if you use CCSEND and add the /C parameter to the command line when the default logo is set to None. The fax actually sends correctly but CCSEND reports the error. |
| Cure: |
In this case either ignore the message, don't use the /C parameter, or run SETUP and specify a default logo file. |
CASMGR WARNING: Receive Data Lost
| Cause: |
The fax board tried to receive a file but some of the information was lost. |
| Cure: |
View the received file, and, if damaged, have the sender send it again. |
Rebuilding The Cas (CASMGR) Queue
CASMGR maintains a database to keep track of files in its QUEUE directory. If files have been accidentally deleted from the QUEUE directory, the queue database will no longer correspond to the contents of the QUEUE and your fax log will display an error.
Here's how to correct the problem:
- Exit Windows.
- Change to the SatisFAXtion QUEUE directory (usually C:\FAX\QUEUE).
- Delete the three queue index files by typing:
DEL *.Q
- Restart (Ctrl-Alt-Del) your computer and load CASMGR. (CASMGR loads automatically if included in your AUTOEXEC.BAT file). CASMGR rebuilds the queue files when it loads.
If the problem persists and you are using FAXability Plus 2.0, see "Correcting a Corrupted CASMGR QUEUE" in this document. If you are using FAXability 1.0, FAXability Plus 1.x, or FAXability Plus/OCR 1.0, follow these directions.
- Exit Windows.
- Delete all the files in the directory by typing:
- DEL *.*
- Reboot your computer
This applies to:
| 
