'CPBVXD.386', or 'FASTBACK.386', you will need to add a
semicolon to the beginning of these lines. Common symptoms of a
drive conflict are error 61B or lockups.
2.0 Troubleshooting.
2.1 General Protection Fault.
In some situations, CBW may fail with a message indicating
that a General Protection Fault was detected. In situations
like this, the most common cause is having a parameter of the
EMM386.EXE device driver not properly set. To check for this
situation, edit the CONFIG.SYS file and place a remark, REM
before the DEVICE=EMM386.EXE line. Next, reboot the computer
and retry the CBW operation. If the error no longer occurs,
it is an indication that one of the parameters of the
EMM386.EXE line is conflicting. Try removing parameters one
at a time until the conflicting paramter is located. The Dos
manual contains an explanation of the EMM386.EXE and its
parameters.
If the error persists, or if you do not have a line with
EMM386.EXE, then we need to check for a device driver conflict
as stated in section 1.3. Occasionally device driver
conflicts can cause a General Protection Fault.
3.0 Performance Tips
3.1 Video Drivers
Some systems may experience slow backup speeds. On these
systems, improvements may be gained by changing from the
default VGA driver to the driver supplied with the video
board. To determine if this is the problem, start a backup,
then minimize the CBW window. It is normal for backup speeds
to improve somewhat with CBW minimized, however, if the
results are extreme it may be necessary to change the video
driver. See the video board manual for instructions.
3.2 Operating CBW in the background.
While CBW is capable of running on a system in the background,
performance may decline with each additional application
running. Memory is used by each application which could cause
CBW to fail with an out of memory error.
When running a backup operation in the background, some open
files may not back up.
For fastest performance and to assure a complete backup, you
may wish to operate CBW as the only application open on the
system.
3.3 Memory and Resources.
If you do not have sufficient memory or resources to execute
CBW you will receive an error message. However, having less
than 2.5M of available memory or less than 70% resources may
result in slow performance. If this is the case, you can
improve performance by making more memory or more resources
available to CBW.
To check your available memory, choose Help from the Program
Manager, and then choose About Program Manager. This screen
will provide you with the amount of memory and system
resources available.
To make more memory and resources available, you may need to
close other applications, minimize Program Manager, add more RAM,
or increase the size of your permanent/temporary swap file.
4.0 Considerations for Network Users.
Generally CBW works transparently with Windows for Workgroups,
NetWare Lite and Lantastic, however, with the current version
of CBW, specific file attributes, bindery and privilege
information will not be saved. Please refer to the Networks
Applications section of the manual for more information.
In the Windows for Workgroups environment, if a "Sharing
Buffers Exceeded" message occurs try the following changes:
In the [386enh] section of the SYSTEM.INI increase
NetHeapSize= to 48 and DMABufferSize= to 064. If the error
still occurs you may need to de-select the enable Share Option
in Network under Control Panel.
5.0 General Trouble-Shooting Hints.
SOFTWARE. If you are not able to resolve an error after
following the suggestions given on the error screen, it is
recommended to do the following:
1. Re-try the operation, look for consistent results.
2. Try another tape. Make sure your tapes are on the
Approved Tapes List in the manual or use a Colorado
Memory Systems brand tape for your drive.
3. Check the hard drive for lost clusters, bad sectors, and
fragmentation. If errors occur, correct by running a disk
utility (Norton Utilities, PCTools, etc.) or use 'CHKDSK /F'.
See your Dos manual for more information.
4. Close down all other applications, remove items from your
startup group and remark items out of the load= and run=
lines in the WIN.INI file.
5. Re-boot with a clean AUTOEXEC.BAT and CONFIG.SYS. It is
recommended that this be done from a bootable floppy
diskette. To receive a fax with instructions for this
process, dial our fax-back service at 1-800-368-9673 and
request document #2900.
HARDWARE. If the drive does not respond when you try to access it
with the software, do the following:
1. Remove the tape from the drive and examine it. If the tape is
unspooled, refer to the drive cleaning instructions in the
manual or refer to QICFAX document #2020.
2. Close down all programs, exit Windows and turn the power off
on the computer. If your tape drive plugs directly into the wall
outlet, disconnect it from the wall outlet, wait a few seconds
and then re-connect it. Turn the power back on.
3. Place a tape in the drive and look to see if the LED is
functioning normally. The tape drive LED should not be on
after the tape stops spinning.
ERRORS and SOME REMEDIES
(If at anytime changes are made to the Windows System.ini or the Win.ini
files, please save the changes and then exit Windows thru Program Manager,
file and exit. Then type win at the DOS prompt to restart Windows.
When changes are made to the Autoexec.bat or Config.sys,
if in Windows, please exit Windows thru Program Manager, file and exit;
and at the DOS prompt reboot your computer.)
10E Unexpected or Bad List Item
- Low actual memory/Resources (Free up memory by closing other Windows applications. Also check to see if you can identify any TSR programs that you might be loading in your CONFIG.SYS or AUTOEXEC.BAT files that are not necessary for your system to operate. i.e. Screen Blanker, Anti-Virus, etc.)
- Try adding /Double_Buffers + to SMARTDRV.EXE in the CONFIG.SYS file.
- Try adding the line "DEVICE=C:\path\EMM386.EXE RAM M9" to the CONFIG.SYS file. If you already have an EMM386.EXE line, REMARK the line and add this one. Please make a bootable floppy and make sure that you can boot from your A: drive prior to changing this. This changes the way memory is accessed and in some cases may conflict with something, preventing you from booting.
- Disable write caching (this applies to all disk caching utilities)
- If backing up a network drive, you may want to check your local drive to see if it is being accessed. If it is, it may be wise to upgrade the memory in the computer to help prevent Windows from using the swap file in such a manner.
- If you are using CBW 1.01, please check with Windows Customer Support to see if an upgrade will help your problem
61B Interrupt Not Available
- If another Colorado Backup Error has preceded this error, make sure that you exit Windows and restart the computer before trying to run CBW.
- Possible driver conflict, check for Fastback.386, VIRWT.386, VFINTD.386, CPBVXD.386, VITD.386 in your SYSTEM.INI file.
- Possible memory conflict. Try to REMARK out your EMM386.EXE line in your CONFIG.SYS file. If this fixes the problem, you may want to try a different configuration of EMM386.
- Try adding IRQ9GLOBAL=YES to the [386ENH] section of your SYSTEM.INI file.
73D User Manager Timeout
- Could be a bad tape. Try other tapes to see if this error is consistent with all tapes.
- Lost clusters or bad sectors on the hard disk drive may cause this type of error. Please run a hard disk utility or CHKDSK from DOS to check for hard disk corruption.
- Try adding IRQ9GLOBAL=YES to the [386ENH] section of your SYSTEM.INI.
209 Memory Bad Request
- If you are using DR DOS 6.0 - delete INSTALL.TMP and CBW.DRV from the CBW directory or the directory you installed the tape backup software into. Run CBW and configure the software for a tape drive. Hint - Select Option, Tape Drive Configuration, and Configure New Tape Drive.
- Lost clusters or bad sectors on the hard disk drive may cause this type of error. Please run a hard disk utility or CHKDSK from DOS to check for hard disk corruption.
- Possible bad tape. Try other tapes to see if this error is consistent with all tapes.
- If you are attached to a dedicated controller, such as and FC-10 or TC-15, try alternative settings for the controller.
- Your system may have settings for External Cache and Internal Cache. Set these to disabled and see if that affects the operation of CBW.
514 Tape header contains unexpected or invalid values
- The tape may be unformatted or incorrectly formatted. Please try another tape or try to format the current tape. Sometimes just retensioning a tape can help.
- If you are attached to a dedicated controller, such as and FC-10 or TC-15, try alternative settings for the controller.
733 Unable to establish communication with the task manager
- Check for DEVICE=CMSWTAPE.386 in the [386ENH] section of the SYSTEM.INI file. If this is not present, add this line as the first line under [386ENH].
- Try to reinstall software.
1165/1167 Drive Communication Fault
- If loading SMARTDRV.EXE in the CONFIG.SYS and AUTOEXEC.BAT files, try to REMARK SMARTDRV.EXE out of the AUTOEXEC.BAT
- Remove the tape drive from the configuration and re-configure the software for a new tape drive. Hint - Select Option, Tape Drive Configuration, Remove Tape Drive Configuration and then Select Option, Tape Drive Configuration, Configure New Tape Drive.
- Check all hardware connections.
- In the Virtual Memory settings of 386 Enhanced, which can be found in the Control Panel folder, of the main group, there is an option for 32-bit disk access. If it is enabled, disable it. If it is disabled, enable it. If it has no effect, return it to the original setting.
- Try to reinstall software.
1176 Drive Configuration Fault
- CBW looks for drive specific information. If you are using a drive other than that which was used when CBW was configured, you should do the following. Remove the tape drive from the configuration and re-configure the software for a new tape drive. Hint - Select Option, Tape Drive Configuration, Remove Tape Drive Configuration and then Select Option, Tape Drive Configuration, Configure New Tape Drive.
- Try to reinstall software.
F02 Tape drive controller configuration failed
- Reboot system then run windows and CBW software again.
- Make sure dedicated controller board(TC-15 or FC-10) is seated in the expansion slot.
- Manually re configure the controller board.
F1B Trakker: Parallel Port Interrupt Not Available Or In Use
- Sound card or Scanner is set to same interrupt as parallel port. It may be necessary to change the interrupt of either the parallel port or the conflicting controller.
- If the Trakker and Printer are attached to the same parallel port, they can NOT be used at the same time.
- This error can be caused if the DOS command SUBST has been used.
Attempting Tape Error Recovery
- This may be caused by a bad block on the tape. Try another tape, if this works, try to reformat the tape that causes the problem.
- If the tape drive head is dirty, this may cause problems reading. Clean the tape drive head and try operation again.
- Low actual memory/Resources (Free up memory by closing other Windows applications. Also check to see if you can identify any TSR programs that you might be loading in your CONFIG.SYS or AUTOEXEC.BAT files that are not necessary for your system to operate. i.e. Screen Blanker, Anti-Virus, etc.)
- The tape software may be corrupt. Try to reinstall CBW.
- If you are attached to a dedicated controller, such as and FC-10 or TC-15, try alternative settings for the controller. Avoid using DMA channel 2.
- Lost clusters or bad sectors on the hard disk drive may cause this type of error. Please run a hard disk utility or CHKDSK from DOS to check for hard disk corruption.
- In the Virtual Memory settings of 386 Enhanced, which can be found in the Control Panel folder, of the main folder, there is an option for 32-bit disk access. If it is enabled, disable it. If it is disabled, enable it. If it has no effect, return it to the original setting.
General Protection Fault
- This may be caused by a bad block on the tape. Try another tape, if this works, try to reformat the tape that causes the problem.
- Lost clusters or bad sectors on the hard disk drive may cause this type of error. Please run a hard disk utility or CHKDSK from DOS to check for hard disk corruption.
- Possible driver conflict, check for Fastback.386, VIRWT.386, VFINTD.386, CPBVXD.386, VITD.386 in your SYSTEM.INI file.
- Possible memory conflict. REMARK out your EMM386.EXE line in your CONFIG.SYS file. If this fixes the problem, you may want to try a different configuration of EMM386.
- Possible conflict with IMouse. Check the AUTOEXEC.BAT and CONFIG.SYS files. If this program is present, REMARK the driver and try again.
- If you are attached to a dedicated controller, such as and FC-10 or TC-15, try alternative settings for the controller. Avoid using DMA channel 2.
- Check for DEVICE=CMSWTAPE.386 in the [386ENH] section of the SYSTEM.INI file. If this is not present, add this line as the first line under [386ENH].
Trakker configuration issues
- Sound card or Scanner is set to same interrupt as parallel port. It may be necessary to change the interrupt of either the parallel port or the conflicting controller.
- Disable "Windows Printing System"
- Disable "Super Queue"
- May be caused if FAX modem is selected as printer. Change printer from fax to a printer.
