Failure of scanner to work in Windows/Fusion

[Mravinsky]

I am far from convinced that this is a problem relating to VMFusion as such, but the Apple forum suggested that someone in the VMWare discussion group might know of a solution

My Visioneer OneTouch 8700 scanner runs perfectly on the old PC, where it was set up originally using its disc which tied PaperPort7 Software in with the installation program itself. Later upgraded to PaperPort10.

After connecting to my new MacPro, the scanner's icon is displayed in Control Panel>Scanners; also PaperPort 10 shows in the full dropdown list of programs, but the scanner itself does not work.

Clicking on that icon in Scanners produces the message "Cannot detect scanner. Make sure the scanner is turned on & properly connected to the Computer".

Any ideas, please? I do not want to buy another scanner when the existing one still works superbly - albeit only when connected to a PC!

[Texiwill]

Hello,

Moved to Fusion forum.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education. As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

[admin]

- most notably, what version of Fusion are you running, and is the scanner connected to the virtual machine (e.g. is the appropriate icon on the right side of the status bar glowing blue)?

[Mravinsky]

VMFusion version 1.0.

After several hours of thought, light dawned - it was due to another program. When the scanner was purchased it was linked in with a program called ScanSoft. This was updated last year on the PC, subsequent to which everything was moved over to the Mac.

However, it appears that the drivers for the scanner were bound up with the original version of ScanSoft. So........the scanner did not work because the driver had not been installed; then the original ScanSoft refused to load until its later version had been removed.

Remove the update, install the original, then re-install the update; now everything is functioning perfectly! Good thing that I did not throw away the old disc!