![]() Getting information on how to drive scanners "command sets" was often a problem. ![]() I believe all the scanners I did write drivers for are supported by the open source Sane project, so how to drive them is no longer a secret. The very expensive scanner of 1994 is now easily outclassed by low price models. Some of the major manufacturers are now out of business. The code would probably be of little use anyway. Many were written under non-disclosure agreements. I have problems supplying source code for all the drivers. The final development was USB support for both Castle and Simtec USB cards. Thanks to Gareth Long, parallel port support was added. However the opposition in the Acorn world in the form of Irlam Instruments had been quick witted enough to see what was wrong with the raw results from the Epson scanners and fix it.Īs a result of this I brought out "TWAIN 2" - drivers with a better user interface and many features - including better image scaling - the cause of the grief with Epson scanners. Where I went wrong is that many manufactures achieved better quality by processing the data coming out of the scanners - they did not provide any information on what that processing consisted of. I came a cropper when Alan Wrigley reviewed some of my drivers for Risc User magazine and said they were of poor quality. Just the thing to show off how expandable the new RISC PC was. One highlight was the Nikon Coolscan, a slide scanner built to fit in a 5.25" disk drive bay. Realistically most RISC OS users would only use mid-price models and writing drivers for expensive scanners wasted time that could have been spent on improving the other drivers. To my credit at one time RISC OS supported more scanners than some other operating systems. I ended up providing libraries for BBC Basic. There was not huge interest in the RISC OS world in implementing it. TWAIN relies on applications understanding the protocol. Of course when I originally implemented it on RISC OS the idea was that it would make life easy for people moving applications from Windows to RISC OS. Years later when I ported some of my software to Windows, the TWAIN side of things worked with no modification. I recall being told at one of the Harrogate shows by Charles Moir (of Computer Concepts) that I should stop being silly and admit that what I had implemented was not TWAIN. Folders for sources and modules for the code. TWAIN consists of sources (scanner drivers) and a source manager. ![]() I did have contact with them, but they had little interest in an implementation for RISC OS (an unheard of operating system in a country far away).Īnyway I bought the TWAIN software development kit and I implemented TWAIN for RISC OS. There was a cross industry body that published the standard and maintained it. TWAIN was a laudable effort to provide a standard interface to scanners from applications. A Windows driver is no help on RISC OS computers. It's not so simple, the TWAIN driver is only glue between the scanner and applications on a given platform. Epson and Canon flat bed scanners were already popular in the Acorn world, support for them followed rapidly.Ī common misapprehension is that if a TWAIN driver exists for a scanner then all ones problems are over. The Integrex scanner used the HP Scan Jet command set, so that was the first model supported. In those days scanners were a neat idea, it was the era of fax modems, they fitted together well. Acorn put us in contact with one another. In 1993 Integrex wanted to enter the Acorn market with a low cost scanner and I'd written to Acorn suggesting that I implement the TWAIN scanner driver protocol.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |