A strange thing has begun happening in Photoshop CS2 (running under Win XP SP2), something I've never seen before.
In Lightroom 1.3 I convert a Canon 5D file to 8-bit TIFF format (no compression). Then opening the TIFF file in CS2, I draw a marquee, fill it with white, deselect the marquee, and add type over the top of the white "bar" I've just created -- a simple task that needs doing with all files that are part of the current job. I select Save As to save the file with these changes to a new name -- TIFF format -- keeping layers intact. Then the fun starts...
Normally when you save-as with layers, Photoshop warns that this will increase the file size. But starting with yesterday's session in PSCS2, the warning stopped appearing. (I have never checked the box that would cause PS to suppress the warning.)
Normally a save-as operation to TIFF format produces a dialog box containing selections for (among other things) type of compression. Starting yesterday the dialog box stopped appearing. Instead, Photoshop starts saving the file right away. And another oddity: instead of taking its usual 5 to 10 seconds, PS is now taking 20 to 30 seconds to do the save.
And the final blow: the resulting TIFF file is always corrupt. It can't be viewed or worked with in any other program -- Qimage, Irfanview, FastStone Viewer, you name it. It appears either as a random pattern of garbled colors, or as -- of all the strange things -- a black and white version of itself, very small and tiled about 20 times within the image area. Weird...
Any file derived from it will also be corrupt. (For instance, if after the initial save I flatten layers and save again as TIFF using yet another name. That time I do see the dialog box containing the choice of TIFF compression -- I always select 'none' -- and the resulting file is also unusable.)
I'm baffled. Two days ago the same procedure was producing files that were not corrupt (and the CS2 dialog allowing a choice of TIFF compression did appear any time files with layers were saved). If anyone Out There has a suggestion about what might be happening and how to fix it, I would greatly appreciate the advice.