- This topic has 1 reply, 2 voices, and was last updated 8 years, 1 month ago by .
-
Posts
-
Hi,
I’m doing some tests using two versions of the Twacker 32 bits tools on windows vista (64B OS) using the twain_32.dll as DSM.
the first Twacker tool has the version 1.703, and I had not problem with my data source device.
With the same DS and the Twacker tool (version 1.8.0.0), I got the message in Native mode transfert : Handle to Bitmap Invalid.
When debugging the last Twacker code (version 1.8.0.0), I saw that the FixUp routine in Twacker.c called some windows function :
hBitMap = CreateDIBitmap (hDC, lpDib, (LONG)CBM_INIT, (LPSTR)lpBits,
(LPBITMAPINFO)lpDib, DIB_RGB_COLORS);The hBitmap was NULL, but when I call getLasterror() on CreateDIBitmap I had an Ok status, I mean a 0 return code of CreateDIBitmap but NULL pointer!
Can some one Help me resolving this?
Thanks a lot.Howdy…
I tried this with one of my Kodak TWAIN drivers (i940), running the 32-bit Twacker 1.8.0.0 on Windows 8 (64-bit). I ran numerous native transfer scans with black-and-white, grayscale and color, and encountered no problems using either TWAINDSM.DLL or TWAIN_32.DLL. I also confirmed with another vendor that they’re not seeing any issues with this configuration…
Based on that admittedly limited feedback it seems reasonable to conclude that the scanner driver is having a problem.
If you can provide more details on all of the settings used for the scanning session (assuming that makes a difference), I’d be happy to retry a test that’s more exact compared to what you’re doing. Otherwise I’d take a closer look at the contents of the data being passed to CreateDIBitmap…