On Sun, 2006-01-15 at 19:26 +0000, Kevanf1 wrote:

On 15/01/06, Carl Hartung wrote:

...

On Saturday 14 January 2006 19:42, Kelly J. Morris wrote:

...

internal Iomega Zip 250

Maybe this link might be of some help? - Carl

http://marc.theaimsgroup.com/?l=suse-linux-e&m=110236103022668&w=2

Have you tried either accessing it or setting it up with a disk actually in the drive? It sometimes helps in these cases.

Good idea. I did this and then ran "hardware Information" in YaST. It picks up the Zip 250 Atapi under the category of "Floppy Disk" > dev_names > /dev/hdf . But I don't know what to do next in order to be able to use it. Thanks. Kelly -- Kelly J. Morris

On 16/01/06, Alfredo Cole wrote:

I think (as root)

modprobe imm

should do it.

Regards.

--

This is the procedure for a parallel drive: Open up the /etc/modules file in your favourite text editor - I used Kate in Kubuntu - while logged in as either su or root. I've set up my system to log into root which is not default in Ubuntu/Kubuntu. for an Iomega 250 parallel drive add the line: imm for an older Iomega 100 parallel drive you will need to add the line: ppa save and close the file. You may need to enter your BIOS configuration and set the parallel port properties to SPP At this stage you need to create a mount point in order for Ubuntu/Kubuntu to know where to mount your Zip drive In a terminal (again as su or root) enter mkdir /mnt/zip100.0 (for a Zip 100 drive) or mkdir /mnt/zip250.0 (for a Zip 250 drive). Now, in your favourite text editor again, enter the following line for a Zip 100: /dev/sda4 /mnt/zip100.0 vfat noauto,user 0 0 or for a Zip 250: /dev/sda4 /mnt/zip250.0 vfat noauto,user 0 0 Obviously you will notice that this was written with Ubuntu/Kubuntu in mind :-) I wrote it after getting frustrated with the lack of documentation for this procedure on that site. I don't know whether it will be of any use with an internal drive though. -- ============================================== I am only human, please forgive me if I make a mistake it is not deliberate. ============================================== Xmas may be over but, PLEASE DON'T drink and drive you'll make it to the next one that way. Kevan Farmer Linux user #373362 Cheslyn Hay Staffordshire WS6 7HR

On Mon, 2006-01-16 at 17:47 +0000, Kevanf1 wrote:

On 16/01/06, Kelly J. Morris wrote:

...

On Sun, 2006-01-15 at 19:26 +0000, Kevanf1 wrote:

...

On 15/01/06, Carl Hartung wrote:

...

On Saturday 14 January 2006 19:42, Kelly J. Morris wrote:

...

internal Iomega Zip 250

Maybe this link might be of some help? - Carl

http://marc.theaimsgroup.com/?l=suse-linux-e&m=110236103022668&w=2

Have you tried either accessing it or setting it up with a disk actually in the drive? It sometimes helps in these cases.

Good idea. I did this and then ran "hardware Information" in YaST. It picks up the Zip 250 Atapi under the category of "Floppy Disk" > dev_names > /dev/hdf .

But I don't know what to do next in order to be able to use it.

Thanks. Kelly

-- Kelly J. Morris

Ok we've got somewhere anyway :-) I'm just wondering then if there is an entry in fstab for the drive? I can't access my SuSE PC at the moment so I'm flying blind here. Is it possible to do a refresh in YaST to scan for new hardware with the disk in the drive? Hopefully this would set up an entry for the drive.

Unfortunately, scanning/refreshing finds the Zip drive, but doesn't mount it. I don't know how to edit the fstab to add the Zip drive (/dev/hdf) to it. Below is the text of the fstab (my system is a dual boot with WinXP Home SP2): /dev/hdb3 / reiserfs acl,user_xattr 1 1 /dev/hda1 /windows/C ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0 /dev/hdb1 /windows/D vfat users,gid=users,umask=0002,iocharset=utf8 0 0 /dev/sda1 /windows/E vfat users,gid=users,umask=0002,iocharset=utf8 0 0 /dev/hda5 /windows/F vfat users,gid=users,umask=0002,iocharset=utf8 0 0 /dev/hda6 /windows/G ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0 /dev/hda7 /windows/H ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0 /dev/hdb2 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 /dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/dvdrecorder /media/dvdrecorder subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppy subfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0 Kelly -- Kelly J. Morris

On Mon, 2006-01-16 at 20:54 +0000, Kevanf1 wrote:

On 16/01/06, Kelly J. Morris wrote:

...

Unfortunately, scanning/refreshing finds the Zip drive, but doesn't mount it.

I don't know how to edit the fstab to add the Zip drive (/dev/hdf) to it. Below is the text of the fstab (my system is a dual boot with WinXP Home SP2):

/dev/hdb3 / reiserfs acl,user_xattr 1 1 /dev/hda1 /windows/C ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0 /dev/hdb1 /windows/D vfat users,gid=users,umask=0002,iocharset=utf8 0 0 /dev/sda1 /windows/E vfat users,gid=users,umask=0002,iocharset=utf8 0 0 /dev/hda5 /windows/F vfat users,gid=users,umask=0002,iocharset=utf8 0 0 /dev/hda6 /windows/G ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0 /dev/hda7 /windows/H ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0 /dev/hdb2 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 /dev/cdrecorder /media/cdrecorder subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/dvdrecorder /media/dvdrecorder subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppy subfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0

Kelly

-- Kelly J. Morris

Now then, which one is the Zip drive in that lot? I wonder if it's /dev/sda1 ?

No, it's not there. sda1 (Win drive E) is a logical partition (for data sharing) on the first hard drive that is formatted FAT 32.

If so try changing it to this:

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

If you know that sda1 is not the Zip drive then perhpas add the whole of that line in to the end of your fstab file.

OK, but why would it be /dev/sda4 rather than /dev/hdf that was in the hardware list? Or does it not make any difference?

Whatever you do make sure you have a copy of the file before making any changes. I may have something totally wrong and I don't want you to mess your file up because of one of my suggestions.

Will do. Thanx. Kelly

-- Kelly J. Morris