<?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: The Dreaded Lightroom &#8220;Change Modules&#8221; Error</title>
	<atom:link href="http://singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/feed/" rel="self" type="application/rss+xml" />
	<link>http://singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/</link>
	<description>Photography in Small Doses</description>
	<lastBuildDate>Tue, 20 Mar 2012 17:43:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: liz l</title>
		<link>http://singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/comment-page-1/#comment-3909</link>
		<dc:creator>liz l</dc:creator>
		<pubDate>Sun, 31 Jul 2011 00:15:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-3909</guid>
		<description>Thank you so much for this article, it fixed all my Lightroom issues! I know I&#039;m a couple years late, but it did the trick.
Thanks again!</description>
		<content:encoded><![CDATA[<p>Thank you so much for this article, it fixed all my Lightroom issues! I know I&#8217;m a couple years late, but it did the trick.<br />
Thanks again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: what am i doing wrong?</title>
		<link>http://singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/comment-page-1/#comment-2025</link>
		<dc:creator>what am i doing wrong?</dc:creator>
		<pubDate>Mon, 19 Jul 2010 11:58:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-2025</guid>
		<description>[...]  [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;]  [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/comment-page-1/#comment-1190</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Mon, 26 May 2008 12:45:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1190</guid>
		<description>Well, I thought I&#039;d write in this area since Adobe is so slow and limited in their forum and knowledgebase searches.  I trialed their version 1.3 and, to my utter disappointment, still have no export abilities for background music.  I assume they are limited by Acrobat&#039;s inability to play music.  Well, I let the trial lapse and then went back to the folders that it had imported (I was missing images that I knew I should have had).  I looked at these particular folders Lightroom had set up and found that the X3F files had 0 kb&#039;s!  That was 127 images that were not imported.  When you are importing 100&#039;s and 1,000&#039;s of images, you might just not notice that the files have &quot;0&quot; listed in the registered image!  Now that the app has lapsed, I can&#039;t go in to see if there is, at least, a thumbnail ghost or another place where the file might have been sequestered.  This is not as painful as my iPhoto experience of losing thumbnails and thinking I had lost the originals and, in my panic, accidentally deleting an original file of thousands.  But, it would have been disconcerting if I had shelled out the $300 and found later that these files had been registered as X3F files with no content!  Any suggestions?  Like, kiss them off or hasta la toaster, baby!?!</description>
		<content:encoded><![CDATA[<p>Well, I thought I&#8217;d write in this area since Adobe is so slow and limited in their forum and knowledgebase searches.  I trialed their version 1.3 and, to my utter disappointment, still have no export abilities for background music.  I assume they are limited by Acrobat&#8217;s inability to play music.  Well, I let the trial lapse and then went back to the folders that it had imported (I was missing images that I knew I should have had).  I looked at these particular folders Lightroom had set up and found that the X3F files had 0 kb&#8217;s!  That was 127 images that were not imported.  When you are importing 100&#8217;s and 1,000&#8217;s of images, you might just not notice that the files have &#8220;0&#8221; listed in the registered image!  Now that the app has lapsed, I can&#8217;t go in to see if there is, at least, a thumbnail ghost or another place where the file might have been sequestered.  This is not as painful as my iPhoto experience of losing thumbnails and thinking I had lost the originals and, in my panic, accidentally deleting an original file of thousands.  But, it would have been disconcerting if I had shelled out the $300 and found later that these files had been registered as X3F files with no content!  Any suggestions?  Like, kiss them off or hasta la toaster, baby<img src="?" alt="" /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: monique</title>
		<link>http://singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/comment-page-1/#comment-1164</link>
		<dc:creator>monique</dc:creator>
		<pubDate>Sat, 15 Mar 2008 00:35:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1164</guid>
		<description>thanks for sharing. 
It solved my adobe lightroom problem. :)</description>
		<content:encoded><![CDATA[<p>thanks for sharing. <br />
It solved my adobe lightroom problem. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/comment-page-1/#comment-1080</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Mon, 03 Dec 2007 22:03:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1080</guid>
		<description>Sorry to hear about your troubles, Kev. I did bite the bullet and upgrade to 10.5 (Leopard, actually 10.5.1) and I&#039;m running Lightroom 1.3 and my &quot;Print&quot; module does seem to be working. I admit, I don&#039;t use the print module much, but I tried it once and saw the convenience it brings, especially for contact sheets and such.

I&#039;m slightly disappointed at how slowly Adobe seems to react to things like these. I have a much more serious problem with Leopard and Photoshop CS 3, which I also wrote about. That still has not been resolved, so I&#039;m using CS 2 instead.

Lightroom is a great product, but so is Aperture. I have a lot of time invested in Lightroom and I would like to keep it, but if push came to shove, I have options.

Photoshop is at the place in its lifespan where it has become seriously entrenched and is depended upon by millions. If I couldn&#039;t use Photoshop, I&#039;m really not sure where I would turn. I hope that Adobe can get their act together and fix the problems it has in Leopard because hardware and OS development isn&#039;t going to stop any time soon!

Thanks for sharing your troubles, Kev. If you do get it figured out, please leave another comment so everyone can benefit!</description>
		<content:encoded><![CDATA[<p>Sorry to hear about your troubles, Kev. I did bite the bullet and upgrade to 10.5 (Leopard, actually 10.5.1) and I&#8217;m running Lightroom 1.3 and my &#8220;Print&#8221; module does seem to be working. I admit, I don&#8217;t use the print module much, but I tried it once and saw the convenience it brings, especially for contact sheets and such.</p>
<p>I&#8217;m slightly disappointed at how slowly Adobe seems to react to things like these. I have a much more serious problem with Leopard and Photoshop CS 3, which I also wrote about. That still has not been resolved, so I&#8217;m using CS 2 instead.</p>
<p>Lightroom is a great product, but so is Aperture. I have a lot of time invested in Lightroom and I would like to keep it, but if push came to shove, I have options.</p>
<p>Photoshop is at the place in its lifespan where it has become seriously entrenched and is depended upon by millions. If I couldn&#8217;t use Photoshop, I&#8217;m really not sure where I would turn. I hope that Adobe can get their act together and fix the problems it has in Leopard because hardware and OS development isn&#8217;t going to stop any time soon!</p>
<p>Thanks for sharing your troubles, Kev. If you do get it figured out, please leave another comment so everyone can benefit!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kev Thomas</title>
		<link>http://singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/comment-page-1/#comment-1079</link>
		<dc:creator>Kev Thomas</dc:creator>
		<pubDate>Mon, 03 Dec 2007 20:56:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1079</guid>
		<description>Hate to say it, but I&#039;m running LR 1.3 and on 10.4.11 of OSX. I printed loads of pictures yesterday, but today it&#039;s not letting me into the Print module at all. There&#039;s plenty of drive space, and nothing...but nothing, has been updated. This is really, really frustrating!</description>
		<content:encoded><![CDATA[<p>Hate to say it, but I&#8217;m running LR 1.3 and on 10.4.11 of <span class="caps">OSX</span>. I printed loads of pictures yesterday, but today it&#8217;s not letting me into the Print module at all. There&#8217;s plenty of drive space, and nothing&#8230;but nothing, has been updated. This is really, really frustrating!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Administrator</title>
		<link>http://singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/comment-page-1/#comment-1017</link>
		<dc:creator>Administrator</dc:creator>
		<pubDate>Sat, 03 Nov 2007 02:56:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1017</guid>
		<description>I&#039;m not very happy with Adobe at the moment, thanks to both this Lightroom 1.2 news from Charley as well as my &quot;poor experience with Photoshop CS3&quot;:http://www.singleservingphoto.com/2007/10/17/photoshop-cs3-overrated/. It looks rather certain that I&#039;ll stick with Tiger for at least the rest of this month (even though I have a Leopard DVD on its way to me as I write this).

C&#039;mon Adobe, get with the program!</description>
		<content:encoded><![CDATA[<p>I&#8217;m not very happy with Adobe at the moment, thanks to both this Lightroom 1.2 news from Charley as well as my <a href="http://www.singleservingphoto.com/2007/10/17/photoshop-cs3-overrated/">poor experience with Photoshop CS3</a>. It looks rather certain that I&#8217;ll stick with Tiger for at least the rest of this month (even though I have a Leopard <span class="caps">DVD</span> on its way to me as I write this).</p>
<p>C&#8217;mon Adobe, get with the program!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: charley</title>
		<link>http://singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/comment-page-1/#comment-1011</link>
		<dc:creator>charley</dc:creator>
		<pubDate>Thu, 01 Nov 2007 02:28:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1011</guid>
		<description></description>
		<content:encoded><![CDATA[<p>&#8230;update to last post&#8230;</p>
<p>I revised my search and found this:  <a href="http://www.lightroomforums.net/showthread.php?t=330" rel="nofollow">http://www.lightroomforums.net/showthread.php?t=330</a></p>
<p>It appears LR 1.2 is not fully compatible with OS X 10.5!!!</p>
<p>From the blog:<br />
Per Tom&#8217;s blog, &#8220;The current version of Lightroom 1.2 is not fully compatible with Leopard, Mac OS X 10.5. The good news is that we’ll be releasing an update in mid-November that will address key compatibility issues.&#8221; One of the known issues is that the Print module may not load. For the full blog: <a href="http://blogs.adobe.com/lightroomjour&#8230;d_leopard.html" rel="nofollow">http://blogs.adobe.com/lightroomjour&#8230;d_leopard.html</a>.</p>
<p>In a weird way, I&#8217;m relieved by this answer.  At least I know to stop chasing the issue.  Plus, I can always print from CS3.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: charley</title>
		<link>http://singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/comment-page-1/#comment-1010</link>
		<dc:creator>charley</dc:creator>
		<pubDate>Thu, 01 Nov 2007 02:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.singleservingphoto.com/2007/10/19/the-dreaded-lightroom-change-modules-error/#comment-1010</guid>
		<description>Hey Aaron -

I&#039;m having the same issue in LR (&quot;an error occurred when changing modules&quot;).  It appears to have started after I upgraded to OS X 10.5 last weekend.  I get the error when I click on the &quot;Print&quot; module in LR.  All other modules seem to work okay.  

I&#039;ve re-installed the print driver (Pixma Pro 9000)...re-installed LR... tried the rename-the-Lightroom-folder trick you mentioned...STILL no luck!  I was hoping you might have some other ideas.

Thanks!
Charley</description>
		<content:encoded><![CDATA[<p>Hey Aaron &#8211; </p>
<p>I&#8217;m having the same issue in LR (&#8220;an error occurred when changing modules&#8221;).  It appears to have started after I upgraded to OS X 10.5 last weekend.  I get the error when I click on the &#8220;Print&#8221; module in LR.  All other modules seem to work okay.  </p>
<p>I&#8217;ve re-installed the print driver (Pixma Pro 9000)&#8230;re-installed LR&#8230; tried the rename-the-Lightroom-folder trick you mentioned&#8230;STILL no luck!  I was hoping you might have some other ideas.</p>
<p>Thanks!<br />
Charley</p>
]]></content:encoded>
	</item>
</channel>
</rss>

