Jump to content

PPAOS2.ADD: Difference between revisions

From EDM2
Ak120 (talk | contribs)
mNo edit summary
Ak120 (talk | contribs)
mNo edit summary
 
Line 1: Line 1:
Parallel Port-attached ZIP 100, ZIP+, and ZIP 250 driver
Parallel Port-attached ZIP 100, ZIP+, and ZIP 250 driver


This driver supports daisy chaining, up to a total of five drives. The connections must be CPU -> ZIP Plus/250 -> ZIP Plus/250-> ZIP (original), which MUST be last. Note that ZIP Plus terminator MUST BE OFF unless it is the LAST drive in the chain. If a ZIP (original) is the last drive, then the ZIP Plus termintor MUST BE OFF.
This driver supports daisy-chaining, up to a total of five drives. The connections must be CPU ZIP Plus/250 ZIP Plus/250 ZIP (original), which MUST be last. Note that ZIP Plus terminator MUST BE OFF unless it is the LAST drive in the chain. If a ZIP (original) is the last drive, then the ZIP Plus terminator MUST BE OFF.
  BASEDEV=PPAOS2.ADD
  BASEDEV=PPAOS2.ADD


Line 14: Line 14:


==Limitations==
==Limitations==
OS/2 versions that use LVM for managing hard file space exhibit several pecularities working with ZIP drives.
OS/2 versions that use LVM for managing hard file space exhibit several peculiarities working with ZIP drives.


# Even though media is inserted at boot time, a drive letter may not be assigned. To force the assignment of a driver letter, double click on the "Refresh Removable Media" object. If that fails, eject the media, re-insert, and double click on the "Refresh Removable Media" object.
# Even though media is inserted at boot time, a drive letter may not be assigned. To force the assignment of a driver letter, double-click on the "Refresh Removable Media" object. If that fails, eject the media, re-insert, and double-click on the "Refresh Removable Media" object.
# LVM may report the ZIP drive as corrupted. You can still create a volume.
# LVM may report the ZIP drive as corrupted. You can still create a volume.
# Do NOT do an LVM "Commit Changes" with ZIP media that already contains data inserted. The data may be lost.
# Do NOT do an LVM "Commit Changes" with ZIP media that already contains data inserted. The data may be lost.

Latest revision as of 03:43, 6 November 2022

Parallel Port-attached ZIP 100, ZIP+, and ZIP 250 driver

This driver supports daisy-chaining, up to a total of five drives. The connections must be CPU → ZIP Plus/250 → ZIP Plus/250 → ZIP (original), which MUST be last. Note that ZIP Plus terminator MUST BE OFF unless it is the LAST drive in the chain. If a ZIP (original) is the last drive, then the ZIP Plus terminator MUST BE OFF.

BASEDEV=PPAOS2.ADD

Parameters

  • /V Verbose Output
  • /PORT:# # = Parallel port address (i.e. 378, 278, 3bc)

MULTIPLE PARALLEL PORT DRIVES Each driver instance supports ONLY one parallel port. To install TWO instances, you MUST specify the /PORT: parameter on at least one driver statement to get to the LPT2 port; for example:

basedev=ppaos2.add /port:378
basedev=ppaos2.add /port:278

Limitations

OS/2 versions that use LVM for managing hard file space exhibit several peculiarities working with ZIP drives.

  1. Even though media is inserted at boot time, a drive letter may not be assigned. To force the assignment of a driver letter, double-click on the "Refresh Removable Media" object. If that fails, eject the media, re-insert, and double-click on the "Refresh Removable Media" object.
  2. LVM may report the ZIP drive as corrupted. You can still create a volume.
  3. Do NOT do an LVM "Commit Changes" with ZIP media that already contains data inserted. The data may be lost.
Product Support
OS/2 1.3
OS/2 2.0
OS/2 2.1
OS/2 2.11 SMP
OS/2 Warp 3 C
OS/2 Warp Connect C
OS/2 Warp 4 C
OS/2 Warp Server for e-Business S