We are have trouble with our entire application crashing when attempting to scan or acquire via TWAIN after an upgrade to Windows 10.
I personally doubt that the problem lies with our version of GdPicture, because some computers are working well with Windows 10. But two computers crash even though the latest drivers for Ambir Pro 820i scanner have been installed.
When GdPicture loads a DSM (Data Source Manager), it first looks for TwainDSM.dll in System32. If that file does not exist, it then looks for Twain_32.dll in c:\windows. I discovered this by repeatedly testing using the TwainSetDSMPath method. The inoperable tainDSM.dll prevented GdPicture from try to load Twain_32.dll, thus causing our app to hang.
The scanner tech support (Ambir) said that in their experience, upgrading to 10 from earlier versions of windows is a total crapshoot, where one can get all kinds of strange behavior.
Our solution, in this case, will be to have a special setting on that computer that forces GdPicture to use twain_32.dll without first probing for TwainDSM.dll. It's that or insist that the client re-install Windows 10 on a clean machine, from scratch. Because we can't seem to rid ourselves of the phantom TwainDSM.dll.
By the way, if your app, which contains GdPictureImaging, is exhibiting strange behavior, use the sample app provided by GdPicture to test at client site. That's what I did, and how I traced this issue to its cause.
Just thought I'd put this out there for next poor chump that stumbles into what took me a long time to figure out.
Who is online
Users browsing this forum: No registered users and 4 guests