I upgraded fro PS7 to CS3 a couple months ago and have been experiencing a few glitches. The biggest one is while working on a file, and doing an incremental save, I get a message saying the document could not be saved, because it is in use or has been left open. This frequently happens if I have my image browser open (but not that file) at the same time. Additionally I will get a PSD error message in the image browser (ACDSee). When I Reopen the image browser to that folder there will a new file in the folder with a name like: "~1455.tmp", that cannot be opened. If I change the extension to PSD, I can then open it. Which I figured out after several near heart attacks.
The interesting thing is; I have my scratch disk set to a separate physical disc, that is not the system disc, or the disc where the image files reside. So I'm rather baffled as to why PS is trying to write temp files to my image disc, let alone the parent folder of the file.
Oh, I should add, this is a Win XP box.
Any advice would be greatly appreciated.
Thanks,
Bill
__________________ You can only fish for so long before ya gotta throw a stick of dynamite in the water.
White Balance so easy, even our 5 year old can do it.- Melissa Strickland
Windows XP keeps track of the files that are open by each app to avoid file corruption due to two apps trying to write to the same file at the same time.
And, sometimes an app doesn't promptly close files -- even if it isn't displaying them or doing anything to the file at the time. It still has the file open, and that's all that Windows knows.
So... quit ACDSee and all of its open files are automatically closed. Do this before running PS3. Then you should not get the error messages in CS3 or ACDSee.
If you do see the "Document cannot be saved" message, do a "Save As..." in PS3 and give it a different name to avoid losing changes.
What's happening: When saving a file, PS3 initially saves the document as a temporary file. It does this so that the original file will not get trashed if there's an error during the save (E.g. if you ran out of disk space. If it just saved with the same name, you'd now have trashed the original file). If the PS3 save completes without errors, it then attempts to delete the original file, and then renames the temporary file with the name of the original. If any of these steps go wrong (e.g. because ACDSee has opened either the temp file or the original in the meantime), the whole process grinds to a halt and you are left with a temporary file that has a strange name but in fact is perfectly OK.