[RhoXS]

We have been using an HP Scanjet 7450C scanner with the HP PrecisionScan Pro scanning software and Paperport. This combination of hardware and software worked very well for us allowing us high productivity, excellent control over the scanned images, and a very good and usable electronic filing system. All this changed immediately after installing Windows 7.

Under Windows 7 (both 32 and 64 bit versions), PrecisionScan Pro (using a TWAIN driver) will no longer "initialize" our Scanjet 7450C, even though the scanner is properly installed as shown by the Device manager. WIA applications such as VueScan work fine but none begin to be as useful as PrecisionScan Pro.

I tried a number of possible solutions and finally found a workaround that works but not very satisfactorily. Under a 32 bit (but not 64 bit) instance of virtual XP, PrecisionScan Pro will finally play nice with the scanner. The major downside results from Paperport (both versions 11 and 12) being very sluggish and prone to crashing in the virtual XP environment.

I have another idea I want to try. I am wondering if PrecisionScan Pro might be willing to behave if I use a SCSI connection instead of a USB connection. The existing USB connection functions perfectly because the scanner is properly shown in the Device Manager and WIA (not TWAIN) based apps work fine. Therefore, I am thinking the issue is with the HP PrecisionScan Pro TWAIN driver and how it communicates with the USB port under Windows 7. Maybe the HP TWAIN driver will behave better if it is only asked to talk to a SCSI connection.

Using a SCSI connection requires buying a new SCSI card, costing almost $200.00. I do not mind spending the money if I had some reasonable assurance it will work so I am looking for opinions. I can always return the card to Newegg less shipping and a 15% restocking fee but I would rather be fair and not risk cycling Newegg unless I have some reasonable assurance the SCSI card will resolve the problem.

It really would be nice to fix this problem and avoid all the inconvenience, crashes, and SSD overhead used by Virtual XP. It also would mean I can revert back to the 64 bit version of Windows 7 and take needed advantage of all of the new 4GB of memory we just purchased.

[I.M.O.G.]

It seems to me your thinking in the wrong direction. I apologize if this is not the answer your looking for, however I'm thinking your best bet may be to evaluate other electronic filing options which advertise Windows 7 support and have better developer backing. Buying expensive hardware to possibly stretch more life out of a poorly supported software application is going to leave you high and dry eventually, if not know, a few more years down the road.

I hope someone else has better advice however.

[SuperMiguel]

why you want to use 7? stay with XP if it worked fine

[johnz]

Originally Posted by SuperMiguel

why you want to use 7? stay with XP if it worked fine

While I'm generally against XP at this point, I'm more against making hardware purchases just to maintain compatibility. Staying with XP isn't a bad idea in this case.

[I.M.O.G.]

Originally Posted by SuperMiguel

why you want to use 7? stay with XP if it worked fine

I'd agree with this... Except once it goes EOL. A plan should be made. XP would be best for now however until that plan is tested and shown to work acceptably.

[RhoXS]

Originally Posted by I.M.O.G.

I apologize if this is not the answer your looking for...

Please do not apologize for taking the time to respond to my question. I certainly appreciate the effort no matter what your opinion is.

I made the transition to W7 for a number of reasons. I tried W7 RC on my laptop, liked it very much, and decided I would have to make the transition sooner or later. The $50/$100 sale last summer for W7 Professional & Home really pushed the decision to sooner than later. Also, it was my intention to run 64 bit and increase the amount of memory to 4 GB.

Now that I made the transition, along with installing an Intel G2 80 GB SSD, I have no regrets and in fact am very pleased with it. Although I had to go back to a 32 bit system, everything from boot up times, program loading times, execution times, etc. run noticeably faster. My machine has a spring to it I never before experienced; everything happens almost instantaneously. It is also much better behaved with respect to networking with other computers and devices on our home network. I no longer have any issues transferring files and even just seeing the one Vista machine we have.

Obviously, everything is not perfect in paradise. The one and only issue is the problem with the HP scanning application, PrecisionScan Pro. It actually works fine too but it will not see the scanner. Paperport, the electronic paperless filing system works fine under both W7 32 and 64 bit systems. It just behaves badly when running it under Virtual XP, something necessary to get PrecisionScan Pro to work properly.

Anyway, I am now committed to W7, have a workaround to a scanning problem that suffices but is not ideal, and really do not want to go back to XP.

Unless someone knowledgeable can tell me that the problem with PrecisionScan Pro seeing the scanner will probably also carry over to a SCSI interface, I am going to order an Adaptec 29320LPE SCSI card from Newegg and try a SCSI connection. I spoke to Newegg today and they do not have a problem taking the card back if it does not work but will probably charge me a 15% restocking fee ($24.00).

[johnz]

You could try different VM software and see if it's better behaved. You'll need an XP license to install, but it's worth a shot. VMware Server, and VirtualBox is what I'd try.