Полигон-2

[q]

А откуда у четырёхголового винта

[/q]

[q]

сам аппарат 2001 года, когда уже на сцене был UDMA2

[/q]

[q]

работать не будет!!!

[/q]

[q]

Извини,

[/q]

[q]

ё-моё! чо он слово "g u e s t" в звёздочки переводит?

[/q]

[q]

Michael Bauer observes that the behaviour of an ATAPI2 ZIP drive does not only depend on the jumper, but also on the BIOS.

I just bought a new computer with Asus P3B-F motherboard and an ATAPI2 ZIP 100MB drive as secondary slave (/dev/hdd). Although the "A" jumper was NOT set, the partition tables of my ZIP disks could not be read and the disks had to be mounted as /dev/hdd instead of /dev/hdd4. But when I changed the BIOS setting for the secondary slave from "Auto" to "None" (which, of course, implies that the drive will not be listed by the BIOS at bootup and that it cannot be booted from), the ZIP drive no longer identifies itself to Linux as "hdd: IOMEGA ZIP 100 ATAPI Floppy", but just "hdd: IOMEGA ZIP 100 ATAPI", and access to the partition table works just fine!

[/q]

[q]

The geometry of a SCSI drive for 100MB disks is reported (on Solaris) as 96/64/32 (on an Adaptec controller), 1024/4/48 (on an NCR controller); both geometries yield 196608 sectors. The geometry of an IOMEGA ZIP 100 ATAPI FLOPPY drive is reported as 96/64/32. These geometries correspond to 196608*512=100663296 bytes. As mentioned above, when jumpered appropriately the disk only reports 100646912 bytes. In such a case 16 KiB is inaccessible. Of course one should not use fdisk on such a disk, but if one does the geometry must be 95/64/32 or so.

[/q]

[q]

Какой привод Iomega Zip 100 работает стабильнее: с USB или LPT-интерфейсом?

[/q]