Hi,

OK, I'm a newbie who gave it the ol' college try and I think I'm close, but...

I'm trying to configure Mandrake Linux 9.0 to use an internal Zip 100 drive.

The instructions from Iomega say...

insmod aha152x (did this, worked)
insmod fat (did this, worked)
insmod vfat (did this, worked)

Add to fstab...

/dev/sda4 /mnt/zip100.0 vfat noauto,user 0 0

(OK, but I have no /dev/sda4 - what do I put here!?)

mkdir /mnt/zip100.0 (OK, no problem here)

... and to mount the disk,

mount -f vfat /dev/sda4 /mnt/zip100.0


There's that pesky /dev/sda4 again.

Any help appreciated!!!

Much thanks in advance,
Marlo

depends on how it's attached to your machine, if it hooked to an ide channel, it should be /mnt/hdx4 replace the x with the letter a,b,c,or d depending on if its primary master (a), primary slave(b), secondary master(c),secondary slave(d). the quickest way is to reboot mandrake with it attached, mandrake will set it up for you.

The Iomega instructions might be a little outdated.

What kind of Zip drive do you have? IDE, SCSI, USB or parallel port?

I doubt you have a SCSI drive and you don't have an ISA Adaptec SCSI controller. So the aha152x didn't do anything.

If its USB I would of thought that all you would have to do is plug it in and go.

Speaking as an owner of both internal and parallel Zip 100 drives:

Linux always identifies Zip drives (both parallel and ide) as SCSI devices, even though they are not; hence, /dev/sda*. As far as I know, this is always the case with all distros; Zip support is built into the modern (2.2.x and above) kernels; google 'linux iomega zip' to confirm.

Parallel Zip drives are always /dev/sda4. The internal IDE Zip drive is probably /dev/sda1 (at least it is for mine on Knoppix 3.2).

"Linux always identifies Zip drives (both parallel and ide) as SCSI devices"

um, no it doesn't. the atapi/eide version is recognised as a normal hard drive, with an hdX label. and the 4 in hdx4/sdx4 has to do with the file system on the disk. if the disks are still formated vfat, they are always a '4' even though they contain only one partition. if you've made a ext2fs on the disk then they are mounted as sdx1/hdx1.

how can i configure my parallel zip drive?
i have been working on it for about half year and nothing came out.
Under my experience, normally when u plag some kind of device on your pc red hat linux should recognize something was plagged. But after i had connect my parallel zip 100 to my pc. I use 'dmesg' to see what's going on, but nothing.
What's the problem?
Do i need to changed the kernel? as some kind of other sitting?

Tricky, you might find this helpful...
http://www.tldp.org/HOWTO/ZIP-Drive.html

thanks for your reply, but could u explain it more specific or can u just link a file for me or state those major steps for me to configure my paralled zip drive correctly.
Also, where is that software which was stated in that page, the one you had linked to.
I am trying to go to David Campbell's page for more infor or guessing that the software which could be found over there. But unfortunately, i couldn't get there. my netscape said something about 404 error.
Why?


thanks

Thanks Grant,

That's exactly what I was looking for- I'll play with that HowTo doc and that should be enough... somehow this thread got changed into some stuff about an external parallel zip drive- mine is definitely the internal SCSI. But it looks like the HowTo covers everything.

Thanks again to all the posters... lots of good tips.

Marlo

rshaw, thanks for the correction. You are absolutely right. dmesg says that the internal ide zip drive is /dev/hdb (ie. slave drive on first ide channel).

The bootloader (lilo.conf) enables ide-scsi emulation through the append="hdb=ide-scsi" line. Therefore, after booting, the zip drive is accessible through /dev/sda1.