Forum Replies Created
Here’s what I saw concerning the DEVICEEVENT :
No one implements this nice feature except Kodak, and the drivers (i200, i600) just send back an empty list of event … doesn’t help but why not …
Fujitsu, Panasonic and Canon simply return nothing (FAILURE/UNSUPPORTED).
So there is no way today to be aware of what happened during the scanning session.January 7, 2010 at 4:30 pm in reply to: Kodak Scanner Emulation – Problems with images from disk #25027
I’ll be very interested if you have an answer as well, I never found the way to make it work with image files …
ThierryApril 16, 2009 at 5:45 pm in reply to: How to enhancement the speed of data transferring? #24868
Now much of scanner has the sheet feeder or ADF capablities, to user, the speed is perference…
But to our application, we still use the standard TWAIN spec to recieve the data from DS, do you any suggestion to enhancement the recieving speed of data. or any capablities should be sent before enable DS.
Thank you very much.
What kind of performance are you trying to achieve ?
Most of time a high speed scanner (ie > 80 ppm) has a compression setting and memory transfer capabilities to help speeding up, but all depends on the computer linked to the scanner …
Most softwares can drive scanners at full speed …
Set CAP_INDICATORS to FALSE
JFL Peripheral Solutions Inc.
Your Expert Source of Custom Software and Services
for TWAIN Applications, Data Sources,
Peripheral Drivers and Support Software.
Thanks, I will take a look at this … 😉
1) the progress dialog, you can ‘request’ that drivers not show their progress dialogs. read heavily ‘request’, controlled with the bShowProgress parameter many devices that I work with honor the request and do not show their progress dialogs, but as with all things twain – some drivers just don’t play well with others. ymmv
Where do you set this boolean ?
Actually ShowUI at FALSE should be enough to stop display any dialog boxes from the driver (well in Kodak scanners at least) but it is not enough to stop showing the Fujitsu drivers transfers progress … (of course I can capture the Windows handle and hide it, but well, I’m tired of hacking everything, so if you have a better solution …).
Does Microsoft support TWAIN interface in 64 bit 2003 server?
My application works fine on windows,vista (both 32 and 64 bit) and also in 32 bit 2003 server. But not on 64 bit 2003 server.
Can any one provide information on that ?
Thanks in advance
Permissions problems with the driver you want to access ? Driver installation failed on Server 2003 64bits ?
Because, if it works on Vista 64, and Server 2003 32 bits it must work also on the mix of both (Server edition and 64 bits combination).
I cannot see why it couldn’t ..
A driver implementation error or an error in my application?
Hard to know, as it is vendor’s related behavior …
A good data source will give you a log file and enough feedback to be able to find if it’s an application error or not.
Some vendors expose capabilities because it is mandatory from TWAIN spec, but that doesn’t mean that you can change their value.
CAP_AUTOSCAN for example is a scanner specific capability controlling the behavior of the feeder so it could be read only.
Actually I started to run it through the DSM v2, and the DS (TWAIN VRS) still generates hundreds of exceptions and memory access violations, but it looks like it’s staying alive … so this will be my workaround for now …
describe the explosion.
I started by click on ‘1 Load/Open SM’, then, ‘2 Open Source’, and as soon as I release the left button, the application simply disappeared from the screen.
I have a scanner which supports CAP_AUTOSCAN, but when I try to set this capability to true, the DSM_Entry routine returns error coce 1 and condition code 0.
Does anyone know what the causes this error?
What’s the scanner and the driver version ?
I am using your API for scanning. I am not getting how to set property for multi-stream scanning. Please tell me any idea how can I set it.
This should be set on the TWAIN driver (I use Kodak scanners for that), it will generate the images you want in the order you want, you need to know (on the applications side) what you are doing (ie first image = color front, second = color back, third = bw front and so on).
and I guess you’re not having any luck with just letting the driver’s ui build valid CustomDsData for you. shame there is typically so little documentation available from the vendors for their custom caps.
Well that the way I use sometimes to track changes in the data structure returned by the GUI via CUSTOMDSDATA, but it’s time consumming (if this is the only way I do compare before and after settings changed).
Also to explain, for other people reading this thread, I cannot let the GUI opened, for security reason, we don’t want the user to change the settings as they are fixed and validated elsewhere for each scanner.
I don’t know why only Kodak gives all the documentation without having to ask for it … 🙄
but customdsdata hacks are fun.
What is not fun with this hack is to understand the sections significations and modify the rights ones without crashing the driver … 😉February 18, 2009 at 7:07 pm in reply to: Kodak TWAIN driver issue (all versions all scanners all OS) #24617
Where in Kodak did you get help ? Person/e-mail adress ?
Does anyone know how to get support on their drivers, I experience lockups problems when paperjams occurs as others have also. 🙂
I had support when I came to their offices in Rochester, they explained me how the images are sent by the driver in ‘no compression’ memory transfer, it was straightforward after that … 😉
I don’t know if I can mention names or emails here, but basically, most of time, someone from Kodak will see your question if post one, and will help you directly.August 14, 2008 at 9:02 pm in reply to: Kodak TWAIN driver issue (all versions all scanners all OS) #24615
I’ve finally get the answer from Kodak, and the image line (uncompressed mode) has to be padded to 32bits boundary before saving the data to a file (you should check the buffer size, if it is less than the expected size with 32bits alignement). And it works 😀
A big thanks to the guys at Rochester.