Home › Forums › TWAIN Classic › Twain works or not according to the application
- This topic has 3 replies, 2 voices, and was last updated 10 years, 7 months ago by MarkM.
- AuthorPosts
Hello Twain comunity,
I am developing a remote driver for RDP, I am now on test phase, everything works fine but on one of my Computer twain works only on half of the applications.
The problem appears with all Datasources not only mine.
Here a screenshot as exemple where twacker and the mfc sample application see the datasource and gimp and the twain app sample not.
Thank you
Howdy…
The evidence suggests that your copy of gimp was built as a 64-bit native application. Twacker and the Sample App are likely built as 32-bit, causing them to look inside of c:windowstwain_32 for *.ds files. A 64-bit app will look inside of c:windowstwain_64, and it appears that your scanner doesn’t have a 64-bit TWAIN driver.
In that situation it’s recommended that you contact the scanner manufacturer and ask if they have a 64-bit TWAIN driver. Good luck…
— Mark
Actually gimp and twain_app_cmd32 are 32bit build. The exact same .exe can see this same driver on another computer.
I feel like the problem come from the installation of twain on this computer.
It’s an odd situation. You can turn on environment variables to get log information from TWAINDSM.DLL (assuming that’s in use). Just set TWAINDSM_LOG to the full path and name of the log file you’d like to create. You can also set TWAINDSM_LOGMODE to the desired fopen() mode, you’d like to use, in case you want to save all of the possible data.
Or, you can download the source code for TWAINDSM.DLL and use that to debug the issue, but again, this assumes that the application is using TWAINDSM.DLL instead of the older TWAIN_32.DLL. If you’re building GIMP yourself, you might want to change the DSM name from TWAIN_32 TWAINDSM (assuming that it’s using LoadLibrary, which I hope it is). The newer open source DSM is 100% compatible with the older DSM, so that should work just fine.
- AuthorPosts