[Bug 7207] Improving ZIP drive support

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=7207
Ubuntu | linux





------- Additional Comments From vincent.trouilliez at modulonet.fr  2005-12-08 03:08 UTC -------
Okay I did some basic testing. I am writing this from Dapper while testing my
drives. Here is what I found so far, with regard to my internal, IDE drive. I
will run tests on my parallel external drive later if you deem it useful.

Conditions of test: a ZIP disk is present and inserted in the drive, while the
computer is being booted. In the past that proved to help things...


Good things:
------------
- Drive detected at boot ("ide_floppy" module loaded automatically)
- Nice ZIP icon, with proper label, in Nautilus
- Double click on the icon shows contents of disk
- Able to copy files from ZIP to computer and vice versa
- While copying from ZIP to computer, a dialog with progress bar shows up

Bad things:
-----------
- Very slow to respond: takes 20 secones to mount the disk, and 15 seconds to
read/show its contents in a Nautilus window.
- When right-clicking on the icon and selecting "Eject" (there is no unmount
option, only eject), it won't eject the disk (pressing the button on the drive
won't work either sadly), and gives an error dialog: "Unable to eject media:
eject: unable to eject, last error: Invalid argument". 
If I try to eject it by hand at the command line (eject /dev/hdd), it returns
this error: "not an sg device, or old sg driver".
I am using the internal IDE drive here, so it's weird that it's talking about
scsi devices, probably why Nautilus throws an error when asked to eject the disk ?!

So the situation has improved quite a lot compared to Breezy, maybe we can get
it 100% right in time for Dapper, who knows ! ;-)

I will now give my external parallel port a go, hopefully it too will work
better... :-)

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.