#ADAPTEC SLIMSCSI 1460A DRIVER DRIVERS#
Take at least two reboots with the ZIP drivers disabled to restore the original drive letter order. Not boot Warp4 unless the ZIP was connected or it would crash everytime when loading the RAM drive. I tricked Warp 4 (Warp 3 was never a problem) into accepting a RAM disk and the ZIP 100 even if theĭrive letters pushed the CD drive letter ahead by one letter. Aīinary comparison of the two drivers shows some differences in code but not the total byte count. VDISK.SYS inoperable on Warp 4 although it worked fine on Warp 3, if an external drive was present. I think, but can't prove, that they changed either the driver or the kernel to make Trust the dumb users to avoid loading drivers in an order that would lock them out of their computers and create work for IBM
The RAM disk would reassign the driver letter of the boot disk and discouraged its use. After reading the "help vdisk" and other IBM data on the driver, IBM had grave concerns that HDs and the ZIP 100 drive combination was Trying to load a RAM disk on the same Warp 4 with two VDISK.SYS does not appear to have been rewritten between 19 as the byte count is the same, but Of the CONFIG.SYS (assuming Card Services was already installed). They spent 2 pages walking the user through a driver installation that involved a 2 line edit
The biggest problem as Adaptec does not use the same numbering for its AHS152x.ADD driver with a 1460A P133 laptop with a SlimSCSIĬonnected to a SCSI Iomega ZIP 100 - talk about obsolete hardware! The driver extant in the CONFIG.SYS was
#ADAPTEC SLIMSCSI 1460A DRIVER INSTALL#
I just spent 2 days messing with a Warp 4 partial install on a 1995 VOICE Newsletter 03/2005 - Ram driving and Zipping-around-the-SCSI-Drive - File transfers with old hardwareįeature driving and Zipping-around-the-SCSI-Driveįile transfers with old hardware By George W.
0 kommentar(er)
