![]() ![]() I asked David if he had some explanation that would reconcile this disparity, He added: The only problem here is that around a dozen readers have since written to say that they are in fact successfully using OmniPage Pro with DeskScan drivers. Why? Basically, there are too many problems with this driver to make it usable for Pro. Although DeskScan was available when Pro 8 shipped, we didn't support it, relying instead on the existing Pixel drivers. Pro has to query the scanner through the TWAIN source to get its capabilities- scanner bed size, resolution, color format, and so forth. ![]() Unfortunately, many manufacturers supply TWAIN sources that (when used through the "private" interface Pro uses, as opposed to the "public" "Acquire." type interface), are, shall we say, problematic. We added TWAIN support in Pro 8 to address the problems with Pixel drivers. This didn't happen with all Pixel drivers - Epson drivers, for example, seem to work - but it did happen with HP and Nikon drivers. Dropping back to < 8.5 cured the problem. The problem seemed to be the Pixel drivers - simply clicking on the driver in the Chooser (although Pro 8 doesn't use the Chooser as a selection mechanism, selecting a driver in the Chooser initializes it and is useful as quick test) would freeze or crash the system. When OmniPage owners started moving to 8.5 and 8.5.1, we received a flood of reports of scanners not working, which we were able to easily duplicate here. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |