Home › Forums › TWAIN Classic › Programmatic Printing with Kodak
- This topic has 2 replies, 2 voices, and was last updated 15 years, 9 months ago by kimman.
- AuthorPosts
We have to run a range of Kodak scanners without the Twain User interface. This includes endorsing (printing) on the documents.
I have reviewed the documentation included with the scanner (I142) which details the integration requirements specifically a document called ProgrammaticPrinting. I’ve had no luck 🙁 The only capability that is set with success is CAP_PRINTERENABLED. For all other capabilities I get an error code of SEQUENCE ERROR.
I also tried using the CUSTOMDS way ie use the U/I to get all the settings in UIONLY mode and then to restore these settings. Even then the printer settings dont seem to be effective.
Has anyone does this? Or have suggestions to get this working?
Thanks in advance
K
I’d have to dig mine out to make sure, but weren’t there a bunch of documents on the cd that came with your kodak scanner(s)? the ones I’m trying to remember were in the integrators kit and I seem to remember ‘printing’ in there. something to do with a whole bunch of ‘z’ padding the printer’s name… maybe. darn you, now I have to go dig out those docs… this will bother me all night.
otherwise no, I have no advise. just questions.
what triplets are you sending just before you get the seqerror?
.
Thanks for the response .. good timing indeed – I have just managed to resolve the issue thanks to help from the folks at Kodak. And so I do hope you didnt spend the night bothering about this.
There were two issues … the key one was a mistake in my code – the printer wasnt being enabled due to an incorrect alignment issue and so the cap sequence error was on account of that – since the printer wasnt enabled, it was ‘rejecting’ attempts to set the other printer related capabilities.
The other was an error in the documentation – the CAP_PRINTERWRITESEQUENCESTRING string must be provided in upper case and not lower case as shown in the documentation.
And so all’s well now.
Thanks
K
- AuthorPosts