Home › Forums › TWAIN Classic › PaperStream hang after scanning
- This topic has 2 replies, 2 voices, and was last updated 9 years, 5 months ago by Thread77.
- AuthorPosts
I am having a problem scanning with the PaperStream TWAIN driver with an internally-built application. I have tested this with a fi-6130, fi-7160, and a fi-7180.
This is a .NET WPF application using Leadtools TWAIN libraries to control the scanner. The software works fine scanning with a fi-6130 using version 9.21 of the the old Fujitsu “Scanner Utility” TWAIN driver. However, when scanning with the same scanner (or a fi-7160 or fi-7180) on a workstation using the PaperStream IP Twain driver (version 1.8.0.3033), the application hangs after scanning. The application logic continues to run, but the UI becomes unresponsive. It feels like there is a modal dialog presented over the application that is preventing the UI from refreshing or capturing input. There is no visible dialog, though.
Someone posted back in March about a similar problem scanning into IrfanView – http://twainforum.org/viewtopic.php?f=2&t=10322&sid=fcd5c58b7d8b94b3db7d41b4ff73efb9. A Fujitsu representative responded that a fix was available. I was wondering if there was any confirmation of whether the fix discussed in that thread is in the version of the PaperStream IP TWAIN driver currently posted on the Fujitsu website, version 1.8.0.3033.
I appreciate any help I can get on troubleshooting and resolving this issue. My company is unable to deploy new scanners until we get past this problem.
Thanks,
AndyI should note as well that if I configure the Leadtools TWAIN interface to show the scanning UI provided by the driver, then my application frequently or always gets control back after scanning. If I configure the Leadtools TWAIN interface to hide the driver’s scanning UI, then my application almost never gets control back after scanning is completed.
Our application requires 1 bit per pixel images and works best with Advanced DTC and several other Fujitsu-specific settings just so. We do not want to show the driver UI, because we don’t want our users to change the scanner settings when scanning. Also we want to avoid them having to click on another button to initiate scanning.
Did you have any luck with your issue? I’m also having the exact same problem.
- AuthorPosts