How to Mount SyQuest or Zip Drives in MS-DOS 6.22

Mounting removable media such as SyQuest cartridges or Iomega Zip disks in MS-DOS 6.22 requires loading dedicated device drivers to interface with the drive hardware, as the operating system lacks native plug-and-play support for removable storage. The process involves identifying the drive interface—typically parallel port, SCSI, or IDE/ATAPI—and configuring CONFIG.SYS to load the appropriate host adapter and block device drivers during boot, or executing a dynamic mounting utility from the command line to assign a drive letter.

The Underlying Driver Architecture

MS-DOS interacts with block devices through character and block device drivers. Because removable drives rely on varying bus interfaces, MS-DOS 6.22 requires a two-tiered driver model to access them:

  1. Host Adapter Layer: A low-level driver communicating directly with the hardware interface (such as an Advanced SCSI Programming Interface, or ASPI, driver for SCSI cards, or a proprietary parallel port communication driver).
  2. Device Target Layer: A driver that interprets the storage commands for the specific drive mechanism and presents it to MS-DOS as a logical disk drive.

Once both layers are initialized, DOS queries the drive, determines its partition and file system structure (which must be FAT16 for DOS 6.22), and assigns the next sequential drive letter.

Mounting Iomega Zip Drives

Iomega Zip drives, most commonly found in parallel port or SCSI variations, can be mounted through two methods: permanent installation via CONFIG.SYS or temporary mounting via command-line utilities.

Dynamic Mounting with GUEST.EXE

The most common and flexible method uses Iomega’s GUEST.EXE utility. When run from the command prompt or a batch file, GUEST.EXE:

  • Scans the parallel, SCSI, and ATAPI ports for attached Zip drives.
  • Loads resident drivers into memory on the fly.
  • Mounts the disk and automatically assigns the next available DOS drive letter without requiring a system reboot.

Static Mounting via CONFIG.SYS

For a permanent configuration, drivers must be added to the CONFIG.SYS file. For a parallel port Zip drive, the configuration requires the parallel-to-SCSI interface driver followed by the ASPI disk driver:

DEVICE=C:\IOMEGA\ASPIPPM1.SYS
DEVICE=C:\IOMEGA\ASPIFAT.SYS

For SCSI Zip drives, replace the parallel port driver with the ASPI driver specific to the installed SCSI controller card, followed by ASPIFAT.SYS or SCSIDISK.SYS.

Mounting SyQuest Drives

SyQuest removable cartridge drives predominantly use SCSI or IDE/ATAPI interfaces.

SCSI SyQuest Drives

To mount a SCSI-based SyQuest drive, the host SCSI controller's ASPI manager must load first, followed by a generic ASPI disk driver or SyQuest's proprietary disk manager. In CONFIG.SYS, add:

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

(Note: ASPI4DOS.SYS represents the SCSI host adapter driver, which varies by controller manufacturer, such as Adaptec, BusLogic, or Future Domain).

IDE/ATAPI SyQuest Drives

For later ATAPI models (such as the SyQuest EZ135 or SparQ), an ATAPI device driver such as SQATAPI.SYS must be loaded directly in CONFIG.SYS:

DEVICE=C:\SYQUEST\SQATAPI.SYS /D:SYQ01

Drive Letter Allocation and LASTDRIVE

By default, MS-DOS 6.22 only allocates drive letters up to drive E:. If the computer already has multiple hard drive partitions or CD-ROM drives, the removable drive may fail to mount due to a lack of available drive letters.

To resolve this, ensure the LASTDRIVE directive in CONFIG.SYS provides enough headroom for new letters:

LASTDRIVE=Z

Once the configuration files are saved and the system is rebooted (or GUEST.EXE is executed), the removable drive functions identically to a standard hard disk, accessible via standard DOS commands like DIR, COPY, and CHKDSK.