Scanner driver?

[Stan Brown]

I have a CanoScan LIDE 50 scanner, and much to my surprise Windows 7
x64 Home Premium was unable to find a driver. Canon's site says none
is available for Win 7 or 64-bit Vista.

I tried the listed driver for Vista, and it ran without error, in
fact without a message of any kind. But my image program could not
find it in "Select TWAIN source", and in "Devices and Printers" the
scanner is still an "unknown device".

Am I just the victim of an inclined plane in the form of a helix, or
is there some sort of generic scanner driver I might install?

 

[Stan Brown]

I have a CanoScan LIDE 50 scanner, and much to my surprise Windows 7
x64 Home Premium was unable to find a driver. Canon's site says none
is available for Win 7 or 64-bit Vista.

I tried the listed driver for Vista, and it ran without error, in
fact without a message of any kind. But my image program could not
find it in "Select TWAIN source", and in "Devices and Printers" the
scanner is still an "unknown device".

Am I just the victim of an inclined plane in the form of a helix, or
is there some sort of generic scanner driver I might install?

And a related question: any reason not to turn off "Windows Fax and
Scan" for? It's currently checked, but obviously it can't interface
with my scanner. Or can it, and I'm just missing something?

I ask because I have a four-month-old zero-byte file %TEMP%
\FXSAPIDebugLogFile, and Windows won't let me delete it. Googling
found that this is associated with the Windows Fax and Scan feature.

 

[jbm]

"Stan Brown" wrote in message

I have a CanoScan LIDE 50 scanner, and much to my surprise Windows 7
x64 Home Premium was unable to find a driver. Canon's site says none
is available for Win 7 or 64-bit Vista.

I tried the listed driver for Vista, and it ran without error, in
fact without a message of any kind. But my image program could not
find it in "Select TWAIN source", and in "Devices and Printers" the
scanner is still an "unknown device".

Am I just the victim of an inclined plane in the form of a helix, or
is there some sort of generic scanner driver I might install?

--
Stan Brown, Oak Road Systems, Tompkins County, New York, USA
http://OakRoadSystems.com
Shikata ga nai...


Canon, in their wisdom, have decided to offer no support for their older
scanners in the 64-bit environment. I have searched extensively for a
generic 64-bit driver for Canon scanners, or one that will work with a Canon
scanner, but there doesn't appear to be one out there anywhere. There is a
note on Canon;s own web site to this effect. Various forums are full of it,
and there are a lot of very cross people out there. Microsoft have a list
of supported scanners on their site, and depending where you live, in the
USA some of Canon's machines will work, while here in the UK they won't.
Apparently, Microsoft are at a loss over the issue, and are unable offer
support or information, since they cannot get anything out of Canon. It is
Canon's decision, and I guess they are going to lose a large chunk of their
market share through it.

I have a CanoScan 8000F, and there's nothing wrong with it whatsoever, but
am now unable, and never will be able to use it on this computer. But all is
not lost. Second hand laptops are dirt cheap these days, and I have been
offered one running XP just after Xmas (present of a new one for one of
their kids), so I will be able to use that for the scanner and all the other
programs I have that refused to install into Win7.

If anyone knows any different, PLEASE post in this forum so we can all see
it. Thanks.

jim

 

[Paul]

I have a CanoScan LIDE 50 scanner, and much to my surprise Windows 7
x64 Home Premium was unable to find a driver. Canon's site says none
is available for Win 7 or 64-bit Vista.

I tried the listed driver for Vista, and it ran without error, in
fact without a message of any kind. But my image program could not
find it in "Select TWAIN source", and in "Devices and Printers" the
scanner is still an "unknown device".

Am I just the victim of an inclined plane in the form of a helix, or
is there some sort of generic scanner driver I might install?

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

Paul

 

[Chuck]

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

Paul

You can try ViewScan free! It supposedly supports your scanner.

"If you're using Windows and haven't installed the Canon driver, you can
instead install VueScan's driver by:

Make sure you've installed VueScan and that you've answered 'Yes' about
installing drivers
Click the Start button in the lower left corner
Click 'Computer' or 'My Computer' with the right mouse button and choose
'Properties'
Click the 'Hardware' tab (not needed on Vista or 7) and then click
'Device Manager'
Click the scanner with the right mouse button and choose 'Properties'
Click the 'Driver' tab
Click 'Uninstall'
Reboot the computer
If Windows asks for a driver for the scanner, tell it to install it
automatically or to look in c:\vuescan.

This should cause the driver for the scanner to be loaded properly."

 

[jbm]

"Chuck" wrote in message

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

Paul

You can try ViewScan free! It supposedly supports your scanner.

"If you're using Windows and haven't installed the Canon driver, you can
instead install VueScan's driver by:

Make sure you've installed VueScan and that you've answered 'Yes' about
installing drivers
Click the Start button in the lower left corner
Click 'Computer' or 'My Computer' with the right mouse button and choose
'Properties'
Click the 'Hardware' tab (not needed on Vista or 7) and then click
'Device Manager'
Click the scanner with the right mouse button and choose 'Properties'
Click the 'Driver' tab
Click 'Uninstall'
Reboot the computer
If Windows asks for a driver for the scanner, tell it to install it
automatically or to look in c:\vuescan.

This should cause the driver for the scanner to be loaded properly."

=======================

Unfortunately, you have to install Canon's own drivers to make the scanner
work with this program. And since Canon don't supply the necessary drivers
...........................................

jim

 

[Stan Brown]

"Chuck" wrote in message


You can try ViewScan free! It supposedly supports your scanner.

Thanks but $40 is kind of pricy. I'd at least like to see a free
alternative, if one exists.

 

[Stan Brown]

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.)

 

[Paul]

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.)

Did you check the BIOS settings ? My laptop has a grand total of
just one setting - "AHCI" versus "IDE" for the SATA interface.
AHCI is good enough for Windows 7, but some distro I've already
tried, spent a good deal of time "spinning its wheels" while poking
with an AHCI driver. Fortunately, it moved on after a wait of
30 seconds or so. Another one got stuck forever on the AHCI stage.

A lot of distros now, use the "quiet" and "splash" options on the
boot line. This prevents watching the text boot sequence for error
messages. Deleting the "quiet", exposes useful diagnostic info
(which for Linux, is a good choice for a default, if they had a clue).
Nobody gets hurt, if a little text appears on the screen, and having
it can only help.

On my Ubuntu CD, I have instructions printed on the jewel box
label, for useful things to do. This is paraphrasing the cryptic
suggestions on the label.

"Press F6 when the small icon appears at the bottom of the screen.

When it asks for language selection, select English etc.

Pressing F6 again, should cause an annoying menu to appear on
the right of the boot command line. Press <esc> to make that go
away. Press the right-arrow key, to cursor over to the end of the
command line. The cursor should really, already be over on the
right hand side. Pressing the right arrow, should cause the I-beam
cursor to light up, showing you where your input will go.

There will be crap to the left and right of "--". I delete the
"--". If I want to see text, I delete the "quiet" and "splash"
words.

Ubuntu has an option, to load the CD into RAM. This allows the
CD to be ejected after the OS loads. Then, all the software
runs from RAM. To be practical, the computer should have
at least 1.5GB of RAM (to leave some room to run programs).
Add TORAM=yes to the Ubuntu command line. The upper case of those
letters is important. Using a lower-case toram doesn't work.
It takes 3 minutes to load the CD into RAM, during which the
boot sequence will wait for it to complete and won't go further.
Be patient. Once the desktop appears, give the desktop startup
sequence time to complete (perhaps wait until it says "restricted
drivers are available), before attempting to right click on the
CDROM icon, and ejecting the CD. (You can easily learn the right
timing, with a few experiments.)

When your command line edits like adding the TORAM are complete,
press <Enter> to start the boot sequence. Some other distros use
control-X to start booting. It would be nice if the keyboard
shortcuts, kinda matched between distros, but that's expecting
a lot."

If you're bombing somewhere else, if there is any text on the
screen, knowing what it says might help. You can take a picture
of your computer screen (hi def), then post the picture to
imageshack.us , then provide a link to the stored image file
on the site. For example, this is my HDTune results from a
while back. You can put a good sized picture up there.

http://img829.imageshack.us/i/500gb3500418ascomposite.gif/

Paul

 

[Bob Henson]

(e-mail address removed) said...

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?

Failing that, my old scanner (HP 3300) has the same driver problem (no
64bit drivers), but runs fine with 32bit Ubuntu (and, presumably,
64bit). It's a lot of trouble to go to, but you could try installing
32bit Ubuntu in Virtualbox and running your scanner from there - that
way you get round the problems of installing a dual boot system anyway -
you can just run a VM when you need to scan from within Windows.


--
Regards,

Bob

Licentiae, quam stulti libertatem vocabant - Tacitus

 

[Paul]

(e-mail address removed) said...


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?

Failing that, my old scanner (HP 3300) has the same driver problem (no
64bit drivers), but runs fine with 32bit Ubuntu (and, presumably,
64bit). It's a lot of trouble to go to, but you could try installing
32bit Ubuntu in Virtualbox and running your scanner from there - that
way you get round the problems of installing a dual boot system anyway -
you can just run a VM when you need to scan from within Windows.

http://download.virtualbox.org/virtualbox/UserManual.pdf

"10.2 Hardware vs. software virtualization

As opposed to other virtualization software, for many usage scenarios,
VirtualBox does not require hardware virtualization features to be present.
Through sophisticated techniques, VirtualBox virtualizes many guest
operating systems entirely in software. This means that you can run
virtual machines even on older processors which do not support hardware
virtualization.

Even though VirtualBox does not always require hardware virtualization,
enabling it is required in the following scenarios:

* Certain rare guest operating systems like OS/2 make use of very esoteric
processor instructions that are not supported with our software
virtualization. For virtual machines that are configured to contain
such an operating system, hardware virtualization is enabled
automatically.

* 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.

http://en.wikipedia.org/wiki/AMD-V#AMD_virtualization_.28AMD-V.29

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

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.

Looks like fun.

I won't be trying that on the laptop, because it doesn't have
enough horsepower for it. But maybe I'll give it a try on
the desktop.

To see if VT-x is available on Intel, you can use Intel PIU.

http://www.intel.com/support/processors/tools/piu/sb/CS-015823.htm

And for Pacifica, perhaps this utility.

"AMD Virtualization Technology and Microsoft Hyper-V
System Compatibility Check Utility"

http://support.amd.com/us/Pages/dyn...432-4756-aafa-4d9dc646342f&ItemID=177&lang=us

Paul

 

[Chris Ahlstrom]

linuxsux pulled this Usenet face plant:

Idiot

 

[Bob Henson]

(e-mail address removed) said...

Bob Henson wrote:

* 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

 

[Bob Henson]

(e-mail address removed) 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

 

[Paul]

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

 

[Paul]

(e-mail address removed) said...

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

 

[chrisv]

It's very common for

*plonk*

 

[Bob Henson]

(e-mail address removed) said...

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

 

[jbm]

"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

 

[Paul]

(e-mail address removed) said...

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