Adobe Community: The disk copy was changed since you last opened it.

kevin4545

Currently Being Moderated

The disk copy was changed since you last opened it.

Jan 18, 2012 8:05 PM

..... Do you want to save it anyway?

I'm starting to get this message again a lot. It went away for awhile, and is now back.

It started with CS5.

I think Adobe blames it on other software but cannot pinpoint it?

Can anyone fill me in?

10568 Views 79 Replies Latest reply: fcastro75, Dec 12, 2012 2:16 AM

Replies 1 2 Previous Next

Currently Being Moderated

1. Chris Cox,

Jan 18, 2012 8:23 PM in reply to kevin4545

Report

See the previous discussions. Yes, it is caused by something outside of Photoshop.

|
Mark as:
Currently Being Moderated

2. kevin4545,

Jan 18, 2012 8:37 PM in reply to Chris Cox

Report

Thanks Chris. Can you reveal/distilll on this new simplified thread what I need to due to eliminate it?

(I went through the morass of threads and could not decipher it)

|
Mark as:
Currently Being Moderated

3. Tai Lao,

Jan 18, 2012 8:39 PM in reply to kevin4545

Report

You can't eliminate it. You just live with it.

____________
Wo Tai Lao Le
我太老了

|
Mark as:
Currently Being Moderated

4. Tai Lao,

Jan 18, 2012 8:42 PM in reply to kevin4545

Report

As for the cause, it can be any of a variety of things: the Finder itself, a font manager (e,g. Suitcase), Dropbox, etc.

____________
Wo Tai Lao Le
我太老了

|
Mark as:
Currently Being Moderated

5. Chris Cox,

Jan 18, 2012 11:21 PM in reply to kevin4545

Report

Unless you can find which other app it is, you can't do much.
And there are indications that (at least on MacOS) the problem may be with the OS, Finder, or TimeMachine.

|
Mark as:
Currently Being Moderated

6. kevin4545,

Jan 19, 2012 8:59 AM in reply to Chris Cox

Report

Thanks T and Chris.
Appreciate the honesty.

But Chris, even if it's the fault of something else, it started with CS5, and it only comes up with this app, no?

If that is true, there must be something with the devolepment with CS5 that is not happy with certain things on the OS.

I'm suppose you guys are working on it. Maybe it'll just diappear one day.

|
Mark as:
Currently Being Moderated

7. Chris Cox,

Jan 19, 2012 3:06 PM in reply to kevin4545

Report

Photoshop does a lot of error checking when opening and saving files -- more than most other applications. So Photoshop catches more errors, and reports them to the user.
Yes, we keep working on issues like this, and rarely find them to be actual bugs in our code - but find lots of third party bugs.
Unfortunately, many of these are system specific and won't reproduce elsewhere.

|
Mark as:
Currently Being Moderated

8. kevin4545,

Jan 19, 2012 4:46 PM in reply to Chris Cox

Report

Thanks Chris, I see. I don't want to rehash anything, but I think most laymen like me would be befuddled that PS is checking something that touches another app or utility and then bringing up an error.
I'm ok with it -- T's philsoply is zen like and well just wait for it to pass one day.

|
Mark as:
Currently Being Moderated

9. Chris Cox,

Jan 19, 2012 6:38 PM in reply to kevin4545

Report

Imagine if you're working in Painter and Photoshop -- you don't want Photoshop to save over what you just saved in Painter, you'd probably like to know it was changed instead of losing that work.
And Photoshop can see if the file changed and ask if you want to open the updated file.

|
Mark as:
Currently Being Moderated

10. kevin4545,

Jan 19, 2012 7:21 PM in reply to Chris Cox

Report

Sort of hard to get my head around that Chris. I know if would be tiring to expand on that. I get the premise a bit. but maybe you can make this a prefernce in the future -- like with maximize capability..?

|
Mark as:
Currently Being Moderated

11. Chris Cox,

Jan 19, 2012 10:29 PM in reply to kevin4545

Report

We can't easily make error checking a preference.
("would you like you knife with a handle, or do you like bleeding a lot?")

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

12. Noel Carboni,

Jan 20, 2012 7:11 AM in reply to kevin4545

Report

You seem to be concentrating on the effect of the error checking... The implication above is that something the system is doing is (unexpectedly) touching the file. Wouldn't it be best to understand what that is all about and correct it, anticipate it, or configure around it?

Is this happening on all Mac systems?

-Noel

|
Mark as:
Currently Being Moderated

13. kevin4545,

Jan 20, 2012 7:22 AM in reply to Noel Carboni

Report

Neil, that's for me? don't understand. The error comes on only with one app. PHotoshop. It comes up after you save a file. That's it. It's a total nuisance. I click command S to save. and then the message comes up.
It's not even an error message. It's saying something in the file has changed -- of course, I'm working on the file. I decide it's time to do a save. And it's asking if I want to save, something has changed.

One of the all time nuisances of a major software. I'm going to live with it as T says. If you know more what this is about let me know. I'd love to get rid of it.

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

14. Noel Carboni,

Jan 20, 2012 7:30 AM in reply to kevin4545

Report

It was kind of addressed to Chris... All I'm saying is that there's an implication here that something is systemically touching (or possibly altering) files while you are editing them, and that's most certainly not something that should be tolerated or ignored.

Either it's the normal way a Mac system works (which I don't know but I doubt) or something you specifically have running on your system is causing it, which you should understand and possibly change. If the former (normal operation), then Adobe needs to change the way Photoshop works, because the error message is bogus.

-Noel

|
Mark as:
Currently Being Moderated

15. kevin4545,

Jan 20, 2012 7:33 AM in reply to Noel Carboni

Report

Noel, you don't get this message?
In previous versions I never saw this. Now it comes up. I love to know how to remove it.

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

16. Noel Carboni,

Jan 20, 2012 7:43 AM in reply to kevin4545

Report

I get it just fine.

In computers nothing is magic. Even in Macs.

Something is triggering logic in Photoshop that checks to see if any changes have been made to a file since you opened it. You would not normally expect that to happen. Another poster above has indicated it happens a lot and should just be ignored. I say get to the bottom of why it's happening because it just might be important.

It might be that OSX is now doing something it didn't when your version of Photoshop was designed or it might be that something you've installed is doing it. Any reason not to try to find out just what it is?

-Noel

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

17. Noel Carboni,

Jan 20, 2012 7:47 AM in reply to Noel Carboni

Report

To further what I just said, if it DOES turn out to be something you've installed or configured on your system that's unexpectedly touching the file, then whose job do you think it is to diagnose and correct the problem?

-Noel

|
Mark as:
Currently Being Moderated

18. kevin4545,

Jan 20, 2012 8:00 AM in reply to Noel Carboni

Report

Noel writes:

"Any reason not to try to find out just what it is?"

I'm all ears Noel!

|
Mark as:
Currently Being Moderated

19. kevin4545,

Jan 20, 2012 8:01 AM in reply to kevin4545

Report

BTW, I am very grateful to Adobe, PHotoshop, and Chris Cox --great software. Not moaning here.....

|
Mark as:
Currently Being Moderated

20. Marian Driscoll,

Jan 20, 2012 8:05 AM in reply to kevin4545

Report

kevin4545 wrote:

...In previous versions I never saw this. Now it comes up. I love to know how to remove it.
Others have seen this in many different versions of Photoshop. Search the forum for many discussions about this. When you say that you cannot decipher it, neither can anyone else. It is a transient quirk. It all comes down to something unique to your system. Something might have changed around the time you added CS5 but that does not mean CS5 caused it.

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

21. Noel Carboni,

Jan 20, 2012 8:06 AM in reply to kevin4545

Report

Unfortunately I'm no Mac expert - I'm all about Windows. But surely someone here should be able to direct you to ways to find out what is touching your file unexpectedly, beyond just vague references to parts of OSX or just telling you to ignore it. I was just encouraging you not to give up on just those answers.

-Noel

|
Mark as:
Currently Being Moderated

22. kevin4545,

Jan 20, 2012 9:17 AM in reply to Noel Carboni

Report

Marian,
let me ask. Are people noticing this more with CS5? I've never seen it before that edition.

Now of the 100 appications I have, this only comes up with Photoshop CS5.

Beyond that I have no idea how to kill, if you or anyone else on the forum does let know.

If T says, and he knows a lot, that you have to live with it -- I'm not expecting then too much help here.

|
Mark as:
Currently Being Moderated

23. kevin4545,

Jan 22, 2012 7:04 PM in reply to kevin4545

Report

Ok, it happend again, right after doing a few things to the file in PHotoshop, clearly it's a photoshop thing 100%. Though I respect Noel and Chris so I posted to a few Mac forums and they all concur, they are also aware of the problem, lot of Photoshop users there, and that nothing substantial changes to the file on the Mac OS and the issue is 100% with CS5.

One of my favorite posters, Mac genius -- , summed it up (with his permission) :

OS X may indeed touch the file (for example, it may read the file's name and add the file to the Spotlight index), but that doesn't actually change the file.

I am skeptical of Adobe's claims, since earlier versions of Photoshop don't have this problem. There are actually several different dates and times stored with a file on OS X: the date and time the file was created, the date and time the file was modified on disk, and the date and time the file was last accessed. I think, based on what I've observed, that in the past, Photoshop looked at the date and time the file was modified, which is what it should do; it appears that CS5 looks at the date and time the file was accessed, which is the wrong thing to do (as the file may be accessed by, for example, indexing it or placing it in another program--but that does not actually modify it).

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

24. Noel Carboni,

Jan 22, 2012 7:10 PM in reply to kevin4545

Report

I wonder how he determined it's looking at the "last accessed" date. That would indeed be wrong operation. Chris, that should be easy to determine.

For what it's worth, on Windows the very same concepts apply (though the implementation is of course different), and I have never seen it myself nor heard anyone else claim this problem has happened to them on Windows. I'm not all-knowing, but it seems to me to be Mac-specific.

By the way, I think in context the word "touch" has more specific meaning than Mac Genius has led you to believe. "Touching" a file in the Unix world usually means changing its modification date, not the last accessed date.

-Noel

|
Mark as:
Currently Being Moderated

25. Chris Cox,

Jan 22, 2012 11:42 PM in reply to Noel Carboni

Report

Nope, we're looking at the file modification date, not "last accessed".

|
Mark as:
Currently Being Moderated

26. kevin4545,

Jan 24, 2012 7:52 AM in reply to Chris Cox

Report

From the Mac guy:

"When I have observed this problem happening, I've looked at the modification date of the file Photoshop wrongly believes was changed, and it's the same as it was...so something weird is going on there. Whatever the problem, Photoshop CS2 behaves correctly, which makes the "It's OS X!" claim sound very fishy indeed."

-----

Noel, it seems this issue is just for the Mac group then if you say it's not with Windows. Photoshop has a really weird bug in CS5 with Mac users. Hopefully they will fix it. I wish you were on a Mac Noel!

|
Mark as:
Currently Being Moderated

27. Marian Driscoll,

Jan 24, 2012 10:04 AM in reply to Noel Carboni

Report

Noel Carboni wrote:

...I have never seen it myself nor heard anyone else claim this problem has happened to them on Windows...
Here is Windows doing the same thing...

Windows has the same file check and error message. What Windows does not have is a wonky OS or background process that is modifying the file as much as OS X might. (Do not insert platform flame war here. I'm just pointing out something I observe as a user of both platforms.) There's good reason to believe OS X can be improved in regard to how the OS handles image files.

For the related discussion to this topic, check here. Google is your [gossipy] friend.

There is troubleshooting logic that is being ignored here. If this was truly a bug for all users of PSCS5 on Mac, all users of PSCS5 Mac would be seeing this. If this was unique to CS5, we would not have seen similar posts from before the advent of CS5. The fact that it is spotty indicates that certain users have their system configured in unique ways. You need to figure out what is unique about your system. This was mentioned by this topic's first responders.

|
Mark as:
Currently Being Moderated

28. kevin4545,

Jan 24, 2012 10:43 AM in reply to Marian Driscoll

Report

Marian,
I open a file in photoshop, I work on it for 2 minutes, then this nusance sign comes up. It's the fault of the OS?

It only comes up in PS, not Word, Excel, or 100 other apps, only Photoshop etc.

But listen I'm all ears.

I have not heard one suggestion on what to do.

If you think I should post more on Mac forums, I don't mind trying that...

|
Mark as:
Currently Being Moderated

29. Marian Driscoll,

Jan 24, 2012 11:12 AM in reply to kevin4545

Report

You've had suggestions about the possible causes and it was assumed that you would consider disabling those possible causes.

From where are you opening the file? Is the file on your desktop where the OS always generates icon previews? Save your files elsewhere. Are you opening it from an open Finder window with a large icon preview? Don't generate previews with Finder. Uncheck show preview column in Finder's display. Are you running TimeMachine? Try life without it. Are you running anti-virus? Disable it. Are you using Spotlight? Turn it off.

You have never stated what you have running on your system or what troubleshooting steps you have taken. I don't even see a mention of which kitty you are using. Meet us half-way.

From the very first post you have been told that it is any number of things. You need to experiment to see which thing it is.

|
Mark as:
Currently Being Moderated

30. kevin4545,

Jan 24, 2012 11:15 AM in reply to Marian Driscoll

Report

Marion, I running 100 things. I Don't run antivirus, macs don't need them.

Images are on exeternal hard drive. I don't think previews are the issue as they have not been in issue on last 7 versions of photoshop.

Honestly, I did start using time machine for the first time a few months ago.

But really, if CS5 has an issue with Time Machine, the engineers should fix that, Time Machine is pretty important...no?

|
Mark as:
Currently Being Moderated

31. Marian Driscoll,

Jan 24, 2012 11:40 AM in reply to kevin4545

Report

kevin4545 wrote:

...I Don't run antivirus, macs don't need them...
This ends my ability to further converse with you. You're just not aware of your machine and have an attitude that does not seem to want to learn.

If you are running Snow Leopard or Lion (we still have no idea which), you are most certainly running some level of anti-virus. OS X comes with a trinket to catch a few bugs. You can get more advanced antivirus tools as well.

The usefulness of Time Machine varies. There are practical reasons for a power user (such as a Photoshop user) to disable it or limit its function.

|
Mark as:
Currently Being Moderated

32. kevin4545,

Jan 24, 2012 11:57 AM in reply to Marian Driscoll

Report

I'm all ears Marian.

I'm not a Mac genius, but I am more aware of my machine than probably 99% of mac users in the general population.

I love to learn, and would love to hear what you have to say.

I don't think you have one iota of knowledge how to solve this issue and hence you are throwing out generalzations that are totally irrelevant to this thread.

I don't think Noel or Chris or anyone has any idea about this isse.

I think T is one of the smartest PS guys on the board and he has given up too. He advice it just live with it. So that's what I'm going to do!

But please don't put the blame on the Mac OS, or users who come on the forum asking for help.

|
Mark as:
Currently Being Moderated

33. Marian Driscoll,

Jan 24, 2012 12:12 PM in reply to kevin4545

Report

I don't think T is running CS5. If he did, I would suspect that he would know how to get around this problem of yours. He seems more familiar with his system.

I'm throwing out generalizations to someone who is so ambiguous that he cannot even describe which kitty he is using. How is someone (such as the Adobe engineer who gave you some attention here) supposed to understand the problem that needs to be fixed if you cannot fully describe the problem?

I run Photoshop on Mac. I don't have this problem. So you are correct that I have no iota on how to solve your problem. Only you can solve this. ...not an Adobe engineer.

I put no blame on anyone asking for help here. I blame people that fail to fully describe their problem and expect a detailed solution.

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

34. Noel Carboni,

Jan 24, 2012 12:14 PM in reply to Marian Driscoll

Report

Kevin, have you yourself actually verified that the file modification date is not changed (i.e., is set to a time before you started editing the file) when this message comes up?

-Noel

|
Mark as:
Currently Being Moderated

35. Marian Driscoll,

Jan 24, 2012 12:20 PM in reply to kevin4545

Report

kevin4545 wrote:

...But please don't put the blame on the Mac OS...
We are fully entitled to blame Mac OS with silliness like this:
http://forums.adobe.com/message/3638147#3638147

OS X and Finder have some weird crap going on. Mac OS can certainly be improved. You don't have to be embarrased that you bought into a wonky system.

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

36. Noel Carboni,

Jan 24, 2012 12:28 PM in reply to Marian Driscoll

Report

Heh. Windows is wonky too, just differently so.

-Noel

|
Mark as:
Currently Being Moderated

37. kevin4545,

Jan 24, 2012 12:40 PM in reply to Noel Carboni

Report

Honesly, you guys are lot smarter than me, so I going to declear and move on. Perhpas you are correct. so my apologies. I think you will agree, this would be quite hard to eliminate or solve on a forum chat.

|
Mark as:
Currently Being Moderated

38. kevin4545,

Jan 24, 2012 4:13 PM in reply to kevin4545

Report

final PS, received a nice PM from T, turned my head around, did not know or think about spotlight and time machine etc, but, devils advocate, I gave the gist of that info to my Mac friend (I just a dolt by comparison, so don't get mad at me), but this was his interesting reply

..."
.......... But what he is not paying attention to is that even though Time Machine, Spotlight, and other apps may touch a file (by adding it to the Spotlight index or by adding it to a list of files to be backed up), they don't modify it. The modification date remains unchanged; in fact, it would HAVE to, or else it would be worthless!

At the end of the day, Photoshop is reporting that a file has been modified when the file has *not* been modified. That is incorrect on Photoshop's part no matter what excuse is given.

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

39. Noel Carboni,

Jan 24, 2012 4:25 PM in reply to kevin4545

Report

It's kind of silly to be relaying info between forums, where there's altogether too much being unsaid...

Here's my response to:

At the end of the day, Photoshop is reporting that a file has been modified when the file has *not* been modified. That is incorrect on Photoshop's part no matter what excuse is given.

The implication in the statement above is that only Photoshop could be at fault. That's a bogus statement when nowhere has it been proven here that the file modification date/time is not being changed by some other program! For all you know you might have some malware that's going through your file structure and touching the modification dates on your files.

Ask yourself this, Kevin: Have YOU seen it detect a file modification when the modification date is unchanged?

You need to delve into this YOURSELF, or just ignore it as you have said. Details matter!

-Noel

|
Mark as: