- Topics - 0
- Replies - 14
- Total Posts - 14
That was an exploratory work to open some headroom, I am swamped at the moment and have to patch up some work later in the datastream as I have concepting meeting this weekend, and – uh ….. Houston, … ? …. hello ?-! ( answer-back: ) “There are no problems, everyting is wonderful.”
That’s gonna get into SSL & PKI – running over absurdly mis-configured user-space. We ( my New Team Lead & I ) will be bringing up an Electronic Office, isolated from the paper office, good isolation subject to engineering grade work, review and testing. What my hope is here is that a scanner-driver, which may well and I expect it to, be callable through JNI – or any simple tool once I gain beginner grasp on the scope, nomenclature, and standard practices of the linkage issues …. surely we can pass a pointer to a few kilobytes or quarter meg or something, does not make sense to go through a context switch just to get 10-k of data.
Anyway: You have given me enough to work with now.
You can also implement different transfer modes (buffered, disk) that depending on the capabilities of the scanner will make the image available as already compressed JPGs, PNGs, TIFs, etc
I’m gonna model the entire project on HP Officejet J4680 Series, because I have one to do testing on, with the intent of making an efficient and safe driver across the entire HP small – mid size business products. With few hooks, a baseline or reference implementation upon which a coder, working in isolation and thwarted in attempts to get documentation can obtain enough info to get a functional and safe driver running, resistant to shell hooks.
I don’t want to scare people, obviously you are aware of the issues.
I’m gonna be swamped for a few days, I knew one call was a file creation call and the other was a minimal reference, what I need here is I have no familiarity with the codebase, so I do not know where to look for teh data trasfer modes that may have already been coded. It looks to me like it is what I think you are working arournd, a rather minimal implementation so if one wants to do graphics ( with the codebase ) then one will have to write some graphics.
The twist here is that I am experienced in this get-going phase, cannot resolve the above by looking at what I have unpacked.
EZTWAIN Classic (eztw32.dll) is a Windows DLL that provides an easy
interface to the TWAIN image acquisition protocol.
Great, where’s the sources? I see:
Timeout, visit: The Boiler Room
I’ gonna have to do some preliminary orientation on:
saved directly to G4 compressed TIFs and JPEGs. Unfortunately my company doesn't allow me to share code, but I can tell you that the implementation is short and mostly painless once you understand the concepts, as long as you're comfortable with C/C++.
… to that end I am buried in Jeff Heaton’s Introduction to Neural Networks for Java right at the moment…….
What I am trying to do here is program away the “betrayal” that comes when someone who is not informed on computer science and does not wish to be tries to do intake on a thousand printed documents does not have to contort in fear of:
“… the crucial question is whether, on the information available to the defendant when the contract was made, he should, or the reasonable man in his position would, have realized that such loss was sufficiently likely to result from the breach of contract to make it proper to hold that the loss flowed naturally from the breach or that loss of that kind should have been within his contemplation.”
Source:Kuofos v. C. Czarikow Ltd. (The Heron II)
Contemporary shrink wrap insists on going through INT13, masking off needed control codes and data-blocking being done like a dime-size hole in the wall, rather than idempotence employed to gate system calls to the ideosyncratc scheduler of popular commercial grade software so as to get an efficient data-block size of say 100k or quarter meg or whatever it wants so that it is the 802.11-G that is throttlling, not the device or the mainboard and process asscociated with intake.
I can spec some stuff here, now, and in perpituity: We take a raw image stream, do AI on it ( as OCR ) and take what can be recognized as a base character set ( okay, internationalization is here – still, we work to the benefit of technical people ) leaving styled document, as though it were never here, never discussed, only twiddly-diddly for people who want to be nice.
At some point, shortly there after, we proide what in computer science is called a filter interface, such that human intervention either by gui or by spell checker and context validation, is provided for the the programmer and Team Lead. It is part of the license that the code cannot be used save user accept the burden to implement some sort of sanity check at this point.
Then we give a text stream in Java, as Java’s Great Bean directs, free of system-dependent issues such as 0X0A / 0X0D letting 0xcafebabe rule from thereon……
Consider taking your next vacation in the Chinggis khaan home land.