The Robservatory

Robservations on everything…

 

Fujitsu ScanSnap software and the 64-bit-only future

A fair number of my apps are still 32-bit—see how many you still have—though many I don’t really care about all that much. But there’s one suite of apps that I use every day, usually multiple times a day: Fujitsu’s ScanSnap apps. This is the software bundled with the ScanSnap ix500 scanner.

While Fujitsu has been good about updating their software in the past, I was a bit concerned about the upcoming 64-bit transition. So I both tweeted at them and sent them an email. I haven’t seen a reply on Twitter, but a (clearly form letter) reply to my email is at least somewhat encouraging:

There is no problem in the behavior of the application or the OS concerned. The message is only inform that the application needs to be modified for compatibility with next-generation macOS (which should be available near the end of the year). PFU is going to resolve this, but the resolution date is not set yet. In the meantime, please continue using the latest version of the software available.

This blurb was obviously prepared as a response to those complaining about the new 32-bit warning dialog in macOS 10.13.4, but it does seem to address the longer-term question: Fujitsu is planning to “resolve this,” which hopefully implies 64-bit versions are in our future, though at some not-yet-disclosed date.

There are very few things in my workflow that I couldn’t replace…but replacing my ScanSnap and everything it does for me would be quite difficult. Hopefully we’ll see a 64-bit ScanSnap suite before this fall’s deadline.

18 Comments

Add a Comment
    1. I’ve never used ScanDrop, and had to search to see what it did: It appears to send scans directly to various cloud services? If so, you could easily replicate this, I think, using Hazel and a watched folder—just have Hazel copy new files to your cloud service when they appear. Or maybe even a Keyboard Maestro macro than runs each time you scan? (That’s how I handle naming my scanned files.)

      Then again, I don’t know anything about DropScan, so maybe I’m missing some key element of its functionality.

      -rob.

  1. Ah, that’s a good heads up for me. I use an ageing m300 scansnap and I’m almost certain they won’t bother supporting that any more.

  2. After many recommendations on podcasts (MPU!) and blogs I bought an IS1300 some years ago. A nice scanner that served me well. Until I upgraded Mac OS and it turned out the IS1300 was not supported anymore by Fujitsu. For a moment I thought about buying a new Scansnap. But after all I decided to start using my Canon multifunctional for scanning. It’s slightly less convenient than using the Scansnap, but I refuse to replace otherwise perfectly functioning (and rather new) hardware just because the manufacturer is not updating their software for a particular model. I’m quite disappointed in Fujitsu’s lack of support.

    1. The S1300 was discontinued and not supported in newer ScanSnap software, but it does still work perfectly fine for me in macOS 10.13 using ScanSnap software version 3.2 L91. The download link on their site is for 3.2 L80 but then in the tool pick Help > Online Update and it will get L91, the last version available for that scanner.

      I guess if 10.14 requires 64-bit then we are out of luck. Until then the S1300 is perfectly fine.

    1. I haven’t heard anything, and I haven’t seen any updates in the app. The good news is that we now know 32-bit apps will continue to run once 10.14 is out—albeit with the warning. This gives at least an extra year’s worth of usage.

      -rob.

      1. Glad to hear 10.14 can run 32-bit apps. But my ScanSnap software is the last 32-bit app I have and I think it may be slowing down my entire 10.13 machine. I’m very keen to get some 64-bit goodness.

  3. I’ve heard from others that it has very slow performance in Mojave. Anyone here experience that?

    1. I haven’t yet updated my main machine—and may not do so ever unless they fix the automated app permissions snafu—so I can’t say. Hopefully someone else can chime in.

      -rob.

    2. I ran ScanSnap under Mojave and at first thought it was just slow..but it turns out the OCR was not working at all. The Recognizing Text dialog box comes up, stays on screen for a long time and when it’s finished, the scanned doc is NOT searchable. This is a definite show stopper for me when planning to upgrade to Mojave.

  4. After installing Mojave, couldn’t I partition the hard drive and install High Sierra on that to run any 32-bits that I may have need of?

    1. You could, though rebooting is a pain. It might be easier to buy VMware or Parallels and install a virtual macOS—this should work unless your 32-bit apps are graphically intense and really demanding of the CPU.

      -rob.

  5. I just upgraded to Mojave, and my Scansnap Manager stopped working. It will load, but crashes as soon as you hit the scan button. I called Fujitsu and spoke to a very friendly and sympathetic guy who told me the Scansnap Home program is all they have that will work with Mojave. It does not have a preview window, and some other small functions I could live without, but the inability to rename the file I just scanned is a show stopper for me. In order to use it, you have to pick a destination file and give it a name before you scan it. He offered to pass my thoughts on the matter up stream, but there is no replacement for this in the future. I will experiment with it for a while, but I’m afraid this is the end of a long and beautiful relationship with this scanner.

    Jim

    1. I’ve been running Mojave since the GM, and it works fine for me. Maybe you need to reinstall the software; or maybe there are some system permissions that aren’t set right.

    2. Jim:

      I installed Home in a virtual machine so I could test it. You do not have to name a file first, though it will require some customization to get what you want: Set up a new “Verify and Save” profile, and it works much like it did before, popping up the same post-scan dialog box.

      My issue with it right now is that if you scan something as a receipt, you can’t OCR it, but if you scan it as a document, you can’t extract the date from the receipt, which is a cool new feature.

      -rob.

  6. PS Mojave 10.14 , iMac retina 2015 version, scansnap s1300 and scansnap manager 3.2.91.1001
    Just quit and restarted – it takes longer to launch – leave it bouncing in the dock for a minute…

  7. ScanSnap will no longer scan to Evernote since the upgrade to Mojave. Very disappointing. Now I need to find a new scanner compatible with Evernote it seems … ?

Leave a Reply

The Robservatory © 2018 • Privacy Policy Built from the Frontier theme