Scanner driver?

linuxsux pulled this Usenet face plant:



Idiot

--
Love in your heart wasn't put there to stay.
Love isn't love 'til you give it away.
-- Oscar Hammerstein II

said...

Bob Henson wrote:

Stan, I not very techie, but I tried to install Linux Mint 64bit in
Virtualbox on my 64 bit Win7 machine, and got the error message that
VT-x/AMD-V needed to be enabled in my BIOS - I guess that's something to
do with the processor - is yours an AMD processor and might this be the
problem?

* VirtualBox?s 64-bit guest support (added with version 2.0) and
multiprocessing (SMP, added with version 3.0) both require hardware
virtualization to be enabled. (This is not much of a limitation since
the vast majority of today?s 64-bit and multicore CPUs ship with
hardware virtualization anyway; the exceptions to this rule are
e.g. older Intel Celeron and AMD Opteron CPUs.)

So the error you got, is because the guest you used was a 64-bit
one, and VirtualBox needs VT-x or Pacifica turned on for that.

I didn't follow that up, as it didn't really matter whether or not I
installed 32 or 64 bit - so I just used the 32 bit. Are there any
disadvantages in turning on the VT-x support? As I only installed
Virtualbox/Linux for test purposes, I don't want to do anything to the
detriment of my Windows7 set up here.

There is a status page for various guest OS installs here, and the
nature of the user manual, and the status of the OSes here, makes
you wonder exactly how they're going about this emulation.

http://www.virtualbox.org/wiki/Guest_OSes

I don't know enough to comment about that. Interestingly the use under
Windows7 32/64bit section says "Audio drivers must be manually
installed" - but all the Audio worked just fine in the host and the
guest - so maybe they've updated that.

In this article, it mentions...

http://en.wikipedia.org/wiki/Virtualbox

"In the proprietary edition (not in the open-source edition),
a USB controller is emulated (both USB 1.1 and USB 2.0) so that
any USB devices attached to the host can be seen in the guest."

so that is the edition you'd want if attempting to run a scanner
on the host system, via a driver in the guest OS.

I got the proprietary version direct from Oracle (still free) so I've
had no difficulty with USB devices to date - I have the guest talking to
external drives, USB sticks etc. just fine. I'm just about to see if my
own advice to Stan works here too, and see if I can run my old scanner
too, without having to connect it to my Linux powered laptop - it would
save me a great deal of time if it did.

Looks like fun.

I'll let you know shortly! Next project is to run XP in a VM and see if
I can run some of my otherwise obsolete XP programs too. Luckily, I'm OK
for disk space, but memory requirements may be a tad restrictive if I
try to run them all at once.

--
Regards,

Bob

Licentiae, quam stulti libertatem vocabant - Tacitus

said...

Looks like fun.


Sadly, this bit wasn't. Virtual box recognised the scanner, added it to
the USB Devices list and marked it captured - but the scanning software
in the Linux guest couldn't see the scanner. That may be down to the
software, but I've no way to tell.

--
Regards,

Bob

Licentiae, quam stulti libertatem vocabant - Tacitus

Bob Henson wrote:


I didn't follow that up, as it didn't really matter whether or not I
installed 32 or 64 bit - so I just used the 32 bit. Are there any
disadvantages in turning on the VT-x support? As I only installed
Virtualbox/Linux for test purposes, I don't want to do anything to the
detriment of my Windows7 set up here.


Unless there is some security exposure (like allowing some
hypervisor malware to run), I wouldn't think it would matter
otherwise, whether VT-x was enabled or disabled. It's to
help with virtualization, so shouldn't affect other things.

http://en.wikipedia.org/wiki/Blue_Pill_(malware)

I leave mine turned on in the BIOS now. I use VPC2007 a fair bit,
and it is supposed to support VT-x, but I can't tell the difference
with it enabled or disabled in the program. I've just left it
turned on in the BIOS, for the time being. Maybe I'm too
lazy for my own good.

Paul

Bob Henson wrote:
said...
Looks like fun.


Sadly, this bit wasn't. Virtual box recognised the scanner, added it to
the USB Devices list and marked it captured - but the scanning software
in the Linux guest couldn't see the scanner. That may be down to the
software, but I've no way to tell.


Is the VEN and DEV of the scanner, available when you use the "lsusb"
command in Linux ?

Paul

linuxsux wrote:

It's very common for

*plonk*

said...

Bob Henson wrote:
said...
Looks like fun.


Sadly, this bit wasn't. Virtual box recognised the scanner, added it to
the USB Devices list and marked it captured - but the scanning software
in the Linux guest couldn't see the scanner. That may be down to the
software, but I've no way to tell.


Is the VEN and DEV of the scanner, available when you use the "lsusb"
command in Linux ?

Paul

Having shut down the system for something else entirely, I booted
everything up again, reconnected the scanner, and tried again. I did
everything exactly as before, but this time it let me select the scanner
and use it - why it didn't before, I don't know. I've just done a test
scan, and all is well. My scanner is safe from the dustbin (UK
readers)/trashcan (USA)!

Out of curiosity, lsusb shows:-

Bus 002 Device 003: ID 03f0:0205 Hewlett-Packard ScanJet 3300c
Bus 002 Device 002: ID 80ee:0021
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

- not that that means a lot to me.



Regards,

Bob

Licentiae, quam stulti libertatem vocabant - Tacitus

On 10/26/2010 2:04 AM, Alias wrote:
On 10/26/2010 10:18 AM, linuxsux wrote:
Bob wrote in news:MPG.27309cd27bac374a9896c9
@news.eternal-september.org:

said...

If you only have the occasional batch of stuff to scan, perhaps
you could boot a Linux LiveCD and scan from there.

Until it's completely dead, I could use my old XP laptop, I guess. I
haven't tried recently, but the last Ubuntu DVD I tried wouldn't boot
on my 64-bit Dell laptop. (Yes, I was using 64-bit Ubuntu.)

Stan, I not very techie, but I tried to install Linux Mint 64bit in
Virtualbox on my 64 bit Win7 machine, and got the error message that
VT-x/AMD-V needed to be enabled in my BIOS - I guess that's something to
do with the processor - is yours an AMD processor and might this be the
problem?

Linux ****ed up your system BIOS.
It's very common for that **** Linux to **** with the BIOS and render
your
machine DOA.
Better make certain it didn't burn out your CPU and **** up your
monitor by
overdriving it.
I wouldn't touch Linux with a 20 foot pole because Linux sucks.

How long have you been such an outright liar?

Proly not nearly as long as you.
Oops!

On Tue, 26 Oct 2010 08:18:13 +0000, linuxsux wrote:

Linux ****ed up your system BIOS.
It's very common for that **** Linux to **** with the BIOS and render
your machine DOA.
Better make certain it didn't burn out your CPU and **** up your monitor
by overdriving it.
I wouldn't touch Linux with a 20 foot pole because Linux sucks.

Got free from the restraints again, I see.

--
RonB
Registered Linux User #498581
CentOS 5.5 or VectorLinux Deluxe 6.0

On 10/26/2010 03:18 AM, linuxsux wrote:


Linux ****ed up your system BIOS.
It's very common for that **** Linux to **** with the BIOS and render your
machine DOA.
Better make certain it didn't burn out your CPU and **** up your monitor by
overdriving it.
I wouldn't touch Linux with a 20 foot pole because Linux sucks.


HAHAHAHAHAHAHA. Wow..

"Bob Henson" wrote in message
...

Having shut down the system for something else entirely, I booted
everything up again, reconnected the scanner, and tried again. I did
everything exactly as before, but this time it let me select the scanner
and use it - why it didn't before, I don't know. I've just done a test
scan, and all is well. My scanner is safe from the dustbin (UK
readers)/trashcan (USA)!


--------------------------------------------------------------------------------

That rings a bell. With a lot of scanners, when you install the drivers, the
scanner must be either switched off or disconnected. At some stage during
the installation, you will be prompted to connect and switch it on. For some
reason, if it is connected, the drivers will not initiate properly. A reboot
will invariably complete the process.

Things were so much easier with the BBC B. And even easier when you handed
your completed program to your college tutor, and waited three days for the
results. :-)

jim

Bob Henson wrote:
said...
Bob Henson wrote:
said...
Looks like fun.

Sadly, this bit wasn't. Virtual box recognised the scanner, added it to
the USB Devices list and marked it captured - but the scanning software
in the Linux guest couldn't see the scanner. That may be down to the
software, but I've no way to tell.

Is the VEN and DEV of the scanner, available when you use the "lsusb"
command in Linux ?

Paul

Having shut down the system for something else entirely, I booted
everything up again, reconnected the scanner, and tried again. I did
everything exactly as before, but this time it let me select the scanner
and use it - why it didn't before, I don't know. I've just done a test
scan, and all is well. My scanner is safe from the dustbin (UK
readers)/trashcan (USA)!

Out of curiosity, lsusb shows:-

Bus 002 Device 003: ID 03f0:0205 Hewlett-Packard ScanJet 3300c
Bus 002 Device 002: ID 80ee:0021
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

- not that that means a lot to me.



Regards,

Bob

Licentiae, quam stulti libertatem vocabant - Tacitus

That's interesting. I was playing with the VirtualBox yesterday,
doing the same kinds of things you're trying. If I tried to "capture"
a device in the guest OS (I tried a beta x64 Ubuntu and 10.04LTS x32
Ubuntu), I was getting some error, perhaps caused by some issue on
the host side. Using lsusb, all I could get was

Bus 002 Device 002: ID 80ee:0021
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The 80ee:0021 is identified here. I don't know exactly what
you're supposed to do with that virtual device.

http://www.linux-usb.org/usb.ids

80ee VirtualBox
0021 USB Tablet

I was using a couple webcams, as a source of potential USB
devices to grab. And I'm still stuck... Even after some reboots
of both the host and the guest. I keep getting the same error
message when I try to capture a device.

I have a question for you. Did you install the "extras" package
to your Ubuntu guest ? That is where I stopped yesterday - I
need to install Ubuntu on the virtual drive inside the virtual
machine, then try and install the "extras" or add-ins package,
and perhaps then I'll be seeing my test webcams. Up to now,
I was running Ubuntu as if it was a LiveCD, and maybe that
is why it's not working.

If you're seeing this:

Bus 002 Device 003: ID 03f0:0205 Hewlett-Packard ScanJet 3300c

then I'd get that "SANE and friends" packages installed, and
see if you can start scanning. That would be proof the device
is really mapped into the guest OS.

Paul

said...

I was using a couple webcams, as a source of potential USB
devices to grab. And I'm still stuck... Even after some reboots
of both the host and the guest. I keep getting the same error
message when I try to capture a device.

I have a question for you. Did you install the "extras" package
to your Ubuntu guest ? That is where I stopped yesterday - I
need to install Ubuntu on the virtual drive inside the virtual
machine, then try and install the "extras" or add-ins package,
and perhaps then I'll be seeing my test webcams. Up to now,
I was running Ubuntu as if it was a LiveCD, and maybe that
is why it's not working.

I have the extras packet and installed it in Linux, and it is certainly
essential.


If you're seeing this:

Bus 002 Device 003: ID 03f0:0205 Hewlett-Packard ScanJet 3300c

then I'd get that "SANE and friends" packages installed, and
see if you can start scanning. That would be proof the device
is really mapped into the guest OS.

Paul


Now - this is going to sound ridiculous, and I'm going to do more
testing later to see if it replicates every time. When you plug in a USB
device, it gives the standard Windows sound for a connecting USB device,
and then (if you have things set that way) pops up the Windows Autoplay
menu for the device, which, I close) - i.e. the device has connected to
the host machine.

The device shows up (if you're not running the guest full screen) in the
Virtualbox headers under "Devices USB Devices" If you look at that
list of devices there is a faint, vertical, grey line to the left of the
devices. If you try to click the device name you get a complicated error
message (means nothing to me) and nothing works. If you click opposite
the device but TO THE LEFT OF THE GREY LINE, you immediately get the
windows "USB disconnecting" sound as the device is disconnected from the
host. If you go away form that menu for a second and then reopen it, a
large tick has appeared adjacent to the device and TO THE LEFT of that
grey line. Within seconds the device then automatically mounts itself -
and all is well.

If I'm correct, the only problem is a stupid bug (or inaccuracy) in
Virtualbox which requires you to click in PRECISELY the correct place to
get the desired effect. It sounds ludicrous, but it's worked so far
(five or six attempts with different USB devices). It may or may not be
a known problem - but I'm hoping I now have a known answer!


--
Regards,

Bob

Licentiae, quam stulti libertatem vocabant - Tacitus

Bob Henson wrote:
said...
I was using a couple webcams, as a source of potential USB
devices to grab. And I'm still stuck... Even after some reboots
of both the host and the guest. I keep getting the same error
message when I try to capture a device.

I have a question for you. Did you install the "extras" package
to your Ubuntu guest ? That is where I stopped yesterday - I
need to install Ubuntu on the virtual drive inside the virtual
machine, then try and install the "extras" or add-ins package,
and perhaps then I'll be seeing my test webcams. Up to now,
I was running Ubuntu as if it was a LiveCD, and maybe that
is why it's not working.

I have the extras packet and installed it in Linux, and it is certainly
essential.

If you're seeing this:

Bus 002 Device 003: ID 03f0:0205 Hewlett-Packard ScanJet 3300c

then I'd get that "SANE and friends" packages installed, and
see if you can start scanning. That would be proof the device
is really mapped into the guest OS.

Paul


Now - this is going to sound ridiculous, and I'm going to do more
testing later to see if it replicates every time. When you plug in a USB
device, it gives the standard Windows sound for a connecting USB device,
and then (if you have things set that way) pops up the Windows Autoplay
menu for the device, which, I close) - i.e. the device has connected to
the host machine.

The device shows up (if you're not running the guest full screen) in the
Virtualbox headers under "Devices USB Devices" If you look at that
list of devices there is a faint, vertical, grey line to the left of the
devices. If you try to click the device name you get a complicated error
message (means nothing to me) and nothing works. If you click opposite
the device but TO THE LEFT OF THE GREY LINE, you immediately get the
windows "USB disconnecting" sound as the device is disconnected from the
host. If you go away form that menu for a second and then reopen it, a
large tick has appeared adjacent to the device and TO THE LEFT of that
grey line. Within seconds the device then automatically mounts itself -
and all is well.

If I'm correct, the only problem is a stupid bug (or inaccuracy) in
Virtualbox which requires you to click in PRECISELY the correct place to
get the desired effect. It sounds ludicrous, but it's worked so far
(five or six attempts with different USB devices). It may or may not be
a known problem - but I'm hoping I now have a known answer!



I'm seeing different issues here. The list of USB devices doesn't seem
to update itself. For example, I can unplug a webcam, and the menu
entry in VirtualBox stays there. And the response when I click the
entry, is the same error message every time. I've tried installing
the Guest Add-Ons in both a Windows guest OS and the Ubuntu x64
installation, and it made no difference at all. The error message
I'm getting, suggests it's an issue between VirtualBox and Windows 7
(the host), rather than a function of the guest.

The error message includes a GUID (long string of numbers and letters),
and I looked for that in Regedit on the host, only to find it
doesn't exist. So I don't know as a result, whether VirtualBox is
looking for the wrong thing, or the GUID it prints on the screen
has nothing to do with the host operation at all.

I even tried running VirtualBox elevated, and the comical result
was, the USB menu stopped working entirely :-) You could click the
USB entry, and there was no menu and no response. The entry above,
for the CD drive, continued to work properly. So running elevated
didn't have any positive effect.

I think I'm going to ditch it pretty soon, as I'm just not making
any progress.

Paul

said...


If I'm correct, the only problem is a stupid bug (or inaccuracy) in
Virtualbox which requires you to click in PRECISELY the correct place to
get the desired effect. It sounds ludicrous, but it's worked so far
(five or six attempts with different USB devices). It may or may not be
a known problem - but I'm hoping I now have a known answer!



I'm seeing different issues here. The list of USB devices doesn't seem
to update itself. For example, I can unplug a webcam, and the menu
entry in VirtualBox stays there.

It does here too - the entries go when you shut Virtualbox and restart.
It may be that it leaves them there in case you plug the device back in
again - I haven't checked that.

And the response when I click the
entry, is the same error message every time. I've tried installing
the Guest Add-Ons in both a Windows guest OS and the Ubuntu x64
installation, and it made no difference at all. The error message
I'm getting, suggests it's an issue between VirtualBox and Windows 7
(the host), rather than a function of the guest.

I got something like that, until I started clicking in the correct
place.

The error message includes a GUID (long string of numbers and letters),
and I looked for that in Regedit on the host, only to find it
doesn't exist. So I don't know as a result, whether VirtualBox is
looking for the wrong thing, or the GUID it prints on the screen
has nothing to do with the host operation at all.

It might well be the guest, I suppose - but I'm way out of my depth in
even guessing that.

I even tried running VirtualBox elevated, and the comical result
was, the USB menu stopped working entirely :-) You could click the
USB entry, and there was no menu and no response. The entry above,
for the CD drive, continued to work properly. So running elevated
didn't have any positive effect.

I think I'm going to ditch it pretty soon, as I'm just not making
any progress.

I'm going to persevere with it, as it's now running OK here (more by
luck than judgement) - next try is a second installation of Mint 10RC to
test it out before I commit it to my laptop. Then I'm going to try
running XP in a VM. The main advantage of being retired is having time
to play with these things - even if I don't know what I'm doing. Next
project is to LEARN what I'm doing - before my brain goes totally!


--
Regards,

Bob

Licentiae, quam stulti libertatem vocabant - Tacitus