I’ve been using succesfully parallel Iomega ZIP Drive for several years. Now
I installed internal EIDE Nec ZIP drive and I dont understand what’s going on.
The drive shows up as /dev/fd0 and works with DOS formated disks (Fatfsys).
It works also with disks dinit’ed (as raw) in it but then such disks shows as
empty when put in the parallel ZIP drive. When I try to mount disk dinit’ed in
parallel ZIP drive I’m getting corrupted file system detected in EIDE drive.
To have more fun, when the disk is partitioned (77) and dinit’ed in parallel
drive I can read such disk (well, at least directory tree) in EIDE drive but I
have to mount it as raw !!!
Anybody has a clue?
Regards,
Greg Wrobel
–
wrobel@no-spam.zdania.com.pl Experimental Department of Scientific
phone: (+48 12) 617-2883 Equipment and Automation
fax: (+48 12) 634-2205 30-059 Krakow, al.Mickiewicza 30, Poland
Previously, Grzegorz Wrobel wrote in qdn.public.qnx4:
I’ve been using succesfully parallel Iomega ZIP Drive for several years. Now
I installed internal EIDE Nec ZIP drive and I dont understand what’s going on.
The drive shows up as /dev/fd0 and works with DOS formated disks (Fatfsys).
It works also with disks dinit’ed (as raw) in it but then such disks shows as
empty when put in the parallel ZIP drive. When I try to mount disk dinit’ed in
parallel ZIP drive I’m getting corrupted file system detected in EIDE drive.
To have more fun, when the disk is partitioned (77) and dinit’ed in parallel
drive I can read such disk (well, at least directory tree) in EIDE drive but I
have to mount it as raw !!!
Anybody has a clue?
One thing that has bitten us:
when you use the ZIP drive as slave with certain CD drives as master the first
cylinder of the ZIP won’t show up. According to the Iomega web site this is
a problem of the CD drive.
Regards,
Greg Wrobel
–
wrobel@no-spam.zdania.com.pl > Experimental Department of Scientific
phone: (+48 12) 617-2883 Equipment and Automation
fax: (+48 12) 634-2205 30-059 Krakow, al.Mickiewicza 30, Poland
Unhelpfully we have also had problems of compatibility between disks created
using early IDE Zip drives (which were compatible with parallel port drives)
and those created with the more recent drives which have link options to be
set as a floppy or not a floppy (both Iomega and NEC). In both cases the
disks can be used by drives of their own type but show the symptoms you
describe when used on the other type.
This is a real problem to us as we only have two of the “old” style Zip
drives left which we have to move between systems. The drive in our
commissioning portable (Dell Inspiron 7000) creates disks that only appear
to be readable on old style and parallel port drives.
None of our systems have CDs fitted.
Steve
This seems quite curious. As far as I know, all Zip disks are created
equal. The only difference that I can image between Zip drives might
be an offset problem. I would try SPATCH on the same disk on the
two types of drives.
Mitchell Schoenbrun --------- maschoen@pobox.com
Mitchell Schoenbrun wrote:
This seems quite curious. As far as I know, all Zip disks are created
equal. The only difference that I can image between Zip drives might
be an offset problem. I would try SPATCH on the same disk on the
two types of drives.
Yes this is curious. Especially because I can exchange DOS formatted ZIP’s
between internal and external ZIP drives with no problem. So it seems that
Fatfsys works well with both Fsys.eide and your Fsys.mbaiom which means to me
that both drivers uses the same geometry and offsets. Which also means to me
that it is not hardware incompatibility! And I don’t understand where the
problem occures.
Grzegorz Wrobel
wrobel@no-spam.zdania.com.pl
I have progressed slightly in solving my incompatibility problems, I hope
this helps
Having found the QNX “How To” Setting up a Zip Drive I thought all would be
well, however
Assuming I have a Dos formatted Zip disk,
If I simply “mount /dev/fd0 /zip” I get the corrupted file system message
If I then “dinit -h /dev/fd0” and say yes to the raw disk question I can
subsequently “mount /dev/fd0 /zip” and the disk can be used as a native
device
These disks can be accessed on parallel port drives and the older Iomega/NEC
drives but not the new ones.
Looking at the disk with fdisk I find that after the dos format there is one
type 6 partition but after dinit there are four partitions, types 88,194,63
and 117
all marked as nonQNX ? Attempting to mount any of those partitions I.e.
“mount /dev/fd0t88 /zip” etc resulted in failure such as lock up of that
terminal. “mount -p /dev/fd0” reported that it could not mount partition 63
on /dev/fd0 ???
Going back to a Dos formatted disk
If I “mount -p /dev/fd0” I get the /dev/fd0t6 added to the device directory
If I now “mount /dev/fd0t6 /zip” as suggested in the QNX How to I get the
corrupted file system message
If I “Dosfsys2 -R -L /dos/z=/dev/fd0t6” the disk becomes available as /dos/z
(Dosfsys can be used)
Disks mounted in this fashion work with new and old style drives (I have not
tried it on a parallel port drive)
This really only leaves me unable to use the native form on old and new
drives
Steve
Previously, Stephen F Terrell wrote in qdn.public.qnx4:
I have progressed slightly in solving my incompatibility problems, I hope
this helps
Having found the QNX “How To” Setting up a Zip Drive I thought all would be
well, however
Assuming I have a Dos formatted Zip disk,
If I simply “mount /dev/fd0 /zip” I get the corrupted file system message
If I then “dinit -h /dev/fd0” and say yes to the raw disk question I can
subsequently “mount /dev/fd0 /zip” and the disk can be used as a native
device
These disks can be accessed on parallel port drives and the older Iomega/NEC
drives but not the new ones.
Looking at the disk with fdisk I find that after the dos format there is one
type 6 partition but after dinit there are four partitions, types 88,194,63
and 117
all marked as nonQNX ? Attempting to mount any of those partitions I.e.
“mount /dev/fd0t88 /zip” etc resulted in failure such as lock up of that
terminal. “mount -p /dev/fd0” reported that it could not mount partition 63
on /dev/fd0 ???
that is expected because you have written the QNX4 filesytem on the raw disk over the
partition table.
Going back to a Dos formatted disk
If I “mount -p /dev/fd0” I get the /dev/fd0t6 added to the device directory
If I now “mount /dev/fd0t6 /zip” as suggested in the QNX How to I get the
corrupted file system message
If I “Dosfsys2 -R -L /dos/z=/dev/fd0t6” the disk becomes available as /dos/z
(Dosfsys can be used)
Disks mounted in this fashion work with new and old style drives (I have not
tried it on a parallel port drive)
This really only leaves me unable to use the native form on old and new
drives
Steve
you can use fdisk on the /dev/fd0 and change the partition type from 6 to 77.
you then do:
umount /dev/fd0
mount -p /dev/fd0
dinit -h /dev/fd0t77
mount /dev/fd0t77 /zip