Virtual Copies

Status
Not open for further replies.
R

Roger Walton

Member
Joined
Aug 10, 2008
Messages
31
LR2 gives an error message on my Windows XP desktop when I try to make virtual copies. My laptop, same operating system, works fine.

Any ideas?
 
Sort by date Sort by votes
Last edited:
Upvote 0 Downvote
I'd try reinstalling/repairing the install. That doesn't look like a preferences bug, and I think it's unlikely to be a catalog bug, although trying a fresh catalog wouldn't be a bad idea.
 
Upvote 0 Downvote
I've just spotted a similar problem on the U2U forum - might be worth keeping an eye on it. https://forum.adobe.com/webx?128@@.59b5f9'f

Two of the engineers - Dustin & Brian - are on the case, which is promising.
 
Upvote 0 Downvote
Just checked the forum posts and the latest ones may be pointing in the right direction - that this is an issue with AMD processors and not with Intell. This agrees with my situation as the desktop with the problem is AMD, the laptop that works is Intel.

Just thought this may be of interest to anyone else with this issue.
 
Upvote 0 Downvote
Ah, well done Roger, thanks for posting that back. I don't have much time to spend on the U2U right now due to work commitments, so do let us know what transpires.
 
Upvote 0 Downvote
No solution just yet but it's reassuring(?) to know that I'm not the only one with this problem - far from it!

As I read it so far, the AMD processor doesn't appear to have the spec required for LR 2 so it looks as though it will either have to be just the laptop or a new desktop too. Oh dear - an expensive upgrade, I fear.
 
Upvote 0 Downvote
I wouldn't panic yet Roger, never know what fixes they'll come up with. If they have it narrowed down to a specific trigger, it's easier to trace.
 
Upvote 0 Downvote
Don't know wether you're keeping up with the thread on the u2u forum but this problem seems to be affecting only AMD Athlon processors. Athlon 64 processors are fine.
According to Brian, Adobe engineer, it's to do with the fact that Athlon's don't support the SSE2 instruction set.
Unfortunately there are some who appear to be using this problem as an excuse for a general and sometimes personal attack on members of the forum and Adobe staff. Who needs that sort of members in a forum heh?
Hope this helps others with the same problem.
 
Upvote 0 Downvote
Yes, as a new visitor to the u2u forum, I was dismayed to read how some people were using this "bug" to berate Adobe. It's a pity they've such a negative outlook or maybe they've just had a bad week.
 
Upvote 0 Downvote
From reading the comments of some they're having more than a bad week. They seem to be having a bad year!
 
Upvote 0 Downvote
Thanks for posting that Paul, and welcome to the forum!

paul_w said:
Unfortunately there are some who appear to be using this problem as an excuse for a general and sometimes personal attack on members of the forum and Adobe staff. Who needs that sort of members in a forum heh?
Click to expand...

It definitely gets a bit fraught over there. Nice and friendly here though!
 
Upvote 0 Downvote
You're more than welcome.

:)
 
Upvote 0 Downvote
Yep, just read that.

Good news indeed!
 
Upvote 0 Downvote
Looks like bad news on this one.

Apparently, according to the u2u forum, fixing this bug may lead to an even bigger problem so they're losing hope.

Looks like those of us with Athlons wanting to ugrade to Lr2 will have to upgrade our 'puters first!

They're still working on it and will post on the u2u forum if there's any progress.

Fingers crossed.
 
Upvote 0 Downvote
Just and FYI on this bug. I had it happen this weekend on my machine which is NOT and AMD. I have an "Intel Core 2 Quad Q66'' 2.4GHz, XP Pro SP3".

I am not sure how it happened, BUT I do remember making some VC's, then did a couple develop steps on an image, and realized I wanted to back up a couple so I hit Ctrl-Z "Undo" and I think then I got hit by the "Undo Bug"m because it went back waaaaay to many steps. So many so that it undid my creation of my VC's.

So I tried to recreate the VC's and was hit by the above error. I wish I took a screenshot,, but I thought it was a fluke.
 
Upvote 0 Downvote
Thomas Knoll posted on the u2u forum yesterday that Adobe have a potential fix for this problem that they are currently testing.

I'm living in hope. When you consider that Athlon's aren't P4 compatible, because of the lack of SSE2 instruction set, and the requirements are for P4 I, personally, feel that Adobe are doing us proud.

Here's hoping. I'll post more as I find out.
 
Upvote 0 Downvote
@ Madone, have you been able to re-create the fault? If so it might be a good idea to let them know on the User2User forum.
 
Upvote 0 Downvote
paul_w, no not yet.

I've tried, but nothing so far. I'll go post my info just in case there is an order of operations they need to look at.
 
Upvote 0 Downvote
For those of you still trying to cope with 32 bit Athlon chips and Lr2 there is now a fix which will be released in an update "soon". Quoting Eric Chan in a response to a query of mine on the u2u forum as to whether any progress had been made.

Here's hoping "soon" is soon!
 
Upvote 0 Downvote
32 bit Athlon XP users rejoice.

The new release of 2.1 has fixed the problems we were having with writing to .xmp and creating virtual copies.
I installed it about 2' minutes ago and those problems have gone. It also seems to be working mor quickly than 2.' at least the local corrections are doing even on my limited machine.

Big thanks to Adobe for this from me and I suspect from all other Athlon XP users as well. At least we won't hve to go out and buy new machines for a little longer!:D
 
Upvote 0 Downvote
Status
Not open for further replies.
Back
Top