When you think about "PC drives", you probably think about the four classical types of drives; floppy drives, hard drives, tape drives, and CD-ROM drives. These are the most widely accepted and supported drives available today. However, drive designers are always looking for ways to provide better and faster storage solutions, and pack ever-more data onto smaller, more efficient media. As a result, the PC industry often deals with a number of "non-standard" drives - devices which utilize existing magnetic and optical technologies, but do not easily fit the mold of other drives. "Non-standard" drives are also traditionally after-market or add-on devices that are attached through a parallel port, a SCSI interface, or some other proprietary type of drive adapter. Iomega and SyQuest are perhaps the two largest and best-respected makers of "non-standard" drives, and this chapter will look at the background and troubleshooting of the four most popular "non-standard" drives; the Iomega Zip drive, the Iomega Ditto drive, the Iomega Bernoulli drive, and the SyQuest drive.

In order for "removable media" to be popular, it must follow three basic guidelines; it must record quickly, it must hold a lot of data on a single cartridge (or other media), and it must be portable between drives. Floppy drives are very portable, but they hold only a little data. Tapes hold a lot of data, but they are slow, and are not very portable between drives. Hard drives are quite fast, and hold a great deal of data, but they are simply not portable. CD-ROM drives are relatively fast, they also hold a lot of data, and the CDs themselves are very portable, but you need specialized drives to "burn" a CD - and the disc can be used only once. The search for reusable, high-capacity media that is transportable between inexpensive, readily available drives has led Iomega to produce their Zip drive.

The Zip drive has become perhaps the single most popular "non-standard" drive in production today - in fact, the Zip drive is SO popular that some PC makers include them as standard equipment in new systems. Zip drives offer relatively fast seek times at 29mS, and can sustain data rates of 300KB/s across the parallel port (or 1MB/s via SCSI or IDE interfaces). Each cartridge can hold up to 100MB which is large enough to hold huge illustrations, CAD layouts, and even small multimedia presentations. When used with a SCSI interface and a properly configured Adaptec SCSI controller, you may even boot from the Zip drive. Zip drives are available in both internal and external versions.

Symptom 44-1. An Iomega Zip drive displays a floppy disk icon under Windows 95. However, the drive appears to operate properly. This is almost always due to the use of a real-mode DOS driver to support the Iomega drive and adapter. You will need to update the real-mode driver to an appropriate protected-mode driver for Windows 95. For SCSI adapters, you need to find the protected-mode SCSI driver for your particular SCSI adapter and install it through the Add New Hardware wizard in the Control Panel. After the protected-mode driver is installed, you can remove the obsolete real-mode driver from CONFIG.SYS. For native Iomega SCSI adapters, get the protected mode drivers directly from Iomega. For parallel port Zip drives, uninstall the old drive software and install the new Windows 95 driver software.

Symptom 44-2. There is no drive letter for the SCSI Zip drive under Windows 95. The drive does not appear to respond. In virtually all cases, the SCSI driver has not loaded properly. First, open the Device Manager and expand the SCSI Controllers entry, then check the Iomega Adapter line beneath it. If there is a yellow symbol with an exclamation mark on it, the Windows 95 driver did not load. Check the controller next by highlighting that Iomega Adapter line, then select Properties. Click on the Resources page, then verify that your I/O Range and IRQ options are set correctly - they must match the jumper settings on your adapter board. If you must update the resource settings manually, make sure the Automatic Settings box is not checked (and remember to save any changes). If you allocated new resources, you may have to shut off the PC and change jumper settings on the controller board itself to match the resources allocated in the Device Manager. Restart the computer - once the system reboots, the Windows 95 driver should load normally.

If problems persist, check the signal connector (especially for SCSI adapters). Make sure the SCSI cable is intact, and connected to the drive properly. If problems continue, your SCSI adapter is probably installed correctly, but the bus may be terminated improperly. Make sure that you terminate both ends of the SCSI bus properly.

Symptom 44-3. There is no drive letter for the parallel port Zip drive under Windows 95. Parallel port drive problems can almost always be traced to faulty connections, port configuration issues, or driver problems. Check the external power connector first. Parallel port drives are powered externally. Make sure that the power pack is working, and see that the power cable is connected properly to the drive. If the drive does not appear to power up, try a different power pack or drive. Check the signal cable next, and make sure that you are using a good-quality, known-good parallel port cable which is attached securely at the PC and drive. The Zip drive is very sensitive to devices such as copy protection modules (or "dongles"), and other "pass-through" devices. Try connecting the drive directly to the parallel port. Also disconnect any printers on the parallel port.

The parallel port setup may be incorrect. Reboot the PC and enter CMOS Setup. Check to see that the parallel port is configured in EPP or bi-directional mode. If the problem continues in the EPP mode, try configuring the parallel port for "compatibility mode". For SCSI installations, check the SCSI host controller. There is a known incompatibility between the Iomage Zip drive and the Adaptec 284x adapter - the Iomega PPA3 driver does not work with the Adaptec 284x controller. Check with Iomega for an updated driver.

There may be a problem with your driver(s). Open the Device Manager and find the SCSI Controllers entry (even though it is a parallel port device). If there is no such entry, the driver is not installed. If you expand the SCSI Controllers section, there should be an entry for the Iomega Parallel Port Zip Interface. If not, the driver is not installed. Check for hardware conflicts. If the Device Manager entry for the Iomega Parallel Port Zip Interface has a yellow circle with an exclamation mark on it, the interface is configured improperly and is conflicting with other devices. Also check for device properties. Highlight the Iomega Parallel Port Zip Interface entry, click on Properties, then select the Settings page. Find the box marked Adapter Settings, then type:

/mode:nibble /speed:1

Save your changes and reboot the system. If that fails, try reinstalling the drivers. Highlight the Iomega Parallel Port Zip Interface and select Remove. Then reinstall the drivers from scratch. Next, try running in DOS. Start the PC in DOS mode (command prompt only), then install the Iomega installation disk and type:

a:\guest <Enter>

If the Zip drive still does not receive a drive letter, the parallel port may be faulty or incompatible with the drive. Try the drive on another system. If this tactic works on another system, the problem is definitely related to your original PC hardware. If the problem follows the drive, the fault is likely in the drive. Try another drive.

Symptom 44-4. The system hangs when installing drivers for Windows 95. System hangups during installation are usually the result of hardware conflicts or problems. Check the signal cable first, and make sure that you are using a good-quality, known-good cable which is attached securely at the PC and drive. Open the Device Manager and find the SCSI Controllers. If there is no such entry, the driver is not installed. If you expand the SCSI Controllers section, there should be an entry for the Iomega Parallel Port Zip Interface. If not, the driver is not installed.

Check for hardware conflicts. If the Device Manager entry for the Iomega Parallel Port Zip Interface has a yellow circle with an exclamation mark on it, the interface is configured improperly and is conflicting with other devices. Highlight the Iomega Parallel Port Zip Interface entry, click on Properties, then select the Settings page. Find the box marked Adapter Settings, then type:

/mode:nibble /speed:1

Save your changes and reboot the system. If problems continue, try running in DOS. Start the PC in DOS mode (command prompt only), then install the Iomega installation disk and type:

a:\guest <Enter>

If the Zip drive still does not receive a drive letter, the parallel port may be faulty or incompatible with the drive. Try the drive on another system. If this tactic works on another system, the problem is definitely related to your original PC hardware. If the problem follows the drive, the fault is likely in the drive. Try another drive.

Symptom 44-5. After installing a Zip drive, you find the other drives in the system are using the DOS compatibility mode. This is almost always the result of the GUEST.EXE program. The real-mode Guest.exe program supplied by Iomega is designed to allow you to access the Zip drive in DOS and Windows 95, and this causes the other drives in your system to use the "DOS compatibility mode" (you may also notice a decline in drive or system performance). Try installing the protected-mode drivers for the Iomega drive:

• In the Control Panel, double-click the Add New Hardware icon.
• Click Next, click the No button, then click Next.
• Click Other Devices, and then click Next.
• In the Manufacturers box, click Iomega, and then click Have Disk.
• Install the files from the Windows 95 CD-ROM by inserting the CD-ROM in the drive, typing the following line in the "Copy Manufacturer’s Files From" box, and then clicking Next:

• After the files are copied, click Finish.
• Restart the computer when prompted to do so.

Symptom 44-6. The Zip drive takes over the CD-ROM drive letter in Windows 95. You may simply need to switch drive letters between the Zip drive and CD-ROM drive:

• Open Device Manager and double-click on the Disk Drives entry.
• Highlight the Iomega Zip drive entry and click on Properties.
• Click on the Settings page.
• In the Reserved Drive Letters section, there is a Start Drive Letter and an End Drive Letter setting. Enter the desired drive letter for the Zip drive in both start and end drive entries (be sure to use the same drive letter for both start and end). Click on OK.
• Double-click on the CD-ROM entry.
• Highlight your CD-ROM Drive entry and click on Properties.
• Click on the Settings page.
• In the Reserved Drive Letters section, there is a Start Drive Letter and an End Drive Letter setting. Enter the desired drive letter for the CD-ROM drive in both start and end entries (be sure to use the same drive letter for both start and end). Click on OK.
• Click on OK to close Device Manager, then shut down and restart the computer.

Symptom 44-7. You encounter duplicate ZIP drive letters. You notice that the Zip drive (or another drive) has been assigned a duplicate drive letter. In most cases, the problem can be traced to a third-party SCSI adapter and drivers which conflict with Iomega SCSI drivers. Do NOT use any drive before correcting this problem. Open your CONFIG.SYS file and examine each driver that scans the SCSI bus to assign drive letters. Chances are very good that you have a third-party driver which is assigning a letter to the Zip drive, as well as an Iomega-specific driver assigning another letter to the Zip drive. Use a command line switch with the third-party SCSI driver to limit the number of IDs that will be assigned.

Symptom 44-8. A Zip guest locks up or cannot locate the drive or adapter. Chances are that an ASPI manager referenced in the GUEST.INI file is conflicting with hardware in the PC. This often happens in systems with two SCSI adapters (and parallel ports). Try editing the GUEST.INI file. Open the GUEST.INI file on your Iomega install disk and specify which ASPI manager needs to load in order to access the Zip drive. Remember to make a backup copy of the GUEST.INI file before editing it. As an alternative, choose the Iomaga SCSI adapter driver. If you are using a native Iomega SCSI adapter, choose the ASPI manager that applies to the adapter as shown in Table 44-1. Once you have identified the proper ASPI manager for your adapter, REMark-out all of the other ASPI lines in GUEST.INI except for the one that you need.

If you are using a non-Iomega SCSI adapter, you will need to add the complete path and filename for the driver to GUEST.INI, and REMark-out all of the other ASPI drivers. Once the GUEST.INI file is updated, save your changes and reboot the system, then run GUEST from the drive and directory containing the updated GUEST.INI file. If problems persist, try the drive on another system, or try a new drive on the suspect system.

Symptom 44-9. You encounter Zip drive letter problems under DOS. The drive letters following C: may change unexpectedly when Iomega drivers are installed to support a new device. This can interfere with applications that look at specific drives, or access to network resources. You will need to relocate the drives before installing Iomega software. Since the GUEST.EXE utility loads at the end of AUTOEXEC.BAT, the Iomega drive will be assigned the last drive letter. DOS assigns letters to network drives alphabetically after assigning letters to any internal or external drives connected to the computer. When a new drive is added, the network drive may be "pushed down" one letter (i.e. from E: to F:). Applications that reference specific drive letters may then fail to work correctly unless they are reinstalled or adjusted for the drive letter change. If you use a batch file to connect to a network, it will need to be updated to the new drive letter. A network log-in script may also need to be revised.

Use the DOS LASTDRIVE= command to relocate your first network drive letter further down the alphabet - this insulates your network drive letter assignment from future changes should you add other drives to your system. For example, you can make your network drive N: by adding the following line to the end of CONFIG.SYS. This would allow you to add ten drives (D: through M:) to a system without pushing down your network drive letter:

LASTDRIVE=M

NOTE: Do not set your last drive to Z: or you will be unable to access any network drive. If you use multiple network drives, do not set your last drive to a letter late in the alphabet (such as X: or Y) since that will limit the number of network drives you can use simultaneously.

Check your CD-ROM drive letters. CD-ROM drives have a specific drive letter determined by the /L option of MSCDEX in AUTOEXEC.BAT (for example, /L:E assigns the CD-ROM as drive E:). When a new drive is installed, DOS may assign the CD-ROM drive letter to the new drive, and the CD-ROM drive may seem to disappear. Change the drive letter for the CD-ROM to a letter not assigned to another drive. You may want to relocate your CD-ROM drive several letters down the alphabet so that you do not have to relocate it each time you add a new drive to your system. You must have a LASTDRIVE statement in CONFIG.SYS which sets the last drive equal to or later than the CD-ROM letter. Finally, check the overall system configuration. When DOS does reassign drive letters, be sure to check each of the points below:

• Edit the PATH statement in AUTOEXEC.BAT to correctly reference new drive letter.
• Edit any batch files (including AUTOEXEC.BAT) to correctly reference new drive letters.
• Edit all Windows .INI files and Windows groups to correctly reference new drive letters.
• Check other application setup files and rerun the application’s setup if drive letters cannot be edited.
• For networks, check your user log-in script for references to specific network drive letters.
• Reboot the computer and check major applications - those that do not work with the new drive letter may need to be reinstalled.

Symptom 44-10. The GUEST utility cannot find an available drive letter. If all drive letters are in use, GUEST will not be able to assign a drive letter to the Zip drive. Change the last drive designation. Use the DOS LASTDRIVE command in the end of CONFIG.SYS to increase the number of available drive letters. Do not use a letter near the end of the alphabet.

Symptom 44-11. System recovery fails after the Zip Tools setup process is complete. If the Zip Tools software for your Zip drive fails to install properly (or if the system hangs or was powered down), the Windows Startup group will have a Zip Setup icon that will attempt to run each time Windows is started. Delete the Zip icon in your Startup group, then reinstall the Zip software.

Symptom 44-12. You see error messages such as; "Can't Find Zip Tools Disk" or "No Drive Letters Added" when using Zip parallel port drives. In most cases, you will have to manually assign the proper ASPI driver by editing your GUEST.INI file. Open the GUEST.INI file on your Iomega install disk. Highlight the ASPI driver line that reads ASPIPPA3.SYS, then add the following commands; /MODE=1 /SPEED=1. Remember to make a backup copy of the GUEST.INI file before editing it. The final command line should appear such as:

ASPI=ASPIPPA3.SYS SCAN /INFO SL360=NO SMC=NO /MODE=1 /SPEED=1

Save your changes to GUEST.INI, then run GUEST from the drive and directory that contains your edited GUEST.INI file. GUEST should now assign a drive letter to the Zip drive. Reboot the PC, start Windows, then Run the Iomega Setup routine from the drive and directory which contains your edited GUEST.INI file. The Windows installation should now proceed normally.

Next, check the signal connector, and make sure that the parallel port or SCSI cable is connected properly between the drive and system. Try a known-good working signal cable. If problems persist, boot the system from a "clean" diskette and try running GUEST. If a drive letter is assigned properly, then there is a driver loading in CONFIG.SYS or AUTOEXEC.BAT which conflicts with the Zip drive. You will have to systematically locate the offending driver. Finally, try the Zip drive on another PC. If GUEST works on another PC, the original PC is using an incompatible parallel port. If the drive still refuses to work, try another Zip drive.

Symptom 44-13. Windows 3.11 allows network drive letter to conflict with Zip drive letter. You may see this as a "No Zip Tools Disk Detected" message. The drive may also no longer be accessible from the File Manager or DOS prompt. The problem is that Windows for Workgroups allows GUEST to assign a drive letter that is already used by a network drive. Remap the shared volume - since GUEST is typically run first, you will need to alter the network drive letter under Windows for Workgroups.

Symptom 44-14. The Zip drive setup could not find a Zip Tools disk for Zip parallel port drives. This is usually an issue with the GUEST.INI file which needs to be edited for proper operation. Start the system from a clean floppy diskette, insert the Iomega installation disk, then try running the GUEST utility. If a drive letter is assigned, there may be a driver in CONFIG.SYS or AUTOEXEC.BAT conflicting with the Zip drive. If GUEST fails to assign a Zip drive letter from a clean boot, open the GUEST.INI file in a text editor, locate the ASPI=ASPIPPA3.SYS line, then add the switches; /MODE=1 /SPEED=1 which makes the complete command line appear like:

ASPI=ASPIPPA3.SYS SCAN /INFO SL360=NO SMC=NO /MODE=1 /SPEED=1

Reboot the PC and run the GUEST utility again. If GUEST does run, but you still cannot read the Zip Tools disk, make sure that the signal cables are secure between the drive and system. If problems persist, try the Zip drive on another PC. If GUEST works on another PC, the original PC is using an incompatible parallel port. If the drive still refuses to work, try another Zip drive.

Symptom 44-15. You cannot print while using a ZIP drive. The Iomega parallel port Zip drive works as a "pass-through" device, and the software allows the drive to share a parallel port with printers. However, some printers require two way communication between the printer and parallel port which conflicts with the Zip software - this can cause data corruption and system lockups. In many cases, disabling the bi-directional communication features of the printer will clear the problem.

Canon BJ-610/Canon BJC 610: These printers use drivers that are incompatible with the Zip drive - the drivers reserve the parallel port exclusively for the operation of the printer, and the Zip drive is unable to access the port (and will usually result in a system lock-up when the drive is accessed). The drivers for the Canon printers must be removed. The installation program for the printers will add the following lines to the [386Enh] section of your SYSTEM.INI file. These entries must be removed:

DEVICE=WPSRCOM.386

DEVICE=WPSCREM.386

DEVICE=WPSRBND.386

The following line in WIN.INI will also have to be removed:

LOAD=WPSLOAD.EXE

At this point, the Zip drive will function, but the printer will not (at least not in its high-resolution modes). To restore full printer operation, you will need to re-install the Canon drivers.

Canon Multi-Pass 1000: You cannot use this printer and the parallel port Zip drive at the same time. The only way to make this printer and drive compatible is to change the output of the printer to "File" when you need to use the Zip drive, then back to "LPT1" when you want to use the printer. Use the following procedure to toggle the output from File to LPT1 under Windows 95:

• Double-click on My Computer.
• Double-click on Properties.
• Right mouse button click on the Canon Printer.
• Click on Details.
• Click the down arrow button in the window labeled "Print to the following port".
• Click on FILE (to switch back, choose LPT1).
• Click on OK at the bottom of your screen.

Hewlett Packard 4S, 4+, 4V, 4SI, 4L, 4P, and 5P: You need to disable the bi-directional communication between the printer and system. This can be accomplished by executing the following command from the RUN command line:

c:\windows\dinstall -fdinstall.ins

You can also use the procedure outlined below:

• Bring up the WIN.INI file through either SYSEDIT (in Windows) or EDIT (in DOS).
• In the first section of this file, you should see a line that reads; LOAD=HPSW.EXE. You need to disable this line by inserting a semi-colon (;) at the beginning of the line.
• Now scroll down to the section labeled [Spooler] and insert a semi-colon (;) at the beginning of the line that reads; QP.LPT1=HPLJ4QP.DLL.
• Save the WIN.INI file, exit Windows, and restart the system.

You can now use the HP printer and Zip drive together. These changes will not affect the printer - they just disable the status windows that may pop up telling the current status of the printer.

Hewlett Packard 5l: If you installed your printer using the HOST option, you will need to un-install the printer then re-install it using the PCL option. In your WIN.INI file, disable the line that reads; LOAD=HPLJSW.EXE by placing a semi-colon at the beginning of the line. You will need to do the same with the line that reads; QP.LPT1=??? in the [Spooler] section of your WIN.INI file.

Symptom 44-16. You encounter problems installing a Zip SCSI drive. In virtually all cases, SCSI problems can be traced to hardware problems or driver issues. Make sure that power is provided to the drive (see that the drive power light comes on). See that the SCSI signal cable is intact, and connected securely between the drive and SCSI adapter. Try a new signal cable. Both ends of the SCSI bus must be terminated properly. Make sure that terminators are installed in the correct places. Ensure that the Zip SCSI drive is assigned to a SCSI ID that is not in use by any other SCSI device. Finally, check the drivers - the drivers for your SCSI adapter and drive must be correct, use the right command line switches, and be the very latest versions. Also check for conflicts between SCSI drivers or other drivers in the system.

Symptom 44-17. The drive letter is lost each time the PC is turned off. In many cases, the GUEST utility does not load properly because it is at the end of AUTOEXEC.BAT. Relocate the GUEST command line - open the AUTOEXEC.BAT file and move the GUEST command line to a point earlier in the file. Ideally, the GUEST command line should be the entry immediately following the MSCDEX command line. Save your changes and reboot the computer. The GUEST utility should now load each time the system is rebooted.

Tape drives have generally come to be seen as a necessary evil in the computer industry. We all know that backups are vitally important to protect our valuable data and system setups, yet we cringe when considering the effort required to configure and execute a backup. As a result, Iomega has taken great lengths to develop a tape drive that can be set up and used as quickly and easily as possible. The result is their Ditto drive. There are several versions of the Ditto, providing 420MB, 800MB, and 2GB backups respectively. According to Iomega, the Ditto can be installed in just 5 minutes, and the Ditto software makes backup operations almost intuitive (it will even accomplish backups in the background while you work on other things).

There are two reasons why the Ditto tape drive is in this chapter (instead of Chapter 48). First, the Ditto 2GB drive requires a high-performance floppy drive interface in order to function properly. If you are using an ordinary 500KB/s floppy interface, you will need to install the Ditto Dash accelerator card. Second, the 2GB tape is a proprietary tape manufactured exclusively for Iomega. The Ditto 2GB tape cartridge uses a slightly wider tape (0.315") than the QIC-80 and QIC-40 minicartridges (note that the uncompressed capacity for Ditto 2GB tapes is only 1GB). The 2GB tape drive can read and write to the 2GB cartridge, but cannot format this cartridge, so all Ditto 2GB tapes are pre-formatted.

Symptom 44-18. The internal Ditto tape drive is not detected when running from a floppy disk controller. In most cases, the drive is not powered, or is not connected properly. Check the power connector first. Internal drives are powered by a standard 4-pin mate-n-lock type connector. Make sure that +5 and +12 volt supply levels are adequate, and see that the connector is securely attached to the drive. Next, make sure that the signal cable is attached properly to the drive, and see that the orientation of pin 1 is correct at the drive and controller. Try a new signal cable if possible.

Check the tape cartridge itself. Make sure that you have inserted a known-good tape properly into the drive. If the tape does not initialize after it is inserted, the drive may be defective. Try a new drive. Make sure that the backup software is installed and configured properly on your system. Try reinstalling the software. Finally, try the drive on another computer. If the drive works on another computer, the original floppy drive controller may be inadequate. Try the Ditto Dash accelerator card. If the drive does not work on another computer (or does not work properly with the accelerator card), the drive may be defective. Try a new drive.

Symptom 44-19. The internal Ditto drive is not detected when running from a Ditto Dash accelerator card. In most cases, the drive is not powered, or is not connected properly. Check the power connector first. Internal drives are powered by a standard 4-pin mate-n-lock type connector. Make sure that +5 and +12 volt supply levels are adequate, and see that the power connector is securely attached to the drive. Make sure that the signal cable is attached properly to the drive, and see that the orientation of pin 1 is correct at the drive and controller. Try a new signal cable.

Check the tape cartridge next, and see that you have inserted a known-good tape properly into the drive. If the tape does not initialize after it is inserted, the drive may be defective. Try a new drive. Check for hardware conflicts - the Ditto Dash accelerator board may be using an IRQ, DMA, or I/O setting in use by another device in the system. Reconfigure the accelerator card if necessary. Make sure that the backup software is installed and configured properly. Try reinstalling the software. Finally, you should be concerned with the card slot. Make sure that the Ditto Dash accelerator card is located in a slot away from modem/fax boards, or video boards. Try the accelerator in a new slot.

Symptom 44-20. You notice that the internal Ditto drive takes longer to backup than expected, and the drive regularly spins back and forth. Regular "back and forth" movement is known as shoeshining, and is usually accompanied by several corrected errors. The drive is probably running from a floppy controller, and the data transfer rate of your backup software is set too high. Check for any backup software settings that control the data transfer rate, and set the rate to 500KB/s. Save the changes and try another backup - you should see an improvement. If the PC is in its "turbo" mode, try disabling the turbo mode and try another backup. Finally, try a different drive controller such as a Tape Accelerator II card (or a Parallel Port II tape drive) to improve data transfer rates.

Symptom 44-21. The Ditto parallel port drive is not detected under DOS or Windows 3.1x. This is usually caused by interference with the parallel port. Check the power connector first - parallel port drives are powered externally. Make sure that the power pack is working, and see that the power cable is connected properly to the drive. If the drive does not appear to power up, try a different power pack or drive. Check the signal cable next, and make sure that you are using a good-quality, known-good parallel port cable which is attached securely at the PC and drive. Parallel port drives are very sensitive to devices such as copy protection modules (or "dongles"), and other "pass-through" devices. Try connecting the drive directly to the parallel port. Also disconnect any printers on the parallel port.

Reboot the PC and enter CMOS Setup. Check to see that the parallel port is configured in EPP or bi-directional mode. As a rule, do NOT set the port for ECP mode. Hardware conflicts can also present a problem. Make sure that no other device in the system is using IRQ 7 (for LPT1) or IRQ 5 (for LPT2). If your sound board is using IRQ 7 or IRQ 5, you may need to reconfigure the device. Make sure that you have inserted a known-good tape properly into the drive. If the tape does not initialize after it is inserted, the drive may be defective. Try a new drive. If problems persist, add the following two lines to AUTOEXEC.BAT:

set port_delay=20

set ppt_flags=16

Try the drive on another system. If it works on another system, the original parallel port cannot support the Ditto drive. Try adding a second parallel port to the system. If the drive does not work on another PC, the drive is probably defective and should be replaced.

Symptom 44-22. The internal Ditto drive does not find any catalogs during a restore. The tape’s "catalog" has been lost or corrupted. Use the steps below to rebuild a tape catalog with Iomega backup software:

• Choose the Restore option from the main menu.
• Choose the Catalog pull down menu, then click on Rebuild.
• A screen will appear listing all the catalogs on the tape. Choose the catalog that you wish to rebuild, then choose the OK button (in DOS) or start Rebuild (in Windows).
• The software will then rebuild the catalog and write it automatically to the hard disk. The catalog will then appear in the appropriate box to select files to restore.

Symptom 44-23. The Ditto drive encounters many corrected errors during a compare. If a tape file does not match the same file on a hard disk, the backup software logs a read error. The software then performs a series of re-reads to compare the file. If the re-reads match, the software corrects the logged error. If a full tape backup exceeds 50 corrected errors, there may be a system configuration problem.

First, the drive may be dirty. Clean the R/W tape heads and try the tape again. You can also use the backup software to retension the tape. The tape itself may also be bad. Try a known-good tape. If a known-good tape works properly, the original tape may need to be reformatted. If problems persist, try another tape.

Try booting from a "clean" diskette, then try the DOS backup software again. If the problem disappears, there may be a driver or TSR which is interfering with the Ditto drive’s operation. Check the signal connector. Try a new parallel port (or internal floppy drive) cable to connect the drive and system. Also check for local electrical interference - the parallel port drive may be positioned too close to monitors or high-power multimedia speakers. Try moving the drive away from strong magnetic sources. Internal drives may be positioned too close to CD-ROM drives or hard drives. Try relocating the internal Ditto drive to a more remote drive bay. Finally, the DMA operation of your computer may be too fast. Try slowing down DMA operation through the Iomega software.

Symptom 44-24. You see a "Fatal Exception Error" with the Ditto drive. The configuration files for the drive are set up incorrectly. You will need to correct the proper entries.

Internal Ditto Configurations. For the internal Ditto drive, you will need to edit the TAPECTRL.CFG filr located in the QBWIN directory. Delete the following lines:

DRIVER_TYPE:5,1 "PARALLEL Port Tape Drive," "qbwppqt.dll"

MANUFACTURER: "IOMEGA"

MODEL: "PARALLEL PORT TAPE DRIVE,"FFFF

DRIVER: 5

FEATURES: 0

I/O ADDRESS: 278, *378, 3bc

IRQ NUMBER: 5, *7

DMA NUMBER:

and;

MANUFACTURER: "IOMEGA"

MODEL: "PPT (MSO chip),"FFFF

DRIVER: 5

FEATURES: 0

I/O ADDRESS: 278, *378, 3bc

IRQ NUMBER: 5, *7, 10, 11, 12, 15

DMA NUMBER:

Save your changes, restart the system, then run the tape backup software again.

External Ditto Configurations. For the external Ditto drive, you will need to add the following two lines to the AUTOEXEC.BAT file:

set port_delay=20

set ppt_flags=16

Save your changes, reatart the system, then run the tape backup software again.

Symptom 44-25. The Ditto drive is not restoring selected files. The backup software is probably claiming that no files are selected - even though you have selected files. Take the following steps with Iomega backup software:

• Make sure there are marks next to the files listed.
• Select all files (go to the File command and use the Select All Files option).
• If the backup software still claims that no files are selected, go back into the Select Files option, then select the Special option and take the check mark out of the box that says Exclude Read-Only Files.
• Read only files are excluded by default. This should solve the problem.

NOTE: It is very important that you perform a "compare" after a backup. This ensures that the data on your tape is intact. If you do not compare, data integrity cannot be guaranteed (and a restore may not be possible).

Symptom 44-26. You encounter the error; "The Drive Received an Invalid Command" when using a Ditto drive. In most cases, the drive is experiencing communication problems with the controller. Change the backup software configuration. Go into the Configure menu of the Iomega backup software. Click on the Settings button, then change the Transfer Rate option to 500KB/s. Press <Alt> + <F10> and set the option Cntr Card to "bi-directional". Click on the OK button, and run another backup. If problems persist, add the following line to AUTOEXEC.BAT:

set port_delay=20

Restart the system and try another backup.

Perhaps the single most important complaint about hard drives has been that they are not portable - you can’t just slide out one drive and pop in a new one. Hard drives are traditionally permanent installations. When that drive fills up, you must physically add another hard drive, or replace the existing hard drive with a larger model. Both options require an invasive and time-consuming upgrade procedure. The idea of high-capacity removable media overcomes this limitation. With a removable media drive such as a the Iomega Bernoulli (or their current Jaz) drive, you can finally achieve limitless storage simply by exchanging data cartridges. If you need to use files on another PC, you can just pop out a cartridge, then take it with you to another PC with a Bernoulli (or Jaz) drive. Bernoulli drives are not quite as fast as hard drives, but they are close, and you can usually start programs right from the drive.

The Bernoulli disk is a variation of fixed disk technology. Conventional hard drives rotate rigid disks which force read/write heads to ride on the resulting cushion of air. By comparison, the Bernoulli disk uses a flexible platter which is forced to flex beneath a fixed read/write head. At first glance, you probably would not know the difference between a fixed-platter cartridge (such as a SyQuest cartridge), and a Bernoulli cartridge.

Bernoulli disks have been around for years, and have been through 20MB, 35MB, 44MB, 65MB, 90MB, 105MB, 150MB, and 230MB incarnations. The Iomega Bernoulli 230 drive will operate with all of the previous disk sizes (except 20MB and 44MB) with only a negligible performance hit. Bernoulli drives are traditionally SCSI devices, but Iomega offers a parallel port-to-SCSI adapter to allow operation with a PC parallel port. When used on a SCSI system, you can use the Iomega PC2x, PC4x, PC90, PC800, PC1600, and PC1616 SCSI adapters. Other SCSI adapters can also be used as long as they are ASPI-compatible, and an ASPI driver is provided by the adapter vendor.

Symptom 44-27. The Iomega Bernoulli drive has a floppy icon in Windows 95. This is usually the result of running a real-mode driver to support the Iomega drive and adapter under Windows 95. Check the Iomega driver - you may need to disable the real-mode driver and install the protected-mode driver under Windows 95. The Iomega software provides protected-mode drivers for Jaz Jet, Zip Zoom, PC1600, PC1616, PC800, PC2x, PPA-3, and parallel port devices. If you are using a different adapter, you may need to upgrade and update the driver accordingly. If you are using a non-Iomega adapter (such as a SCSI adapter), you will need protected-mode drivers from the particular SCSI vendor. However, Windows 95 does have a comprehensive library of protected-mode drivers already available.

Symptom 44-28. The Iomega Bernoulli SCSI drive does not have a drive letter in Windows 95. The drive does not appear to respond. In virtually all cases, the SCSI driver has failed to load. Check the driver first. Open the Device Manager and expand the SCSI Controllers entry, then check the Iomega Adapter line beneath it. If there is a yellow symbol with an exclamation mark on it, the Windows 95 driver did not load. Highlight that Iomega Adapter line and select Properties. Click on the Resources page, then verify that your I/O Range and IRQ options are set correctly - they must match the jumper settings on your adapter board. If you must update the resource settings manually, make sure the Automatic Settings box is not checked. Remember to save any changes. If you allocated new resources, you may have to shut off the PC and change jumper settings on the controller to match the resources allocated in the Device Manager. Restart the computer - once the system reboots, the Windows 95 driver should load normally.

If the driver checks out properly, you’ll need to check the device connections. Check the SCSI signal connector first, and make sure the SCSI cable is intact, and connected to the drive properly. If problems persist, your SCSI adapter is probably installed correctly, but the bus may be terminated improperly. See that you terminate both ends of the SCSI bus properly. Finally, make sure that the SCSI ID for your drive does not conflict with the ID of other SCSI devices in the system.

Symptom 44-29. The parallel port (or PPA-3) adapter does not have a drive letter in Windows 95. Parallel port drive problems can almost always be traced to faulty connections, port configuration issues, or driver problems. Check the power connector first. Parallel port drives are powered externally, so ensure that the power pack is working, and see that the power cable is connected properly to the drive. If the drive does not appear to power up, try a different power pack or drive. Also make sure that you are using a good-quality, known-good parallel port cable which is attached securely at the PC and drive.

Remove any other devices on the parallel port. Parallel port drives are often very sensitive to devices such as copy protection modules (or "dongles"), and other "pass-through" devices. Try connecting the drive directly to the parallel port. Also disconnect any printers on the parallel port. Reboot the PC and enter CMOS Setup. Check to see that the parallel port is configured in EPP or bi-directional mode. The controller may also be presenting a problem. There is a known incompatibility between the Iomega Bernoulli drive and the Adaptec 284x adapter - the Iomega PPA3 driver does not work with the Adaptec 284x controller. Check with Iomega for an updated SCSI driver.

Open the Device Manager and find the SCSI Controllers entry (even though it is a parallel port device). If there is no such entry, the driver is not installed. If you expand the SCSI Controllers section, there should be an entry for the Iomega Adapter. If not, the driver is not installed. If the Device Manager entry for the Iomega Adapter has a yellow circle with an exclamation mark on it, the interface is configured improperly and is conflicting with other devices in the system. Device properties may also be a problem. Highlight the Iomega Adapter entry, click on Properties, then select the Settings page. Find the box marked Adapter Settings, then type:

/mode:nibble /speed:1

Save your changes and reboot the system. You could also try reinstalling the drivers. Highlight the Iomega Adapter and select Remove. Then reinstall the drivers from scratch. Finally, consider the drive itself. Try the drive on another PC. If the drive works on another system, the parallel port is incompatible (or the PPA3 is not configured properly). If the drive does not work on another PC, try a new Bernoulli drive.

Symptom 44-30. The Bernoulli drive takes over the CD-ROM's drive letter in Windows 95. You may simply need to switch drive letters between the Bernoulli drive and CD-ROM drive:

• Open Device Manager and double-click on the Disk Drives entry.
• Highlight the Iomega Bernoulli drive entry and click on Properties.
• Click on the Settings page.
• In the Reserved Drive Letters section, there is a Start Drive Letter and an End Drive Letter setting. Enter the desired drive letter for the Bernoulli drive in both start and end drive entries (be sure to use the same drive letter for both start and end). Click on OK.
• Double-click on the CD-ROM entry.
• Highlight your CD-ROM Drive entry and click on Properties.
• Click on the Settings page.
• In the Reserved Drive Letters section, there is a Start Drive Letter and an End Drive Letter setting. Enter the desired drive letter for the CD-ROM drive in both start and end entries (be sure to use the same drive letter for both start and end). Click on OK.
• Click on OK to close Device Manager, then shut down and restart the computer.

Symptom 44-31. You encounter an "Invalid Drive Specification" error after installing an Iomega SCSI drive. Your system automatically boots into Windows, and it will not return to the installation program. The error occurs when you try to access the Iomega drive. In most cases, you need to install the Iomega SCSI software from the DOS prompt. Boot the system from a "clean" diskette, then try installing the Iomega SCSI software again.

Symptom 44-32. You encounter an "Invalid Unit Reading Drive <x>" error. Software drivers appear to load fine, and the Bernoulli drive is assigned a drive letter as expected. In virtually all cases, there is a problem with the SMARTDRV statement in AUTOEXEC.BAT. Check the drive controller BIOS first - there may be a conflict with the BIOS on your PC1616 controller card. If you are NOT booting from the PC1616, try disabling the PC1616 BIOS with the ISACFG.COM utility accompanying the PC1616 adapter (you can also obtain the utility from Iomega at www.iomega.com). Reboot the PC - the error should be corrected.

If you ARE booting from the PC1616 controller (the Bernoulli drive), leave the controller’s BIOS enabled, but try loading SMARTDRV high (i.e. into the upper memory area). If you cannot load SMARTDRV high, disable its command line in AUTOEXEC.BAT and reboot the system, then load SMARTDRV from the DOS command line once the PC initializes. If problems persist, try the new GUEST program from Iomega (make sure you’re using the latest version). Once you install the GUEST.EXE and GUEST.INI files to your PC, enter the path and command line for GUEST near the end of AUTOEXEC.BAT (before Windows starts) such as:

c:\zinstall\guest.exe

If these solutions fail to correct the error, then SMARTDRV cannot be loaded and will need to be remarked out of the AUTOEXEC.BAT file entirely.

NOTE: If you use the GUEST program, you cannot compress the disks using DISKSPACE. Also, GUEST does not support the PC80 or PC90 adapter cards.

Symptom 44-33. You encounter problems using the Iomega parallel port interface (PPA-3) with a Bernoulli drive. Problems with the PPA3 are usually related to installation issues, but drivers can also prevent the PPA3 from responding. Check the power connector first - the external device MUST be turned on before powering up the computer. If the device refuses to power up, check the power pack and its connection to the Bernoulli drive. Make sure that the signal cable is the proper length, and is connected securely to the drive and system. Unusually long cables may cause read/write errors. Try disconnecting the printer or other parallel port device from the system, and try the PPA3 as the only parallel port device attached to the parallel port. Check the drive termination next. The PPA3 board is terminated, and the last drive attached to the PPA3 cable must also be terminated. If the Bernoulli drive is the last device attached to the PPA3, make sure it is terminated properly.

Check the driver installation. You need either OAD 1.3 (and higher), or Iomega SCSI 2.0 (and higher) to use the PPA3 board. Once the drivers are installed, you should see several lines in CONFIG.SYS such as:

REM OAD 1.3 or later:

DEVICE=C:\OADDOS\ASPIPPA3.SYS /L=001

DEVICE=C:\OADDOS\DOSCFG.EXE /M1 /V /L=001

DEVICE=C:\OADDOS\DOSOAD.SYS /L=001

or;

REM Iomega SCSI 2.0 or later:

DEVICE=C:\IOMEGA\ASPIPPA3.SYS /L=001

DEVICE=C:\IOMEGA\SCSICFG.EXE /V /L=001

DEVICE=C:\IOMEGA\SCSIDRVR.SYS /L=001

Try some ASPIPPA3.SYS command line options. The ASPIPPA3.SYS driver provides several important command line options in Table 44-2 that can be employed to streamline its operation. If the ASPIPPA3.SYS command line generates any errors, you can decipher the errors with Table 44-3.

Symptom 44-34. The Iomega PPA3 locks up on installation. Chances are that the ASPIPPA3.SYS driver is causing the computer to lock up, or is causing a "Divide by zero overflow" error. Check the power connector first. The external device MUST be turned on before powering up the computer. If the device refuses to power up, check the power pack and its connection to the Bernoulli drive. Also make sure that the signal cable is the proper length, and is connected securely to the drive and system. Unusually long cables may cause read/write errors. Termination may be an issue - the PPA3 board is terminated, and the last drive attached to the PPA3 board must also be terminated. If the Bernoulli drive is the last device attached to the PPA3, make sure it is terminated properly by setting the termination switch on the back of the drive to "I". If the switch is set to "O", turn off the drive, set the switch to "I", turn the drive on, and reboot the PC. Update the ASPIPPA3.SYS driver. Try adding the /SL360=NO switch to the command line such as:

DEVICE=C:\IOMEGA\ASPIPPA3.SYS /SL360=NO

Save your changes to CONFIG.SYS and reboot the computer. Try the PPA3 board and Bernoulli drive on another PC. If they work on another system, the original parallel port is probably incompatible. If the PPA3 and drive do not work on another system, try another set of cables. If problems persist, try the Bernoulli drive directly on a SCSI adapter. If the drive works directly, the PPA3 has probably failed. If the drive does not work, it has probably failed.

Symptom 44-35. You encounter SCSI communication problems. In virtually all cases, SCSI problems can be traced to hardware problems or driver issues. Check the power connector first, and see that power is provided to the drive (the drive power light should be on). Make sure that the SCSI cable is intact, and connected securely between the drive and SCSI adapter. Try a new signal cable if possible. Termination may also be a problem. Both ends of the SCSI bus must be terminated properly. Make sure that terminators are installed in the correct places on your SCSI chain. The Bernoulli SCSI drive must be assigned to a SCSI ID that is not in use by any other SCSI device. Finally, check the drivers. Make sure that the drivers for your SCSI adapter and drive are correct, use the right command line switches, and that you are using the very latest versions. Also check for conflicts between SCSI drivers or other drivers in the system.

Symptom 44-36. Your IDE Bernoulli drive receives two drive letters. Your plug-and-play (PnP) BIOS is detecting the Bernoulli drive as a fixed drive and assign one drive letter, but the Iomega drivers detect the Bernoulli drive again - assigning a second drive letter. PnP support for the Bernoulli drive may be a problem. Enter your system CMOS Setup and disable the PnP support for the Bernoulli drive. Save your changes and reboot the system. If you cannot disable BIOS support for the Bernoulli drive, power up the system with the Bernoulli disk removed - this causes BIOS to overlook the drive, but the Iomega drivers will still assign the drive letter properly.

Symptom 44-37. Using an Iomega PC2X 8-bit Bernoulli controller may cause the system to crash. According to Iomega, their PC2X 8-bit Bernoulli controller cards may not function properly on 486/33MHz and faster computers. For Windows 95 Setup, you may need to run Setup with the "ignore hardware detection" parameter such as:

SETUP /I

To correct this problem, you’ll need to use the controller on a slower computer (rarely a practical option), or install a better Bernoulli controller card in the existing system.

Symptom 44-38. The compressed removable-media drive(s) are not automatically mounted on startup. This problem can occur under Windows 95 if the computer has two floppy disk drives and the following settings exist in the Drvspace.ini file:

MaxRemovableDrives=2

AutoMount=1

To resolve this issue, you’ll need to increase the value of the "MaxRemovableDrives=" setting to match the total number of removable-media drives in the computer. For example, if your computer has two floppy disk drives and a double Bernoulli drive, use "MaxRemovableDrives=4" (two floppy disk drives plus two Bernoulli drives). Edit the DRVSPACE.INI file as follows:

1. Locate the Drvspace.ini file using Windows Explorer (it should be in the root directory). Right-click the file, then click Properties.
1. Click the Read-only check box to clear it, then click OK.
1. Double-click the Drvspace.ini file to open it.
1. Change the value of the "MaxRemovableDrives=" setting to match the total number of removable-media drives, or set the "AutoMount=" entry to the drive letters assigned to the removable-media drives. For example, if you have a double Bernoulli drive with drive letters D and E assigned to the drive, use the setting "AutoMount=DE".
1. Save and then close the file. Reboot Windows 95.

NOTE: When you use an Iomega RCD driver with a double Bernoulli drive, you may receive a "General Failure" error message the first time you access the second drive. This causes automatic activation and automatic mounting to fail. Use an Iomega OAD or SCSI driver to resolve the problem.

Symptom 44-39. You have problems when running Iomega Jaz Tools under Windows 95. When Iomega Tools for Windows 95 is installed on your computer, the system may crash (or you may receive an error message referencing the Iomega.vxd file) when you attempt to use the Iomega Jaz Tools. This occurs especially under FAT32 partitions of OSR2. Chances are that you’re using an older version of Jaz Tools for Windows 95 (earlier than version 5.0). Earlier versions of Jaz Tools are not compatible with FAT32 (OSR2). You’ll need to uninstall the Jaz Tools package, then install version 5.0 or later which is FAT32 aware.

SyQuest is another drive manufacturer which has capitalized on the popularity for removable media drives. Rather than using the flexible disk media of Bernoulli technology, SyQuest chose to employ the rigid platter/floating head approach used by more conventional hard drives. As a result, SyQuest drives are a bit closer to being "real" hard drives than Bernoulli drives. The traditional 44MB and 88MB SyQuest drives of years past have been replaced by products such as the EZ-Drive (135MB) and EZ-Flyer (230MB) drives. SyQuest has just recently released the dual-platter 1.5GB SyJet drive which places the SyJet in direct contention with Iomega’s 1.0GB Jaz drive.

Symptom 44-40. You encounter problems with removable-media IDE drives in Windows 95. There are several potential problems; the removable drive is not detected or not accessible within Windows 95; media changes (such as removing a disk and inserting a new disk) are not detected; or the removable drive appears as a non-removable hard disk in Windows Explorer or Device Manager. This happens because removable-media IDE drives are not fully supported by the IDE drivers included with Windows 95. You’ll need to install the following patch files for Windows 95: Esdi_506.pdr (version 4.00.1116 dated 8/25/97 or later), and Voltrack.vxd version 4.00.954 dated 3/6/96 or later. Both of these files are available in the REMIDEUP.EXE file available from the Microsoft Software Library (www.microsoft.com). Once downloaded, find the file in Windows Explorer and double-click on it, then follow the on-screen instructions. The new files will be patched to the Windows\System\Iosubsys directory.

NOTE: The Voltrack.vxd file is installed on Windows 95a computers only - this file is not installed on computers running OSR2.

Symptom 44-41. You encounter problems with SyQuest drives and Future Domain SCSI adapters. Although SyQuest drives should perform properly with Future Domain SCSI adapters, there are some issues that might cause problems. Inspect the SCSI ID first. Future Domain SCSI adapters install drives from the higher SCSI ID (6) to the lowest (0) - this is opposite from the majority of HBA manufacturers which assign drives from ID 0. Make sure any hard disk drives have a higher SCSI ID number than the SyQuest drives when you install a removable drive on the SCSI bus. That way, the hard drives will be assigned the lower DOS drive letter (i.e. C: then D:).

Future Domain controllers will not allow the SyQuest drive to serve as a boot device. If you must make the SyQuest drive bootable, contact Future Domain for a firmware upgrade. Cartridge preparation can also be a problem. Future Domain PowerSCSI software works with cartridges prepared and used on the same PC. When exchanging the cartridge with one of a different format, size, or partition, the PowerSCSI driver will not handle the new cartridge properly. You might need different SCSI drivers. Check your SCSI drivers. In order for the SyQuest utilities to work properly with Future Domain adapters (and handle non-native cartridges), the CONFIG.SYS file must contain the following drivers:

DEVICE=C:\PWRSCSI!\DCAM18XX.EXE

DEVICE=C:\PWRSCSI!\ASPIFCAM.SYS

DEVICE=C:\SYQUEST\SCSI\SQDRIVER.SYS

The correct CAM.EXE driver for your particular adapter must be used in the CONFIG.SYS file (such as CAM950.EXE). Do not use FDBIOS.SYS or INT4BCAM.SYS with SQDRIVER.SYS (only one driver can be used to control the SyQuest drive). The SyQuest DOS formatting program SQPREP will partition and Format DOS cartridges with Future Domain adapters if the drivers are correctly installed in CONFIG.SYS as shown above.

Symptom 44-42. You encounter problems with SyQuest drives and NCR SCSI adapters. SyQuest drives work well with NCR (now part of AT&T Global Systems) adapters, but you must be using version 3.12 or later SyQuest utilities. The SCSI drivers may be causing problems. To make the SyQuest cartridges removable under DOS, the following three entries must be present in CONFIG.SYS:

DEVICE=C:\SDMS\DOSCAM.SYS (10-08-93 or later)

DEVICE=C:\SDMS\ASPICAM.SYS (10-08-93 or later)

DEVICE=C:\SyQuest\SCSI\SQDRIVER.SYS

If you choose to use the NCR driver SCSIDISK.SYS instead of SQDRIVER.SYS, the ability to remove cartridges and use non-native cartridges will be lost. Make sure that both drivers are NOT loaded together, or data corruption will result. Also suspect an issue with the SCSI ID. Typical NCR SCSI priority is from lowest (0) to highest (6), and the NCR adapter is SCSI ID 7. The SyQuest DOS partition and format utility (SQPREP) works well with NCR adapters as long as the drivers are loaded in CONFIG.SYS as shown above.

Symptom 44-43. You encounter problems with SyQuest drives and Rancho Technology SCSI adapters. SyQuest SCSI drives work properly with Rancho Technology SCSI adapters, but there are some issues that you must be aware of. First, Rancho Technology SCSI BIOS requires that a cartridge be installed in the SyQuest drive at boot time (the Rancho Technology BIOS will hang if no cartridge is installed and the drive is ready). SCSI drivers can also be an issue. SyQuest utilities will work through the ASPICAM driver supplied with Rancho Technology adapters. To make the cartridges removable under DOS, the CONFIG.SYS file must have drivers loaded in this order:

REM For the Rancho Technology 1600:

DEVICE=C:\RT1600\DOSCAM.SYS (12-14-94 or later)

DEVICE=C:\RT1600\ASPICAM.SYS (12-14-94 or later)

DEVICE=C:\SyQuest\SCSI\SQDRIVER.SYS

or;

REM For the Rancho Technology 1000:

DEVICE=C:\RT1000\RTASPI10.SYS (01-26-93 or later)

DEVICE=C:\SyQuest\SCSI\SQDRIVER.SYS

If you choose to use the Rancho Technology driver SCSIDISK.SYS instead of SQDRIVER.SYS, the ability to remove cartridges and use non-native cartridges will be lost. Make sure that both drivers are NOT loaded together, or data corruption will result. Check the SCSI ID - typical Rancho Technology SCSI priority is from lowest (0) to highest (6), and the Rancho Technology adapter is SCSI ID 7. The SyQuest DOS partition and format utility (SQPREP) works well with Rancho Technology adapters as long as the drivers are loaded in CONFIG.SYS as shown above.

Symptom 44-44. You encounter problems with Packard-Bell multimedia PCs and SyQuest drives. Packard Bell systems often use unusual IRQ assignments which may interfere with the default settings of many SCSI adapters. Check the hardware settings - many Packard Bell PCs use IRQ 11 and IRQ 12 for the CD-ROM drive, sound board, and mouse. When installing a SCSI adapter, make sure to use IRQ 10 and the I/O address of 340h. If there is any other 16-bit card (especially a network card) in the system, use IRQ 15 instead.

Symptom 44-45. You encounter problems using BusLogic SCSI adapters and SyQuest drives. The BusLogic ASPI driver (BTDOSM.SYS) will operate with the SyQuest device driver SQDRIVER.SYS, but the order of installation can be very important. Install the BusLogic driver first, then install the SyQuest software. Once the drivers are installed, the CONFIG.SYS file should be in this order:

DEVICE=C:\BUSLOGIC\BTDOSM.SYS /D

DEVICE=C:\SYQUEST\SCSI\SQDRIVER.SYS

Remove the BusLogic disk driver BTMDISK.SYS:

REM DEVICE=C:\BUSLOGIC\BTMDISK.SYS

Relocate any other Buslogic device drivers after SQDRIVER.SYS. Reboot the system after making any changes to CONFIG.SYS. Finally, check the driver dates. Make sure that you are using SQDRIVER.SYS version 7.72 or higher, or the SyQuest software release 3.12 or higher (01-27-95 or later).

Symptom 44-46. You encounter problems using Qlogic SCSI adapters and SyQuest drives. While SyQuest SCSI drives will operate properly with Qlogic SCSI adapters, there are some issues that can cause problems. First, Qlogic FastSCSI software does not support SyQuest cartridge exchange without installing the SyQuest SQDRIVER.SYS driver. Install the two Qlogic drivers, then install the SyQuest drivers. Make sure that the QL00DISK.SYS driver is NOT installed in CONFIG.SYS. A typical CONFIG.SYS file will appear such as:

DEVICE=C:\QLOGIC\QL41DOS.SYS

DEVICE=C:\QLOGIC\QL00ASPI.SYS

DEVICE=C:\SyQuest\SCSI\SQDRIVER.SYS

Make sure to use the correct QLxxDOS.SYS driver for your particular Qlogic SCSI adapter. CorelSCSI software is often shipped with Qlogic SCSI adapters. If a CorelSCSI driver is installed to support a SyQuest drive, do NOT install the SQDRIVER.SYS driver. Finally, disable or REMark out the QL00DISK.SYS driver if it is entered in the CONFIG.SYS file. If the QL00DISK.SYS driver is allowed to coexist with SQDRIVER.SYS, data corruption will result.

Symptom 44-47. You encounter problems using an IBM MicroChannel SCSI controller and SyQuest drive. This note applies to the /A and /2A MicroChannel SCSI adapters. The IBM ASPI driver (ASPI4B.SYS) will only operate with the SyQuest driver SQDRIVER.SYS under DOS - not under Windows. The MSDRVR.ZIP shareware has been known to circumvent this incompatibility. For current pricing and availability, contact the shareware maker:

Micro Staff Co., Ltd.

1-46-9 Matsubara, Setagaya-ku, Tokyo, Japan 156

Tel: 011-81-3-3325-8128

Fax: 011-81-3-3327-7037

CompuServe ID: 100157,1053

Symptom 44-48. You encounter problems using Data Technology Corporation (DTC) SCSI adapters and SyQuest drives. The DTC SCSI adapters will operate with SyQuest drives, but there are several points that can cause problems. Install the DTC ASPI driver first, then install the SyQuest utility software. Once all the drivers are installed, the CONFIG.SYS file should appear in this order:

REM For the DTC 3280AS ISA version and the DTC 3290AS EISA version:

DEVICE=C:\DTC\ASPI3xxx.SYS

DEVICE=C:\SYQUEST\SCSI\SQDRIVER.SYS

Remember to remove the DTC device driver ASCSI.SYS in the CONFIG.SYS file:

REM DEVICE=C:\DTC\ASCSI.SYS

Also, in the AUTOEXEC.BAT file:

REM C:\DTC\ASCSI.EXE

Load any other DTC device drivers after SQDRIVER.SYS, or:

REM For the DTC 3130 PCI version:

DEVICE=C:\DTC\DOSCAM.SYS

DEVICE=C:\DTC\ASPICAM.SYS

DEVICE=C:\SYQUEST\SCSI\SQDRIVER.SYS

Remember to remove the DTC device driver SCSIDISK.SYS in the CONFIG.SYS file:

REM DEVICE=C:\DTC\SCSIDISK.SYS

Load any other DTC device drivers after SQDRIVER.SYS. Remember to reboot the PC after making any changes to your CONFIG.SYS or AUTOEXEC.BAT files. Finally, check the driver dates. Make sure that you are using SQDRIVER.SYS version 7.72 or higher, or the SyQuest software release 3.12 or higher (01-27-95 or later).

Symptom 44-49. The lights on the SyQuest drive are blinking in a regular pattern. The drive has suffered a fault, and generally must be replaced. Use Table 44-4 to find the specific error code. In most cases, you will have to replace the drive outright.

This concludes the material for Chapter 44. Be sure to review the glossary and chapter questions on the accompanying CD. If you have access to the Internet, take a look at some of the various removable media drive makers listed below:

Iomega: http://www.iomega.com

SyQuest: http://www.syquest.com