could not complete your request because the file is not compatible with this version of photoshop

Harry,
>why does this only seem to affect .psd files?

I have no idea. That's just the way it is. As my astronomer professor used to say, "I cannot explain the universe to you; I can only describe it."

We are all users just like you in these user to user forums. We are not here to defend anybody nor to apologize for anybody. We can only offer solutions and workarounds when we have them.

At the top of this page you will find a Contact button to communicate with Adobe if you wish. You are not addressing Adobe here.

Again, why does this only seem to affect .psd files? I've never had a problem with any of the .eps or .tif composites of these files.

As per post #23,
> In all three instances, the file is irreparably and irretrievably damaged. If you are lucky, you may be able to recover the flattened composite, as you have discovered

I did try opening it in previous versions of PS and it did not work.

D.C.
>Unfortunately, this is a bug Adobe apparently can't or refuses to fix

With all due respect, that is nonsense! If you read the background on this or read the FAQ, you'll understand why Adobe is NOT responsible for the myriad possible network misconfigurations possible. It is up to your network administrator to be competent enough to address your network's unique issues, and test and maintain it.

It is unfair and unreasonable to expect Adobe to do your IT's job.

Please read: http://kb.adobe.com/selfservice/viewContent.do?externalId=322391&sliceId=1 for more info.
>Adobe, we WANT A FIX TO THIS BUG!!!!!

You are addressing your peers (who are trying to help everyone understand the issue), not Adobe!

Neil

If you want to work over the network then fix (or get an all apple) your network.

I've always worked over the network and never had a problem with corrupt files. Now I'm in a shop that regularly works on files that are 3 and 4 gigs and we still have no problem with corruption.

Adobe is just covering their butts (as had to be done on a billboard recently on 42nd street. What a bunch of puritans I'm surrounded by.

alan

Unfortunately, this is a bug Adobe apparently can't or refuses to fix. This has been a problem for YEARS and is still a problem in CS3. We've had problems with PSD files becoming "corrupted" when editing over the network. Fine, we can work locally.

yet, today, we had a user who created a large PSD file locally, saved, closed PS and placed the file in Illustrator (where it is fine). tried to re-open file in PS and this error pops up. yet, there is NO fix for this, other than a PSD layer recovery tool which is a real bear.

Adobe, we WANT A FIX TO THIS BUG!!!!!

This is the boilerplate text I use in connection to saving to a network (please NOTE the part where it explains that normally, it does work, but that it is impossible to troubleshoot someone else's network remotely, and that's why it's not supported by Adobe):

If you are opening files over a network or saving them to a network server, please cease and desist immediately in the event you are currently experiencing problems with one or more files. Working across a network is not supported.

See:

http://www.adobe.com/support/techdocs/322391.html

Copy the CLOSED file from your server to your local hard disk, work on it, save it again to your local hard disk, close it, and copy the closed file back to the server.

Of course, the fact that Adobe does not support working across a network does not necessarily mean it won't work. It should.

Adobe's position is that there are too many variables in a network environment for them to guarantee that everything will work correctly in every network, especially given the fact that if something does not work properly, it's probably the network's fault, and Adobe has no way of troubleshooting your network.

If you can't work locally, you are on your own, and if something happens, you're on your own. If you must work from a server, make sure your network administrator is a competent professional.

When problems arise, a lot of valuable work can be lost.

Isired,

I know of only three causes for a this specific problem:

1.-- The file was damaged by NAV (Norton Anti Virus);

2.-- The file was opened or saved on a server across a network;

3.-- Some hardware malfunction damaged the file,

In all three instances, the file is irreparably and irretrievably damaged. If you are lucky, you may be able to recover the flattened composite, as you have discovered.

As a last resort, if Graphic Converter doesn't open it, nothing will.

> the directory would be bad on 3 diff macs (and now 1 PC)?

No. If a file is damaged on one computer, for whatever reason including a bad directory, it will be bad on any computer you subsequently transfer the file to.

>even copied file to local HD's...

Aha! There's the cause of the damage. You are working over a network, opening and/or saving files to a server. That's a big no-no!

(See next post.)

buko, should have said 'thanks' first. things are stressful now... if all else fails, will run check tonight.