This topic contains 2 replies, has 1 voice, and was last updated by Beatrice Demar 2 months, 4 weeks ago.
Viewing 3 posts - 1 through 3 (of 3 total)
-
Posts
-
Viewing 3 posts - 1 through 3 (of 3 total)
Forums › TWAIN Classic › Application crash
This topic contains 2 replies, has 1 voice, and was last updated by Beatrice Demar 2 months, 4 weeks ago.
My software opens communication with a scanner, requests a scan, pulls in the files, closes the data source and data source manager.
Sometimes, my application crashes when communicating with the data source (access violation – haven’t tracked it down). Next time the application opens, it can’t open communication with the data source since, presumably, the crashed application never closed it. The scanner shows a dialogue indicating it is unable to communicate. Once you restart the computer all is well again. Is there a way I can kill all open handles to that data source when my application opens?
When running into a problem with a TWAIN driver, it’s necessary to talk to the scanner vendor. They would be able to explain why their scanner can’t be used after an application crash.
There are some free tools you can use to try to understand what’s going on.
TWACKER – a simple app for TWAIN drivers that can be obtained from the TWAIN Working Group website
TWAIN C# – which includes a tool for trying things with TWAIN drivers, search for TWAIN Github to find the repository
Inspector TWAIN – a certification tool for exercising your scanner’s TWAIN driver
Can’t the problem be possibly caused by DEP? As happened to TWAIN2 under Win 32 bit? In this case all you need is to right-click Project in Solution Explorer, click Properties->Configuration Properties->Linker->Advanced->Data Execution Prevention (DEP) and set it to No.