<?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: When migrating to a new operating system, Look Before You Leap!</title>
	<atom:link href="http://paperjammed.com/2009/09/07/when-migrating-to-a-new-operating-system-look-before-you-leap/feed/" rel="self" type="application/rss+xml" />
	<link>http://paperjammed.com/2009/09/07/when-migrating-to-a-new-operating-system-look-before-you-leap/</link>
	<description>Has paper taken over your life?</description>
	<lastBuildDate>Thu, 01 Jul 2010 19:23:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Snow Leopard Update for ScanSnap &#124; Paper Jammed</title>
		<link>http://paperjammed.com/2009/09/07/when-migrating-to-a-new-operating-system-look-before-you-leap/comment-page-1/#comment-5135</link>
		<dc:creator>Snow Leopard Update for ScanSnap &#124; Paper Jammed</dc:creator>
		<pubDate>Sat, 14 Nov 2009 04:37:06 +0000</pubDate>
		<guid isPermaLink="false">http://paperjammed.com/?p=676#comment-5135</guid>
		<description>[...] August, I ordered my copy the first week and was so excited that I installed it the day it arrived. My joy was short-lived, however: the most important software package I use did not [...]</description>
		<content:encoded><![CDATA[<p>[...] August, I ordered my copy the first week and was so excited that I installed it the day it arrived. My joy was short-lived, however: the most important software package I use did not [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tad</title>
		<link>http://paperjammed.com/2009/09/07/when-migrating-to-a-new-operating-system-look-before-you-leap/comment-page-1/#comment-4321</link>
		<dc:creator>Tad</dc:creator>
		<pubDate>Tue, 08 Sep 2009 20:16:14 +0000</pubDate>
		<guid isPermaLink="false">http://paperjammed.com/?p=676#comment-4321</guid>
		<description>Thanks for the good news on the Scansnap/Finereader combo. I&#039;m pretty confident that as the next week or two pass most of the Snow Leopard software issues will either be resolved or will be understood better.

I haven&#039;t given up hope yet—my Snow Leopard DVD is still sitting on my desk, ready for action.

It&#039;s funny that I just don&#039;t seem to remember this much fuss when I migrated from Tiger to Leopard; but then again that was during my first year on Macintosh so I hadn&#039;t yet settled in.

I&#039;m already expecting that I will hit a few quirks along the way that I will have to learn to live with. When I migrated to Leopard, my spiffy HP LaserJet 1320 started flashing the error light every time I printed a document. It still works, but I have to go downstairs to the printer and press the &quot;Go&quot; button for the document to come out. HP never fixed it, and AppleCare couldn&#039;t figure it out. There&#039;s an ancient thread out there somewhere about it with plenty of people having the same issue, but I can&#039;t imagine that it will ever be fixed...</description>
		<content:encoded><![CDATA[<p>Thanks for the good news on the Scansnap/Finereader combo. I&#8217;m pretty confident that as the next week or two pass most of the Snow Leopard software issues will either be resolved or will be understood better.</p>
<p>I haven&#8217;t given up hope yet—my Snow Leopard DVD is still sitting on my desk, ready for action.</p>
<p>It&#8217;s funny that I just don&#8217;t seem to remember this much fuss when I migrated from Tiger to Leopard; but then again that was during my first year on Macintosh so I hadn&#8217;t yet settled in.</p>
<p>I&#8217;m already expecting that I will hit a few quirks along the way that I will have to learn to live with. When I migrated to Leopard, my spiffy HP LaserJet 1320 started flashing the error light every time I printed a document. It still works, but I have to go downstairs to the printer and press the &#8220;Go&#8221; button for the document to come out. HP never fixed it, and AppleCare couldn&#8217;t figure it out. There&#8217;s an ancient thread out there somewhere about it with plenty of people having the same issue, but I can&#8217;t imagine that it will ever be fixed&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael F</title>
		<link>http://paperjammed.com/2009/09/07/when-migrating-to-a-new-operating-system-look-before-you-leap/comment-page-1/#comment-4310</link>
		<dc:creator>Michael F</dc:creator>
		<pubDate>Tue, 08 Sep 2009 04:49:51 +0000</pubDate>
		<guid isPermaLink="false">http://paperjammed.com/?p=676#comment-4310</guid>
		<description>Hey -- I did upgrade to Snow Leopard, and wanted to give you a quick update on the Scansnap situation.

There are two issues, at least with the version of software that came with my new Scansnap S1500M.

1) The Scansnap Manager software&#039;s &quot;Quick Menu&quot; function doesn&#039;t work. There is a very quick fix you can do (editing a text file) to disable it. I never used it anyway - I wanted more control than that. &quot;Scan to Folder&quot; by contrast DOES work, despite earlier reports.

2) The &quot;Finereader for Scansnap&quot; app has a bug that causes it not to recognize PDFs as coming from Scansnap Manager, even when they do. The cause seems to be the &quot;PDF Producer&quot; metadata tag embedded in the PDF. The Finereader software is looking for &quot;Mac OS X 10.5.8 Quartz PDFContext&quot;, but under Snow Leopard, the string is set to &quot;Mac OS X 10.6 Quartz PDFContext&quot; instead. 

There is a fix for this as well -- there&#039;s a free command line tool called pdftk that can modify this metadata.  I&#039;ve confirmed that fixing this is all that is required to get Finereader for Scansnap to work again on files scanned under Snow Leopard.

It looks easy enough to turn this process into an Automator workflow, and save it as a folder action, or even as an app that Scansnap Manager can hand off its scanned files to. (Could also be a service under Snow Leopard, so that you can process previously-scanned-under-SL PDFs by right-clicking them and choosing the service.) 

The details of what I found out are in the comments of the post you linked to, above.

Hope this is helpful if you do decide to migrate forward...</description>
		<content:encoded><![CDATA[<p>Hey &#8212; I did upgrade to Snow Leopard, and wanted to give you a quick update on the Scansnap situation.</p>
<p>There are two issues, at least with the version of software that came with my new Scansnap S1500M.</p>
<p>1) The Scansnap Manager software&#8217;s &#8220;Quick Menu&#8221; function doesn&#8217;t work. There is a very quick fix you can do (editing a text file) to disable it. I never used it anyway &#8211; I wanted more control than that. &#8220;Scan to Folder&#8221; by contrast DOES work, despite earlier reports.</p>
<p>2) The &#8220;Finereader for Scansnap&#8221; app has a bug that causes it not to recognize PDFs as coming from Scansnap Manager, even when they do. The cause seems to be the &#8220;PDF Producer&#8221; metadata tag embedded in the PDF. The Finereader software is looking for &#8220;Mac OS X 10.5.8 Quartz PDFContext&#8221;, but under Snow Leopard, the string is set to &#8220;Mac OS X 10.6 Quartz PDFContext&#8221; instead. </p>
<p>There is a fix for this as well &#8212; there&#8217;s a free command line tool called pdftk that can modify this metadata.  I&#8217;ve confirmed that fixing this is all that is required to get Finereader for Scansnap to work again on files scanned under Snow Leopard.</p>
<p>It looks easy enough to turn this process into an Automator workflow, and save it as a folder action, or even as an app that Scansnap Manager can hand off its scanned files to. (Could also be a service under Snow Leopard, so that you can process previously-scanned-under-SL PDFs by right-clicking them and choosing the service.) </p>
<p>The details of what I found out are in the comments of the post you linked to, above.</p>
<p>Hope this is helpful if you do decide to migrate forward&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
