In a message dated 11/2/2009 6:13:32 A.M.  Pacific Standard Time, 
[email protected] writes:
LR3 is intentionally  disabled from reading LR2 catalogs ... the
release note that came with it  says that. This is to prevent people
from using the PUBLIC BETA for  production work and damaging their
files. You are supposed to a) DUPLICATE  the ORIGINAL files you are
going to TEST it with, and b) create and test with  a NEW  catalog.
http://labs.adobe.com/technologies/lightroom3/releasenotes.pdf

This  is a test evaluation only release at present. If it is running
poorly, go to  the adobe forums that were detailed on the page from
which you downloaded it  and in the release notes do discuss  it:
http://forums.adobe.com/community/labs/lightroom3/

Public Betas  like this are not for everyone. Lots of stuff is far from
final and will not  work correctly yet. And they're not for production
work. I've worked with it  only a little bit so far, and thus far it
seems to work pretty well on the  machine I'm testing it on (MacBook
2Ghz, 2G  RAM).

=============
Thanks. I assumed it wasn't suppose to work with  the old catalog. But 
there is certainly something wrong with the way it is  creating a new catalog. 
I 
used 1.4 Beta when it came out and didn't have a  similar problem (or 
whatever the previous Beta was). So it's definitely bug  report time. 

Although I didn't see the release notes and the information  about using 
copies of files, so maybe they disabled creating a whole new  catalog. I don't 
mind doing debugging for someone on something like this -- so  the end 
product will be something I want. For instance, I wanted to check out  the 
watermark feature.

Thanks, Godfrey.

Marnie  

---------------------------------------------
We can't solve problems  by using the same kind of thinking we used when we 
created them. Albert Einstein   


--
PDML Pentax-Discuss Mail List
[email protected]
http://pdml.net/mailman/listinfo/pdml_pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow 
the directions.

Reply via email to