The TWAIN Forum
It is currently Thu Jun 30, 2016 12:20 pm

All times are UTC - 8 hours [ DST ]

Post new topic Reply to topic  [ 5 posts ] 
Author Message
PostPosted: Mon Jun 10, 2013 8:34 am 

Joined: Mon Jun 10, 2013 8:20 am
Posts: 1
Hello All,
I need some assistance getting TWAIN devices seen by applications. MS Word and other software utilizing TWAIN will not recognize my TWAIN compliant device.

OS: Windows 2008 R2 with Desktop Experience installed / 64 Bit OS
Scanner: Kodak I2400 directly connected to the Server via USB

Twain_32 Twacker sees all TWAIN drivers and allows me to scan.
Twain_64 Twacker cannot see any TWAIN drivers or devices.
Is there a way to use / activate the TWAIN_32 Twacker when trying to scan from these applications? Perhaps there's a completely different issue.

Any assistance would be greatly appreciated!

PostPosted: Tue Jun 11, 2013 12:38 pm 

Joined: Thu Mar 10, 2005 1:16 pm
Posts: 137
Hi Phil...

It sounds like you have a few things going on there.

The Kodak i2400 comes with a 32-bit TWAIN driver. This driver works on native 32-bit versions of windows, and also works under WOW64 on 64-bit versions of Windows (Windows On Windows64 is the thunking layer for running 32-bit stuff on a 64-bit OS).

Kodak doesn't currently offer a native 64-bit TWAIN driver (please feel free to ask for this feature from Kodak support, it's the best way to get them to add it). What this means is that a native 64-bit application, won't see the i2400.

Moreover, I doubt that Microsoft has added support for the 64-bit DSM (C:\Windows\System32\TWAINDSM.DLL), so you might be out of luck of you're relying on a native 64-bit application from Microsoft.

If, however, you have control of the application, and you really want native 64-bit support, you can check out the list of scanners supporting this feature at this page on the TWAIN Working Group website. ... ivers.html

I hope this helps clarify things a bit...

-- Mark

PostPosted: Tue Jun 11, 2013 12:49 pm 

Joined: Sat May 28, 2005 12:10 am
Posts: 150
Location: Northampton, MA
Hi Phil - if Twack 32 sees the scanner (and can scan from it) then you've got working (32-bit) drivers, that's good. Especially on Windows Server 2008 R2!

What version of Word are you testing with, and what are the other programs that utilize TWAIN?

Generally, if an application supports TWAIN and you have working TWAIN drivers, the application will show those drivers.
If it doesn't, usually one of these things is happening:
1. The application is a 64-bit application. It will *not* be able to use the 32-bit TWAIN drivers seen by Twack_32. It will be able to use 64-bit TWAIN drivers as shown by Twack_64, but... 64-bit TWAIN drivers are not yet commonly available.
2. The application does not support TWAIN - check the specifications or support area of the application to confirm that it supports TWAIN.

A few applications support WIA instead of TWAIN. Those applications will 'see' some scanners that are WIA-compatible, and not see others. You can see your WIA-compatible scanners in the Device Manager, under 'Imaging devices'.

PostPosted: Sun Mar 16, 2014 9:17 pm 

Joined: Sun Oct 20, 2013 8:28 pm
Posts: 13
I have beening working on TWAIN scanning program for a few month, and I have to say it is more complex that I have imagined. I prorgam my TWAIN application in two main parts, one is the core techniques of TWAIN objects acquiring, such as acquiring image to file, and converting acqured image to other image forms, and the other part mainly focuses on TWAIN device contols developing, which is the harder one.

PostPosted: Mon Mar 17, 2014 5:41 am 

Joined: Thu Mar 10, 2005 1:16 pm
Posts: 137
The best trick in TWAIN is to test if CAP_ENABLEDSUIONLY and CAP_CUSTOMDSDATA are TRUE. If so, then allow the user to create snapshots through your application.

Use DG_CONTROL / DAT_USERINTERFACE / MSG_ENABLEDSUIONLY to raise the drivers setup UI, which only supports OK and Cancel, as opposed to Scan and Cancel, which is presented by MSG_ENABLEDS.

Use DG_CONTROL / DAT_CUSTOMDSDATA / MSG_GET / MSG_SET to take snapshots and restore snapshots. This allows an application to access the full feature set of the driver (including custom capabilities) with the least amount of coding. Save the snapshots in files under the application's data folder, making sure to use the TW_IDENTITY.ProductName as a sub-folder, since the file contents are not defined by TWAIN and will differ from one scanner to the next. When the user wants to scan they merely have to select a snapshot and start scanning and the driver will use all the selected settings for that snapshot.

If either of these capabilities is FALSE or unavailable, then offer the user a small set of programmatic controls most useful to your application. Encourage your users to buy scanners that support CAP_ENABLEDSUIONLY and CAP_CUSTOMDSDATA.

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

All times are UTC - 8 hours [ DST ]

Who is online

Users browsing this forum: No registered users and 0 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group
[ Time : 0.104s | 13 Queries | GZIP : On ]