Paul McKenzie
Paul McKenzie
Closing, as this issue has not been able to be duplicated with the HP Scanjet 7000.
DTWAIN version 5.1.0.6 has been released to address the issue of the Samsung driver.
I will keep this issue opened, even though DTWAIN has a workaround. This is for any other programmer's having an issue with this driver.
Looking deeper into the issue, here are the scenarios when scanning in duplex mode: ## For UI mode If the device user-interface (UI) is shown, then aspects of the device...
After further analysis, the feeder state functions for the HP 64-bit driver relies on the MSG_GETCURRENT capability operation instead of the traditional MSG_GET operation that existed for the TWAIN_32.DLL Data...
- I do not know Rust, so I cannot comment on the code. - What is the scanner model? - Are you scanning with or without the user-interface being shown?...
Also, I highly suggest you test your scanner with the DTWDEMO.EXE program, or at least one of the known demo programs. Since I don't know Rust, I have no idea...
This issue is related to #81
This aspect of how a driver is supposed to behave is defined in the TWAIN specification as "transitioning from "State 6 to State 5" when the driver detects that there...
From the DTWAIN logs, it seems to be that the scanner's driver did not fill in the information about the strip that is to be transferred to DTWAIN when acquiring...