Comment 38 for bug 478761

Hi Davias,

That's great -- I'm glad it worked! And thanks for letting me know: It
makes me feel better knowing that at least one other person is having a
similar problem and that the same solution works. Thanks also for posting
to LaunchPad so others can know, and I'm glad to know that it worked from
within VirtualBox, as I use it to for legacy Windows issues.

Too bad we're finding this out just as Ubunutu has dropped xsane from
official support / its repositories as of Lucid 10.4.... :( Not the end of
the world, tho': I'm sure .debs will be available, and worse case I'll
build it from sources myself. I'm prefer the control that xsane gives me
compared to Simple Scanner and the like.

Best,
Doug

On Tue, 01 Jun 2010 14:32:33 -0000 Davias <email address hidden> wrote:
>
> Dear Doug,
> sorry for the delay, I finally had time to give a try to your solution:
> IT WORKS! (where nothing else did...)
>
> This is what I did:
> 1) started Windows 2000 in VirtualBox 3.1.6 on my Ubuntu 9.10 AMD64
> 2) on the Devices menu of VirtualBox I selected "unknown USB device
> 05D8:4022" - this is the address where my Mustek scanner lives on. 3)
> started DirectScan, the Mustek scan program on Win2K 4) the Win2K device
> disconnect window appeared, informing that it was now safe to unplug USB
> device Mustek ScanPlus 1200 5) at THE SAME TIME the XSane dialog box
> appeared offering which device to use for scanning, my webcam or Mustek
> ScanPlus 1200 - this is common as I have 2 scanning device, at least for
> sane. 6) selected the Mustek ScanPlus 1200 and instead of getting "open
> of device gt68xx:libusb:001:009 failed: Invalid argument" I had xsane up
> and running!
>
> So definitely using the Windows driver took the scanner away from this
> strange lock mode it was fallen!
>
> Thanks again for your solution,
> Dave
>