ScanSnap fi-5110EOX for Macintosh

[dfbills]

To followup- I just got the upgrade. It has been six months since first contact and now it actually works. Wow.

[BrokerDon]

How do I get my Fujitsu fi-5110C scanner to work in Acrobat 8 Pro running on OS X Leopard 10.5.3?

I installed the ScanSnap Manager v 2.2 L11 using the Japanese to Engish instructions but Acrobat doesn't recognize the scanner (the ScanSnap icon in the Mac menu bar has a red "X" through it even after inserting a document and hitting the Scan button on my fi-5110C). My guess is Fujitsu doesn't have an OS X "Leopard: TWAIN driver so I'll need to use some other software. Will Fujitsu's Japanese/U.S. localized ScanSnap software scanning software do the trick?

Please let me know ASAP... This is a serious roadblock to moving to Mac from a PC.

[dfbills]

As far as I know, the Fujitsu mac driver isn't actually TWAIN at all. It really only works within the Fujitsu software.

[mclbruce]

Quote: Originally Posted by BrokerDon How do I get my Fujitsu fi-5110C scanner to work in Acrobat 8 Pro running on OS X Leopard 10.5.3?

TWAIN-SANE might work: http://www.ellert.se/twain-sane/

Scantango might be a good workaround for scanning to PDF: http://www.scantango.com/

[duffman416]

WOW, I got my S500 going on my Macbook Pro with Leopard. I followed the instructions and ran into the snag about the newer English ScanSnap_V22L11 file causing problems with the Apply button and the wacky profiles that didn't work right. Oh yeah, that was fun.. I was searching like crazy for the V21L11 english file from the Fujitsu site, and was about to give up until I figured I would try and replace one character in the URL on their site and give it a shot. BAM!

The file is there! It's just not hyperlinked on the Fujitsu website! Just copy the link and replace the '22' with a '21' in the URL and you can download it!

Took the english lproj file from the old English 21 file and it works like a champ!!

I hope this helps anyone who ran into the problem with the English 22 version!

(RANT) Why Fujitsu won't release an English version for their non-M scanners to run on Mac's is absolutely beyond me. I mean come on, you let a Japanese version float out there but can't get the English one going? I have to spend 2 hours backdoor hacking this thing to get it to work? Sheesh... How many people have switched from PC to Mac in this country and then are SOL with their old scanners? Low blow, especially when you give one country a working version..

-Duff

[flomrudi]

judging from the rave reviews everywhere I was expecting to be overjoyed but I am actually frustrated with it. I cannot get this scanner to OCR automatically after every scan. I have the scans opening in acrobat pro however I have to manually run OCR for everything. the reviewers say that there is a way to do auto OCR with this scanner. I learned that this does not come with the AABBY OCR software, is there a way to buy AABBY for scansnap, or to get this S300M to auto OCR? there'd better be! grrrr!

[dfbills]

You can get finereader directly from AbbyySoft:

http://abbyydownloads.com/Scansnap_M...-08-06.dmg.zip

Note this only works with ScanSnap scans.

[raymoreno]

Hello -

Thank you! Thank you!

I'm a newbie here but wanted to say thanks again. I carefully read each of the posts. The copy/paste of each of the english files was tedious but worth it. I have english localization after a reboot.

Does anyone have camngnp223's installer file that would automate this on my other computer?

Ray

[JoeInStl]

I've had the S510 for my PC for a year and I love it. I just switched to a MacBook Pro and I'm trying to get the PC version to work on my Mac.

Before I found this message I just installed the latest Mac (English) version of the software and of course it didn't work. I was excited to read some of the posts above where some people have done what I'm trying to do.

I was trying to use their step by step instructions but I ran into a snag. I tried to install the Japanese version but the installer stops and says I already have a new version of the software on my volume. I've already tried to delete the software by dragging the ScanSnap folder into the trash. I also downloaded AppTrapper to see if that could get rid of any hidden files. No luck so far.

Anyone have any ideas how I can get the Japanese (older) software installed?

Thanks for any help.

Joe

[bbh]

I had the same problem: couldn't install the older drivers because they detected a newer driver. Simply go to ~/Library/Receipts and /Library/Receipts to ensure that you delete the old package receipt. it worked for me!

[chines12]

Hello,

Brand new here. Have 5110 Scansnap that I am trying to use with Mac 10.4. Installed the new Mac driver, but the Icon on the tray has a red circle with a line through it. My Mac doesn't seem to recognize the Scansnap as a Scanner, just some type of USB device. Any suggestions would be helpful.

Thanks,

Christine

[EvilDNA]

Ok. I've read all the threads. Looking for some guidance. I want to get the ScanSnap 300 or 300M. The issue is I want one piece of S300 hardware that will work in the Mac and Windows OSes.

Specifically, on a Mac Book Pro (10.5) in OSX and Paralles. The safe bet is to go with the S300M running in OSX and drag and drop my PDFs to Windows. But . . .

If I want the scanner to work in the Windows OS as well as OSX, the question is:

Can the S300M hardware run on a PC w/ the S300 software?

I've read about getting the ScanSnap PC scanners working w/ the Mac Software w/ the localization changes, however, I am Mac most of the time and PC some of the time. Added, I don't any scanner at the moment.

Does anyone have an opinion that would contradict going w/ the S300M and hoping it 'just works' w/ it's PC counterpart software in the Windows OS?

Like I said . . I just want one S300 scanner hardware to run on Windows and Mac. Crazy, I know.

Thanks,
Evil

[bstad]

EvilDNA - I would suggest the PC version, and use Scantango on the Mac. The only thing I can tell you lose is the ability (and I just may not have figured out how yet) to do auto-paper-size. From what I can tell you have to give Scantango the exact size, though you can create custom sizes. I've even done one for those insanely-long Fry's receipts! I just had to create a 3x29 document size.

[mrglsmrc]

i use some software from devon technology called devonthink pro. they have a version called devonthinkprooffice that uses scansnap technology on a mac and recommend specifically a certain fujitsu scanner in leopard.
if any of you guys go to devon's forum page,
http://www.devon-technologies.com/se...=scansnap&r=10
you should get some answers about scansnap and mac. from what little i understand it was apple's fault that scansnap didn't work for a while. apple changed a core technology and later switched back.
-marc

[jamesr219]

Hello,

The versions on the current site are no longer working. Can someone please send me a copy of V21L11 so I can english-fy it? Can't seem to find it anywhere and when I english-fy the current version the apply button is in wrong spot and no settings can be changed!

Please PM me if you have it..

Thanks,

-jr

[racerx90]

Well, I took a shot at getting the M300 scanner working under OS X on a MAC last night (since I have the PC version of the scanner, but I now have a MAC laptop after changing jobs.) I will say first I haven't looked at this in a ton of detail, but I was playing with it a little to at least get an idea what needs to be done to probably get it working (I'm hoping someone else on the forum in the same situation as me will know a little more about disassembling code on MACs than I do.)

1) Took the 300M_0B00.nal firmware file from the MAC version of ScanManager (you can find it in show package contents->resources->firmware) and copied it to my VMware installation of Windows OS (under c:\windows\ssdrivers\*).

2) Renamed the file to 300_0B00.nal (so ScanManager PC would find it since in the code it just looks for 300_* (pc) and 300M_* (mac) in a certain directory). I moved the original 300_0C00.nal to 300x_0C00.nal (just a different name so it wouldn't be found.)

3) Gave the USB device (while the scanner was plugged in and on) to the VMware Windows installation and let it discover and load the firmware file. Sure enough it did and both ScanManager and the scanner were on-line and ready (even the About ScanManager dialog box saw the scanner as a S300M now!)

4) Next I detached the USB device (the scanner is still on at this point) from VMware and gave it back to the host OS (MAC OS X.)

5) Finally, I started ScanManager on the MAC and it recognized the scanner and I could scan documents at will. No more red cross on the icon and everything worked perfectly!! I even checked the hardware device list on the MAC and it saw a S300M (even though the scanner was an S300!)

What I found out from this:

* There's essentially *NO* difference in the hardware between the S300 and S300M given the firmware has to be loaded first anyway (other than the DeviceID and Device Name which are pre-programmed into a ROM.)

* Before the loading of the MAC firmware file, the S300 scanner identifies itself on the USB Bus with PCI VendorID: 0x04c5 and DeviceID: 0x1156 (this is the default even without a firmware file loaded (meaning the device is waiting for code an the blue light is blinking.)

* Once the new firmware file is loaded (solid blue light) and the scanner "boots-up" then the DeviceID is changed to 0x117F (which is for a 300M.) Also the Device Name changes from ScanSnap S300 to ScanSnap S300M (I scanned the firmware image file with a hex editor and all this is in there.) So the new firmware image file will override any pre-programmed information on the device (which makes me wonder if the device has an eeprom that can be reflashed.)

The problem I'm faced with is how to get ScanManager under MAC OS X to load the S300M firmware file on the S300 (which identifies itself with DeviceID: 0x1156 instead of the 0x117F id it's looking for.) No small task without the source code.

Here's what I've tried:

* SANE - while I can get the S300 scanner working under SANE just fine with the MAC, if I give it the MAC S300M firmware file it doesn't "re-initialize" the device like ScanManager does so the device doesn't come up as DeviceID: 0x117F like I want it to (perhaps I could dig in the code to see if there's anything stray in there which might help (or contact the author.))

* Also, I digged through the package contents of the ScanManager MAC application and loaded up the binary in a hex editor and did some searching through the code. I was able to find in numerous locations where the code is looking for the DeviceID 1156 and 117F (or 7F11 since the endian-ism is reversed in the executable! I tried changing the 1156 to something else in case it had a check preventing it from working and then changed the 117F to look for the 1156 without much success. I tried many combinations, but without a disassemble of the binary that I can easily read I suspect I'm wasting my time here.

In addition, I tried editing where it looked for the Device Name S300M and swapped it with S300 - still no luck. I need to look through the code and see what it's doing when it identifies the scanner and then loads the firmware file.)

I suspect this could be patched with the right tools (I use to do this all the time in Windows using PE Explorer and a hex editor.) However, I'm new to OS X so I'm not too familiar how most of this stuff works which is where I'm struggling right now.

I'm hoping someone else who also has this scanner or even maybe the S500 or S510 could help out. I suspect we might be able to get the new version of ScanManager that doesn't work with those devices to work with a few patches. We just need to figure out what's in the code preventing them from working - I'm sure it will work with the right patches (I doubt the checks are very complicated.)

FWIW: Here's a partial list of DeviceIDs and scanners that I was using to locate the right code bits given I didn't have a disassembly of the code:

0x1156 - S300
0x117F - S300M
0x10FE - S500
0x1135 - S500M
0x1155 - S510

Thanks!!

Regards,
E.

[jamesr219]

Quote: Originally Posted by racerx90 Well, I took a shot at getting the M300 scanner working under OS X on a MAC last night (since I have the PC version of the scanner, but I now have a MAC laptop after changing jobs.) I will say first I haven't looked at this in a ton of detail, but I was playing with it a little to at least get an idea what needs to be done to probably get it working (I'm hoping someone else on the forum in the same situation as me will know a little more about disassembling code on MACs than I do.) 1) Took the 300M_0B00.nal firmware file from the MAC version of ScanManager (you can find it in show package contents->resources->firmware) and copied it to my VMware installation of Windows OS (under c:\windows\ssdrivers\*). 2) Renamed the file to 300_0B00.nal (so ScanManager PC would find it since in the code it just looks for 300_* (pc) and 300M_* (mac) in a certain directory). I moved the original 300_0C00.nal to 300x_0C00.nal (just a different name so it wouldn't be found.) 3) Gave the USB device (while the scanner was plugged in and on) to the VMware Windows installation and let it discover and load the firmware file. Sure enough it did and both ScanManager and the scanner were on-line and ready (even the About ScanManager dialog box saw the scanner as a S300M now!) 4) Next I detached the USB device (the scanner is still on at this point) from VMware and gave it back to the host OS (MAC OS X.) 5) Finally, I started ScanManager on the MAC and it recognized the scanner and I could scan documents at will. No more red cross on the icon and everything worked perfectly!! I even checked the hardware device list on the MAC and it saw a S300M (even though the scanner was an S300!) What I found out from this: * There's essentially *NO* difference in the hardware between the S300 and S300M given the firmware has to be loaded first anyway (other than the DeviceID and Device Name which are pre-programmed into a ROM.) * Before the loading of the MAC firmware file, the S300 scanner identifies itself on the USB Bus with PCI VendorID: 0x04c5 and DeviceID: 0x1156 (this is the default even without a firmware file loaded (meaning the device is waiting for code an the blue light is blinking.) * Once the new firmware file is loaded (solid blue light) and the scanner "boots-up" then the DeviceID is changed to 0x117F (which is for a 300M.) Also the Device Name changes from ScanSnap S300 to ScanSnap S300M (I scanned the firmware image file with a hex editor and all this is in there.) So the new firmware image file will override any pre-programmed information on the device (which makes me wonder if the device has an eeprom that can be reflashed.) The problem I'm faced with is how to get ScanManager under MAC OS X to load the S300M firmware file on the S300 (which identifies itself with DeviceID: 0x1156 instead of the 0x117F id it's looking for.) No small task without the source code. Here's what I've tried: * SANE - while I can get the S300 scanner working under SANE just fine with the MAC, if I give it the MAC S300M firmware file it doesn't "re-initialize" the device like ScanManager does so the device doesn't come up as DeviceID: 0x117F like I want it to (perhaps I could dig in the code to see if there's anything stray in there which might help (or contact the author.)) * Also, I digged through the package contents of the ScanManager MAC application and loaded up the binary in a hex editor and did some searching through the code. I was able to find in numerous locations where the code is looking for the DeviceID 1156 and 117F (or 7F11 since the endian-ism is reversed in the executable! I tried changing the 1156 to something else in case it had a check preventing it from working and then changed the 117F to look for the 1156 without much success. I tried many combinations, but without a disassemble of the binary that I can easily read I suspect I'm wasting my time here. In addition, I tried editing where it looked for the Device Name S300M and swapped it with S300 - still no luck. I need to look through the code and see what it's doing when it identifies the scanner and then loads the firmware file.) I suspect this could be patched with the right tools (I use to do this all the time in Windows using PE Explorer and a hex editor.) However, I'm new to OS X so I'm not too familiar how most of this stuff works which is where I'm struggling right now. I'm hoping someone else who also has this scanner or even maybe the S500 or S510 could help out. I suspect we might be able to get the new version of ScanManager that doesn't work with those devices to work with a few patches. We just need to figure out what's in the code preventing them from working - I'm sure it will work with the right patches (I doubt the checks are very complicated.) FWIW: Here's a partial list of DeviceIDs and scanners that I was using to locate the right code bits given I didn't have a disassembly of the code: 0x1156 - S300 0x117F - S300M 0x10FE - S500 0x1135 - S500M 0x1155 - S510 Thanks!! Regards, E.

Great Approach. I knew that it could be done somehow changing the device ID which is reported on the USB bus..

So, to recap. All you have done is just taken the ROM from the 300M version, and tricked the windows version into loading that ROM into the 300 thus turning it into a 300M?

I have a fi-5110EOX2, so I don't know if this will help me. Maybe the fi-5110EOX2 ROMs are in there too..

anyways, nice work. Thanks for sharing!

-jr

[racerx90]

Quote: Originally Posted by jamesr219 So, to recap. All you have done is just taken the ROM from the 300M version, and tricked the windows version into loading that ROM into the 300 thus turning it into a 300M?

Yes - exactly. I should note that the Windows ScanManager is also locked by the DeviceID's (meaning once the MAC rom was loaded it wouldn't re-initialize the scanner if it was disconnected.)

So if you have an S300M - then it wouldn't work on a Windows system and vice-versa with an S300. You'd need to trick the MAC ScanManager to load the Windows ROM to get the DeviceID's reset so it looked like a S300 in order for it to work.

Essentially, either scanner isn't interchangeable between OS's so you can't buy one and expect it to work on both OS's (meaning it's just a software lock not a hardware difference other than the physical "color" of the device itself which doesn't affect operation.)

I even disassembled the scanner and checked to see if the eeprom was socketed (I would have just re-flash it with my burner), but it's soldered to the mainboard. Honestly, I'm not that interested in trying to go through the effort of removing it since I don't own the right type of iron to remove it easily.

Quote: Originally Posted by jamesr219 I have a fi-5110EOX2, so I don't know if this will help me. Maybe the fi-5110EOX2 ROMs are in there too..

No, it won't since the fi-5110EOX2 has a built-in ROM, but I still think it will work with a change to the ScanManager binary. I don't think it matters on the ROM image itself but what the DeviceID is when ScanManager looks at it. So with the right patching to the binary, I still believe it will work (the code isn't protected and it can be disassembled and binary patched.)

I finally got IDA Pro Disassembler running yesterday and was looking through the ScanManager binary, but it's not obvious to me right now without setting up the MAC server so I can debug the binary in real time to see the code path it's taking (everything I'm doing so far I *think* should work, but it's not.) (It's kind of weird to do this since I have to disassemble it on my Windows system (running under vmware) and use a server running on the MAC side to feed the code over to it which I haven't had type to setup yet.)

I really need to find a couple of spare hours to step through the code path with each of the ROM versions loaded from both scanners (S300 & S300M) to what see the correct code path needs to be then patch around it. It should be straight forward to patch for all the different scanners once you figure out the correct flow of the code (meaning you could get it working for S300, S500, S510, fi-511EOX2, etc.. once you know what needs changing.)

Regards,
E

[racerx90]

I tried working on it this weekend for a little while, but I didn't get too far. IDA Pro would connect successfully to the mac server using 32-bit mode (it would just completely crash in 64-bit mode - there's definitely some issues with it! and I'd get a process list which I could attach to and get a complete disassembly of ScanSnap Manager (which is a good start.)

However, when I tried to step through the code the machine would just crash (system had to be rebooted.) I tried it 3 times and all 3 times during the first step through the code my laptop crashed and had to rebooted. (It reminds me of the OS to airplane analogy where the plane crashed just after take-off killing all the passengers and the black box recorder couldn't be found so it couldn't be explained!

I also tried using gdb under Xcode (which worked just fine and even allowed me to step through the code without an issue), but without a working copy of the disassembly or the original source code to reference where you are in the code it was next to useless to understand (I admit I'm not that skilled.) I couldn't trace or step through any of the calls like I see when using IDA Pro (at least it wasn't obvious to me how to do it like it is with IDA Pro.)

I'm going to try to run IDA Pro on another system (not sure that's going to help it though because the crash is coming from ScanSnap Manager on the MAC side not from VMware) and see what happens. I could also download IDA Pro 5.30 as I'm using the older 5.20 version - maybe this will fix it, but not sure.

I'm up for any ideas if anyone has some. I haven't been able to find any other utilities which can give me a disassembly and allow for realtime debugging on the MAC (not to say that others don't exist.)

Regards,
E.

[craigl]

I'm the author of ScanTango.

ScanTango does Auto Size - you simply specify (or create) a page size larger than the page sizes you will be scanning and then in your scanner setup you select the Auto Crop filter. You can even create a custom Auto Crop filter to tweak how sensitive it is to margin notes, etc. You can also use other filters such as deskew, despeckle, and rotate.

ScanTango supports ALL of the ScanSnap scanners (even the PC models) on the Mac. The latest version allows you to try ScanTango with your scanner before you buy. It also supports most of Fujitsu's workgroup scanners such as the newer 6130.