<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Using a Windows ScanSnap On the Mac Using VirtualBox</title>
	<atom:link href="http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/</link>
	<description>Learn How To Go Paperless With Easy Document Tips</description>
	<lastBuildDate>Tue, 07 Feb 2012 17:47:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: racerx90</title>
		<link>http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/comment-page-1/#comment-678</link>
		<dc:creator>racerx90</dc:creator>
		<pubDate>Wed, 07 Apr 2010 17:58:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/#comment-678</guid>
		<description>All new set of patches now available. This includes V2.2 L11, V2.2 L12, and V3.0 L20W (patches the dmg file directly! ;)  
 &lt;a href=&quot;http://forums.macosxhints.com/showthread.php?t=32046&amp;page=17&quot; rel=&quot;nofollow&quot;&gt;http://forums.macosxhints.com/showthread.php?t=32...&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>All new set of patches now available. This includes V2.2 L11, V2.2 L12, and V3.0 L20W (patches the dmg file directly! <img src='http://www.documentsnap.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /><br />
 <a href="http://forums.macosxhints.com/showthread.php?t=32046&amp;page=17" rel="nofollow">http://forums.macosxhints.com/showthread.php?t=32&#8230;</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BrooksD</title>
		<link>http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/comment-page-1/#comment-655</link>
		<dc:creator>BrooksD</dc:creator>
		<pubDate>Fri, 26 Mar 2010 23:12:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/#comment-655</guid>
		<description>Hi David, did you try racerx&#039;s patches above in this thread?  I&#039;ve heard people had good luck with them. </description>
		<content:encoded><![CDATA[<p>Hi David, did you try racerx&#039;s patches above in this thread?  I&#039;ve heard people had good luck with them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/comment-page-1/#comment-654</link>
		<dc:creator>David</dc:creator>
		<pubDate>Wed, 24 Mar 2010 03:29:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/#comment-654</guid>
		<description>I have been trying to find a way to install my S510 (without the N) on the new iMac that I have just purchased and have tried the Japanese workaround and every other suggestion that I could find on the internet and have had no luck. 
 
Please help!!! </description>
		<content:encoded><![CDATA[<p>I have been trying to find a way to install my S510 (without the N) on the new iMac that I have just purchased and have tried the Japanese workaround and every other suggestion that I could find on the internet and have had no luck. </p>
<p>Please help!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clint Marks</title>
		<link>http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/comment-page-1/#comment-448</link>
		<dc:creator>Clint Marks</dc:creator>
		<pubDate>Tue, 13 Oct 2009 23:35:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/#comment-448</guid>
		<description>You are modest. Your work is much appreciated. </description>
		<content:encoded><![CDATA[<p>You are modest. Your work is much appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BrooksD</title>
		<link>http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/comment-page-1/#comment-386</link>
		<dc:creator>BrooksD</dc:creator>
		<pubDate>Tue, 15 Sep 2009 19:36:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/#comment-386</guid>
		<description>I don&#039;t know about this model specifically, but Fujitsu didn&#039;t make their scanners cross-platform until the most recent version, so I doubt it.  If you are feeling brave, you can check into the link that racerx90 posted above.  Good luck. </description>
		<content:encoded><![CDATA[<p>I don&#039;t know about this model specifically, but Fujitsu didn&#039;t make their scanners cross-platform until the most recent version, so I doubt it.  If you are feeling brave, you can check into the link that racerx90 posted above.  Good luck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyaw Lwin</title>
		<link>http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/comment-page-1/#comment-378</link>
		<dc:creator>Kyaw Lwin</dc:creator>
		<pubDate>Mon, 14 Sep 2009 04:56:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/#comment-378</guid>
		<description>Dear Sirs, 
 
I have a special offer for fi-5110EOXM (MAC version). 
Do you think I can purchase the unit and use it in WindowXP? 
WIll it works?  
I do not rquires to use in MAC OS. 
 
Thanks in advance. </description>
		<content:encoded><![CDATA[<p>Dear Sirs,</p>
<p>I have a special offer for fi-5110EOXM (MAC version).</p>
<p>Do you think I can purchase the unit and use it in WindowXP?</p>
<p>WIll it works? </p>
<p>I do not rquires to use in MAC OS.</p>
<p>Thanks in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/comment-page-1/#comment-243</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Tue, 30 Jun 2009 17:50:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/#comment-243</guid>
		<description>I patched the Scansnap manager and can now use my original generation PC Scansnap on OS X. Great and thanks. Question: if I purchase a new, current Mac model Scansnap, could I  use the patched driver with it, so that I could use both Scansnaps on my OS X laptop, one at home, and one at the office? </description>
		<content:encoded><![CDATA[<p>I patched the Scansnap manager and can now use my original generation PC Scansnap on OS X. Great and thanks. Question: if I purchase a new, current Mac model Scansnap, could I  use the patched driver with it, so that I could use both Scansnaps on my OS X laptop, one at home, and one at the office?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: racerx90</title>
		<link>http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/comment-page-1/#comment-142</link>
		<dc:creator>racerx90</dc:creator>
		<pubDate>Sat, 25 Apr 2009 23:42:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/#comment-142</guid>
		<description>Brooks-  
  
LOL! By no means am I the &quot;ScanSnap king&quot;!  
  
It was out of shear frustration I did this in the first place (I wasn&#039;t about to buy a new scanner either although the thought had crossed my mind once or twice while debugging this! ;)  
  
I doubt you&#039;d believe me if I told you that I&#039;m not an engineer; I work in marketing - it&#039;s the honest truth. I also just got a Mac this past year, so by no means am I an expert in OS X either.  
  
What I did anyone could have also done if they would have just took the time. Once I figured out that you could turn an S300 into an S300M by loading the Mac firmware file under a Windows VM (then disconnecting the scanner and giving it back to the host OS) - I knew the Mac ScanSnap Manager could be re-written. It clearly wasn&#039;t a &quot;hardware&quot; limitation (given the firmware has to be loaded by the software each time the scanner is initialized.)  
  
From there, all I did was use otool/otx to disassemble the code. Once I had the disassembly to work from, I used the assembler reference guide to decipher the instructions (in hex) along with a hex editor to re-write and patch the code in the appropriate addresses. (It&#039;s very tedious, but I was rather stubborn to get it working.)  
  
It was fairly easy to locate the correct routines since the DevIDs of the scanners are clearly readable in the code (and I got those from the SANE supported device list web page.)  
  
What I mean by that is you&#039;d see a cmpw instruction along with 0x117F (S300M) DevID - so you knew for sure you found one of the code paths. Some of those DevIDs, would then need to be re-written for their PC-scanner counterparts - for instance, S300M - 0x117F needed to be changed to S300 - 0x1156 (or 5611 in hex) and so forth for all the different scanners. The rest of the code sections were documented well enough from the disassembler (i.e. firmware load, initialization, etc.), so when you were following the code paths you could see exactly where you were at least.  
  
Essentially, there&#039;s only 3 unique scanner code paths in the drivers - S300M, S500M/S510M, and fi-5110EOXM. All the scanner types fall into one of those code paths which I then changed to support their PC-based counterparts.  
  
There was only 1 other change I needed to do in order to fix a bug I found in the about-&gt;details menu. This was a bit more tricky, because I had to re-write the instructions (not just the DevIDs) to handle the other scanner types (this is where the assembler instruction guide came in handy.) Otherwise, it wouldn&#039;t correctly identify the scanner name in the details window, and at least for the S300 (I believe for others as well), it wouldn&#039;t show the correct icon in the dock and if it&#039;s running on USB or AC power (it&#039;s more cosmetic than anything, but I wanted it to be right.)  
  
For the most part, it was just a bunch of trial and error to get it working (since I couldn&#039;t read through every line of code (there&#039;s literally tens of thousands of lines), so I made a lot of assumptions and took a *LOT* of guesses) - meaning, you make a change, and then test it out until I finally got the entire code-path working and debugged.  
  
Surprisingly enough, there&#039;s already a lot of the PC-based scanner support code in the Mac ScanSnap Manager application so it wasn&#039;t a ton of work for me (there might be only 15 places I had to patch a few bytes). It looks like Fujitsu originally had it in the code, then pulled it out at the last minute for some reason (I&#039;m certain the code was there then removed based on what&#039;s left.)  
  
I recently emailed Fujitsu and asked them if they could provide cross platform support in their drivers for their other scanners now that they&#039;ve released cross-platform support for their new S1500-series (obviously there&#039;s been a number customers complaining about it.) Hopefully, they&#039;ll have it in their heart to do it, but I&#039;m still waiting on an answer (but I&#039;m not holding my breath.)  
  
Finally, I&#039;ve documented my patch and also posted a link to download it in the MAC OS X Hints forum. This way if anyone would like to know what I did or learn from this then the information is available.  
  
Anyway, even though it was a lot of &quot;fun&quot; to do - I&#039;m glad at least that it&#039;s been helpful to others in the same situation as me (I&#039;m definitely not alone.) My patch kit has already been downloaded almost 390 times so far without a single issue reported! Thanks!  
  
Regards,  
E </description>
		<content:encoded><![CDATA[<p>Brooks-  </p>
<p>LOL! By no means am I the &quot;ScanSnap king&quot;!  </p>
<p>It was out of shear frustration I did this in the first place (I wasn&#039;t about to buy a new scanner either although the thought had crossed my mind once or twice while debugging this! <img src='http://www.documentsnap.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />   </p>
<p>I doubt you&#039;d believe me if I told you that I&#039;m not an engineer; I work in marketing &#8211; it&#039;s the honest truth. I also just got a Mac this past year, so by no means am I an expert in OS X either.  </p>
<p>What I did anyone could have also done if they would have just took the time. Once I figured out that you could turn an S300 into an S300M by loading the Mac firmware file under a Windows VM (then disconnecting the scanner and giving it back to the host OS) &#8211; I knew the Mac ScanSnap Manager could be re-written. It clearly wasn&#039;t a &quot;hardware&quot; limitation (given the firmware has to be loaded by the software each time the scanner is initialized.)  </p>
<p>From there, all I did was use otool/otx to disassemble the code. Once I had the disassembly to work from, I used the assembler reference guide to decipher the instructions (in hex) along with a hex editor to re-write and patch the code in the appropriate addresses. (It&#039;s very tedious, but I was rather stubborn to get it working.)  </p>
<p>It was fairly easy to locate the correct routines since the DevIDs of the scanners are clearly readable in the code (and I got those from the SANE supported device list web page.)  </p>
<p>What I mean by that is you&#039;d see a cmpw instruction along with 0x117F (S300M) DevID &#8211; so you knew for sure you found one of the code paths. Some of those DevIDs, would then need to be re-written for their PC-scanner counterparts &#8211; for instance, S300M &#8211; 0x117F needed to be changed to S300 &#8211; 0&#215;1156 (or 5611 in hex) and so forth for all the different scanners. The rest of the code sections were documented well enough from the disassembler (i.e. firmware load, initialization, etc.), so when you were following the code paths you could see exactly where you were at least.  </p>
<p>Essentially, there&#039;s only 3 unique scanner code paths in the drivers &#8211; S300M, S500M/S510M, and fi-5110EOXM. All the scanner types fall into one of those code paths which I then changed to support their PC-based counterparts.  </p>
<p>There was only 1 other change I needed to do in order to fix a bug I found in the about-&gt;details menu. This was a bit more tricky, because I had to re-write the instructions (not just the DevIDs) to handle the other scanner types (this is where the assembler instruction guide came in handy.) Otherwise, it wouldn&#039;t correctly identify the scanner name in the details window, and at least for the S300 (I believe for others as well), it wouldn&#039;t show the correct icon in the dock and if it&#039;s running on USB or AC power (it&#039;s more cosmetic than anything, but I wanted it to be right.)  </p>
<p>For the most part, it was just a bunch of trial and error to get it working (since I couldn&#039;t read through every line of code (there&#039;s literally tens of thousands of lines), so I made a lot of assumptions and took a *LOT* of guesses) &#8211; meaning, you make a change, and then test it out until I finally got the entire code-path working and debugged.  </p>
<p>Surprisingly enough, there&#039;s already a lot of the PC-based scanner support code in the Mac ScanSnap Manager application so it wasn&#039;t a ton of work for me (there might be only 15 places I had to patch a few bytes). It looks like Fujitsu originally had it in the code, then pulled it out at the last minute for some reason (I&#039;m certain the code was there then removed based on what&#039;s left.)  </p>
<p>I recently emailed Fujitsu and asked them if they could provide cross platform support in their drivers for their other scanners now that they&#039;ve released cross-platform support for their new S1500-series (obviously there&#039;s been a number customers complaining about it.) Hopefully, they&#039;ll have it in their heart to do it, but I&#039;m still waiting on an answer (but I&#039;m not holding my breath.)  </p>
<p>Finally, I&#039;ve documented my patch and also posted a link to download it in the MAC OS X Hints forum. This way if anyone would like to know what I did or learn from this then the information is available.  </p>
<p>Anyway, even though it was a lot of &quot;fun&quot; to do &#8211; I&#039;m glad at least that it&#039;s been helpful to others in the same situation as me (I&#039;m definitely not alone.) My patch kit has already been downloaded almost 390 times so far without a single issue reported! Thanks!  </p>
<p>Regards,<br />
E</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BrooksD</title>
		<link>http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/comment-page-1/#comment-141</link>
		<dc:creator>BrooksD</dc:creator>
		<pubDate>Fri, 24 Apr 2009 14:57:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/#comment-141</guid>
		<description>Wow, thank you so much for this awesome walkthrough racerx90!I never would have thought of messing around with the application files themselves, so I will definitely check out that thread. You&#039;re the ScanSnap king (we&#039;re not worthy...). </description>
		<content:encoded><![CDATA[<p>Wow, thank you so much for this awesome walkthrough racerx90!I never would have thought of messing around with the application files themselves, so I will definitely check out that thread. You&#039;re the ScanSnap king (we&#039;re not worthy&#8230;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: racerx90</title>
		<link>http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/comment-page-1/#comment-135</link>
		<dc:creator>racerx90</dc:creator>
		<pubDate>Sun, 19 Apr 2009 19:28:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.documentsnap.com/using-a-windows-scansnap-on-the-mac-using-virtualbox/#comment-135</guid>
		<description>Yes - read on: 
 
Honestly, the Fujitsu ScanSnap scanners are really great - no complaints whatsoever except for one. Having switched to a Mac laptop for my new job ended up orphaning my S300 scanner (expensive paperweight) with no way to work on the Mac (it&#039;s ridiculous that Fujitsu does this) and I wasn&#039;t about to buy another one. 
 
I tried just about everything to get the S300 scanner working with the MAC driver under OS X (including the resource swap trick with the Japanese driver - but it doesn&#039;t support S300, not to mention it&#039;s a complete waste of time), but it just doesn&#039;t work. Even though most of the code is in the MAC driver to support all of the PC-based ScanSnap scanners - Fujitsu just disables it in the initialization routine based on DevID&#039;s. 
 
Essentially what I found out after a lot of testing is that there&#039;s no discernible difference between the the PC-variant and the MAC-variant scanner hardware - even the firmware for the S300 line is software loaded from the driver. The only real difference is the PCI Device IDs (0x117F vs. 0x1156), which holds true for the rest of the ScanSnap scanners. 
 
After months of procrastinating I decided that I had enough of the VMware/VirtualBox solution and decided to just do a binary patch for the ScanSnap Manager software for the Mac and add support for all the ScanSnap scanners. Now the S300, S500, S510, and fi-5110EOX/2/3 scanners will work under OSX with the latest V2.2 L11 Mac ScanSnap drivers from Fujitsu (which was designed to work with the S300M, S500M, S510M and fi-5110EOXM scanners.) Go to forums at MAC OS X Hints, read through the thread to find the installation instructions and you will also find a link to download the patches that I created ( &lt;a href=&quot;http://forums.macosxhints.com/showthread.php?t=32046&amp;page=10&quot; rel=&quot;nofollow&quot;&gt;http://forums.macosxhints.com/showthread.php?t=32...&lt;/a&gt; ). It&#039;s a simple 1-step process to do the patch (just drag the ScanSnap Manager application on the patch utility and it does all the work for you plus it supports multiple languages!) 
 
Finally, I also figured out and documented how to use MAC-based ScanSnap scanners on PCs (Windows) with a 1-line change to the device drivers. Even though I did it with the S300M, I&#039;m positive it will work with the S500M, S510M, and fi-5110EOXM scanners. It&#039;s in the same MAC OS X Hints thread I linked to above (just read it for details.)  
 
This should eliminate *all* cross-platform incompatibilities with the Scanners and the corresponding drivers. 
 
Hopefully that will help others.  </description>
		<content:encoded><![CDATA[<p>Yes &#8211; read on: </p>
<p>Honestly, the Fujitsu ScanSnap scanners are really great &#8211; no complaints whatsoever except for one. Having switched to a Mac laptop for my new job ended up orphaning my S300 scanner (expensive paperweight) with no way to work on the Mac (it&#039;s ridiculous that Fujitsu does this) and I wasn&#039;t about to buy another one. </p>
<p>I tried just about everything to get the S300 scanner working with the MAC driver under OS X (including the resource swap trick with the Japanese driver &#8211; but it doesn&#039;t support S300, not to mention it&#039;s a complete waste of time), but it just doesn&#039;t work. Even though most of the code is in the MAC driver to support all of the PC-based ScanSnap scanners &#8211; Fujitsu just disables it in the initialization routine based on DevID&#039;s. </p>
<p>Essentially what I found out after a lot of testing is that there&#039;s no discernible difference between the the PC-variant and the MAC-variant scanner hardware &#8211; even the firmware for the S300 line is software loaded from the driver. The only real difference is the PCI Device IDs (0x117F vs. 0&#215;1156), which holds true for the rest of the ScanSnap scanners. </p>
<p>After months of procrastinating I decided that I had enough of the VMware/VirtualBox solution and decided to just do a binary patch for the ScanSnap Manager software for the Mac and add support for all the ScanSnap scanners. Now the S300, S500, S510, and fi-5110EOX/2/3 scanners will work under OSX with the latest V2.2 L11 Mac ScanSnap drivers from Fujitsu (which was designed to work with the S300M, S500M, S510M and fi-5110EOXM scanners.) Go to forums at MAC OS X Hints, read through the thread to find the installation instructions and you will also find a link to download the patches that I created ( <a href="http://forums.macosxhints.com/showthread.php?t=32046&amp;page=10" rel="nofollow">http://forums.macosxhints.com/showthread.php?t=32&#8230;</a> ). It&#039;s a simple 1-step process to do the patch (just drag the ScanSnap Manager application on the patch utility and it does all the work for you plus it supports multiple languages!) </p>
<p>Finally, I also figured out and documented how to use MAC-based ScanSnap scanners on PCs (Windows) with a 1-line change to the device drivers. Even though I did it with the S300M, I&#039;m positive it will work with the S500M, S510M, and fi-5110EOXM scanners. It&#039;s in the same MAC OS X Hints thread I linked to above (just read it for details.)  </p>
<p>This should eliminate *all* cross-platform incompatibilities with the Scanners and the corresponding drivers. </p>
<p>Hopefully that will help others.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Database Caching 7/22 queries in 0.251 seconds using disk: basic
Object Caching 448/459 objects using disk: basic

Served from: www.documentsnap.com @ 2012-02-07 22:57:07 -->
