Installingthe scanner drivers from the link on the bottom of this page will install the latest OEM VRS, TWAIN Data Source, ISIS Driver and WIA/STI drivers for a Kodak Ngenuity Scanner. For more information please read the Release Notes posted on this page.
This firmware update has been provided to allow the conversion from the Bell and Howell (BBH) version of the Ngenuity Scanner to a the KODAK version of the Ngenuity Scanner or the upgrading of firmware to the latest version on a Kodak Branded Ngenuity Scanner.
Please note that converting the scanner to KODAK branding will require you to update to the Kodak version of the Users Utility and scanner drivers by installing the KODAK Scanner installation CD version 1.0 or higher. A zipped version of this installation CD has been provided on our website for free download.
Installing the scanner drivers from the link on the bottom of this page will install the OEM VRS, TWAIN Data Source, ISIS Driver and WIA/STI drivers for a BBH branded Ngenuity Scanner. For more information please read the Release Notes posted on this page.
Please note that the User Utility and drivers on this installation CD will only work with a Bowe Bell and Howell (BBH) branded scanner. If your scanner is Kodak branded these drivers will not work with your scanner. Drivers for a Kodak branded Ngenuity scanner have also been provided as a download on this website.
Note: WINDOWS 7 is only supported by the KODAK Branded Ngenuity drivers. You can update the Bowe Bell and Howell branded scanners to support WINDOWS 7 with a firmware update. See the KODAK Branded Ngenuity Scanner Firmware section for the firmware and installation instructions for this update.
This firmware update has been provided to allow the updating of the firmware on a BBH branded Ngenuity scanner. The update will correct some known issues with this firmware. There are no new features added in this update.
A patch is a pattern of parallel, alternating black bars and spaces that is printed on a document. Kodak Scanners which have patch reading capability can recognize patch documents and automatically assign a document image level, increment the document image address, or perform Color on the Fly functionality.
Kodak Alaris is a leading provider of information capture and intelligent document processing solutions that simplify business processes. We exist to help the world make sense of information with smart, connected solutions powered by decades of image science innovation. Our award-winning software, scanners, and professional services are available worldwide and through our network of channel partners.
Privacy Notice Legal / Site Terms California Notice at Collection Do Not Share My Personal Information
2024 Kodak Alaris Inc. TM/MC/MR: Alaris, ScanMate. All trademarks and trade names used are property of their respective holders. The Kodak trademark and trade dress are used under license from Eastman Kodak Company.
As far as I know, Kodak i4850 has the option to integrate with ISIS driver so it should work well with Laserfiche ScanConnect. Kindly appreciate if anyone can confirm me with it and share some experience with me if you have used Kodak i4850 or any newer Kodak scanner. Thank you!
Unless a customer needs a specific capability only provided by ISIS drivers, we strongly recommend using TWAIN drivers with Laserfiche because our support case data shows they are significantly more reliable and less fiddly. I wouldn't use ScanConnect/ISIS drivers unless that's your only viable option. I don't want to give the impression that ScanConnect/ISIS is bad, only that all else equal, the TWAIN option is better and you shouldn't use ISIS support as a decision criteria by itself.
If you do have to use ScanConnect/ISIS, while I don't see that specific model on the Laserfiche ScanConnect 8.3 Supported Scanners list, many other Kodak models are. The list hasn't been updated in almost three years and should be interpreted as "what we had the opportunity to test with" rather than "only scanners on this list work". The more up to date Supported Scanners list shows that we certified the Kodak i4600 with ScanConnect back in 2010. I'm guessing that's a predecessor in the same hardware family that plausibly shares a driver lineage with the i4850.
The reason why they use ScanConnect/ISIS driver is because they have get used to it and are reluctant to change since it has been working as always. I will review their solution design to see if it is possible to change to TWAIN so that it is more stable on Laserfiche side. If eventually TWAIN is not a viable option in their case, I will let them know we have certified Kodak i4600 which is the same hardware family that is likely to share the same driver lineage with Kodak i4850. And we will also request a test unit from Kodak to run through integration test with their solutions.
If they're reluctant to change because they're used to the ScanConnect/ISIS driver and it's been working fine, I don't see any issue testing it out with the i4850 and using it if you don't encounter any issues. I'd just also test with TWAIN so you can have that as a validated backup option if you do encounter any issues with the ScanConnect/ISIS driver.
I have a Kodak ESP C310 printer that I tried installing on my computer (Ubuntu 10.04), but it wouldn't even recognize the device. So, I went on the Kodak site and talked to a representative online (after Googling and not finding anything helpful), and all they told me was that Kodak drivers do not support Linux or any form of Linux, like Ubuntu. I asked them if they ever would, and the person told me they were working on it. Well, that doesn't help me at all. Has anyone been able to work around this problem of Kodak not supporting Linux? I don't want my printer to go waste, I need it.
As you've said, Kodak don't currently distribute Linux drivers for their machines, but the internet is a vast place, and, thanks to the amount of more advanced users using Ubuntu, their are some available.
The work-a-round I've used to print from my Ubuntu linux system to my Kodak ESPOffice 2170,is to set up "eprint" on the 2170. The setup process creates an email address of the
fo...@kodakeprint.com. When you email to that address it will:1) print the email2) print any attachment (MS Office) or pdf file to the printer.
I chose the Ubuntu 64bit package (despite it saying it was for distro 14.04 LTS). It DL'd a .DEB package, and all it took was a doubleclick on the DL'd file in the Download folder to launch and install. I then brought up the bottom left corner Menu, Applications, Administration, Printers and set up a new network printer. The rest was easy and intuitive. Test page successfully printed.
You can't install drivers via Crossover - Crossover sits at the application level on your Operating System, whereas drivers hook into the kernl, below the application level. If your printer has Mac drivers (i.e. you can print to it using a mac-native app), Crossover should be able to use it since CX uses your Mac print drivers.
can you print from Notepad? To try this, go to Crossover's Programs>Run Command menu. Select your Forte Agent bottle, and then type "notepad" in the command field. Click "run". type some random text, and then go to file>print in notepad and try printing to your Kodak printer. Does this work?
You can't install drivers via Crossover - Crossover sits at the
application level on your Operating System, whereas drivers hook
into the kernl, below the application level. If your printer has Mac
drivers (i.e. you can print to it using a mac-native app), Crossover
should be able to use it since CX uses your Mac print drivers.
can you print from Notepad? To try this, go to Crossover's
Programs>Run Command menu. Select your Forte Agent bottle, and then
type "notepad" in the command field. Click "run". type some random
text, and then go to file>print in notepad and try printing to your
Kodak printer. Does this work?
If it freezes, what about a newly created created bottle, set to winXP? Does notepad print from that bottle? If so, you might be seeing some kind of odd bottle corruption, probably caused by an update, which would mean that your best course of action is to delete that bottle and re-install the Forte Agent program into a new one.
Alternately, you could try archiving the bottle (Configure>Manage Bottles>Advanced>Make Archive), then delete the present bottle and restore the archive, which is "as good as" re-installing in many situations, and this may be one of them if it turns out you can print in a newly created bottle but not the old.
At this point the best thing I can think of would be install a new copy of Agent into a new bottle, and then copy the pertinent data from your old bottle into the new. You can get to the interior of each bottle by highlighting a bottle inside Manage Bottles and heading to Advanced>Open C: Drive in Finder.
I've forgotten how to install Forte Agent. I see it's not a supported application. I got the installation to say "Will install from HBrazee > Downloads > cnet_agentenu600-1186_exe.exe, but it won't proceed from there. (I'd rather install by just copying the agent directory that I copied from my Windows partition).
If you're at ""Will install from HBrazee > Downloads > cnet_agentenu600-1186_exe.exe" in the Install Software menu but you can't click "install" to proceed, you might not have "other application" selected from the list of applications, as per these instructions:
At any rate, given your "no Windows program configured to open this file" errors on attempting to launch any app installed in Crossover, I'd say your Crossover install is pretty well hosed. I would not recommend using Time Machine as a restore method for Crossover in this particular case. It sounds like Crossover's various libraries are out of order, and using Time Machine will probably just make things worse - you're likely best off completely removing all Crossover components from your system
3a8082e126