Unfortunately, it is very often when problems that you maybe experiencing with OCR processing are results of malfunctioning printer drivers. Here are several steps to determine whether the source of the issue is the SimpleIndex application, the driver interface provided by our vendor, or the Kodak scanner driver. If you have a few minutes and can perform these tests and send the diagnostic logs that would be much appreciated. But one of us can remote in and help out after the break if you would rather do it that way.

TWAIN Driver Tests:

Please download and install (onto your client machine) the diagnostic logging tool from here:

http://www.eztwain.com/eztwain4-diagnosis.htm

Install on the affected machine… and then after you install TWISTER and before you run TWISTER, start Dosadi logging up .. this will capture some very detailed logs of all the communications and timing in TWAIN between the driver and TWISTER while twister does its job – attach both the logs to the case

Download the TWISTER Twain Driver Analyzer and run it on the scanner in question to produce a report (please have it do a 1 page scan as this gives extra diagnostic information). Please save the report to a text file and then attach that file to your reply. (Please don’t copy/paste the output directly into your reply as it will get truncated by our system and also makes a “wall of text” which makes the case hard to read)

http://www.eztwain.com/twister.htm

Also, you can

Download our TWAIN test app:

https://www.scanstore.com/downloads/TWAINTest.zip

Set the log file path by editing the Acquisition.exe.config file in Notepad and replace this with a valid local path:

initializeData=”c:\users\YOUR_USERNAME\Documents\DotTwain.log”

Please reproduce the issue while the logging is enabled, then attach the log file produced to your reply. (Please don’t copy/paste the output directly into your reply as it will get truncated by our system and also makes a “wall of text” which makes the case hard to read)

Below is a link to a third party free viewer that uses TWAIN but also does not touch DotTwain – you can test quickly to see if it has the delays

Download the free IrfanView image viewer from www.irfanview.com and use its TWAIN Scanning feature to select a scanner and scan a page. Let us know if it was able to scan successfully or if it encountered problems. This is useful because Irfanview does not use any DotTwain components and if it runs into the same errors, it’s a pretty good indication that the issue is with the driver/scanner/TWAIN subsystem and not our components.

ISIS Driver Tests:

To conduct this test, please download this test application:

https://www.scanstore.com/downloads/ScanTest.zip

Unzip them to c:\Temp\ScanTest

Technically you can put them anywhere but my command line sample will assume they are in that folder.

First, I would like you to run the ISISDemo.exe which is the demo app from our ISIS driver vendor. If it is able to quickly load the driver interface, then the issue is something in SimpleIndex that I should be able to fix myself. If this application also takes a long time to load, then the issue is something that must be resolved by the vendor.

Next, please run the following command line from a command prompt:

c:\Temp\ScanTest\ScanProcess.exe Test “c:\Temp\ScanTest\Test.pdf” Test -szl

This will display the ISIS driver settings interface and should replicate the driver delay, and generate a log file called Test.pdf.log in the ScanTest folder. Please send me that log.