Yes, I have PS CS2. Yesterday I was converting RAW to Tif's and doing layer masks. After closing PSCS2 AND the Bridge, I was looking at my working directory and found an NEW file called " ~pscf.tmp ". Looks like some kind of temp file that didn't get erased after closing down PSCS2 or the Bridge (wished when I closed PSCS2 the bridge would also close). Any idea what the small ~pscf.tmp might be ? ITS 24MB BIG and taking unneccessary hard drive space.
I dont have a complete answer, but something similar happened to me as well. Not just once. The first error was while running batch when I got the message that PS could not close the file because it was in use. The image that failed was gone from the folder and there was the first ~psXXX.tmp file. I reran the batch and it worked the second time.
Then it happened three or four times while doing interactive updates by selecting 3-5 files at a time. Each time, I could not close a new tmp file appeared. The files would not close until I manually removed the tmp file.
It seems to be intermittent. When it fails, the input image file has been removed from the folder. Im not sure if it could be recovered from the tmp file. Finally, I stopped and re-cycled PS. Well see if it happens again soon.
If I suggested that this might be a defect in CS2 Im sure that team Adobe would jump all over me. So, I wont. Working as coded. Im on Windows XP/Pro (Media Edition).
If this happens to you, I suggest trying to find out what image file is now missing.
I will watch for the frequency of occurance and what I was doing at the time and see if there is any repeatable relationship. IF the PS Team watches these lists, we might like some feedback or some suggestions on what we can do to keep if from occuring.
I have PSCS2 flagged to open the Bridge, and start only PSCS2. Wish I could get the Bridge to close the sametime I close PSCS2. I don't have a need to have the Bridge open alone.
WinXPpro 2.8ghz P4, 1 gig ram. PSCS2 cache set up on external 60gig firewire hard drive.
I finished editing a 90mb .tif. I tried saving it to a NEW file called filename.bmp. It went away and returned with a 8, 16, 24, 32bit dialog box preselected for 32bit color depth. I selected 24bit.
PSCS2 returned with "Could not save F:\..\filename.bmp, because the file is already in use or was left open". Hmmm, this is not correct because the filename.bmp had not been created yet. I was attempting to save it to a .bmp file.
So I checked to make sure that the .tif I was working on had been saved. Then I closed it and reopened it and this time when I saved it as a filename.bmp it did save it. It also opened this filename.bmp in my active window.. which is correct.
The appearance of these very large *tmp files is happening to me on a regular basis. Twice I've had files larger than 100MB, both after heavy editing sessions with many layers. But it's happening on a regular basis and I've had to just hunt them down after a session. I don't know if the tmp files would stay after a reboot, but they do remain after closing out Pshop.
The _crop_XX.tif files seem to be something new. As I said earlier, I really believe that the ~psXX.tmp files are image files that are now missing (from the same folder).
Do the tif files behave like tif valid image files? Sounds like they are artifacts of a crop tool (ACR?).
Have you tried to rename one of the tmp files to a valid image extension to see if CS2 or anything else recognizes them? My laptop with CS2 is out of action for a few days. Else I would try to recreate one. It didnt seem hard to last week.
I looked at the MS KB article and also dont think it applies. CS1 on the same machine never failed. On the other hand, I have been unable to find any similar reports in the PS Mac forums.
I agree.. yes I was doing a copy to layer, then did some flipping horizontally, and resizing the layer to fit... and then flattened it.
I did delete the 232mb of junk files. Needed the F:\ hard drive space for more important work.
I did find another stray file ~psDC.tmp 71.9mb This one I copied/renamed to theaterxxxx.tif (don't laugh). Tried to open it in PSCS2 and PSCS and both programs said 'Could not complete your request because it is not the right kind of document'. Well it was worth a try.. never know it might have worked. This time it did not
Any other thoughts ?? I might have to delete CS2 and revert back to using CS. It is almost not worth having to do the file/folder maintenance every day deleting the files that CS2 creates but does not dispose of properly.
I hope someone from the CS2 team is reading this thread.
There is a similar thread under the Bridge Windows forums. Rags Gardner, "Bridge bug - unlinks files, lost forever" #7, 6 May 2005 1:38 pm </cgi-bin/webx?13@@.3bba34ae/6>
Jim Drew, Adobe Bridge QE is participating there.
Most of my failures were with Kodak SLR/n 12MP raw files. About 150 in the initial folder. About 80 that I was playing with for various tasks. The first failure I noticed was using the Image Processor to convert these 80 selected raw images with various ACR adjustments and crops to PSD. The target was a new, empty xxx/TEMP/PSD folder. The Bridge was of course in a totally different path tree with the raw files. The next failure was running a batch action/script against this new folder directly from PS because the IP would not run the action. This was simply updating some info panels in all the files in the folder, no Bridge selection. Next were several failures selecting 3 to 6 images at a time and making trivial layer alignments manually to a copyright logo shape layer.
Again, this was Windows XP Pro, 3.4GZ dual processor, 1GB main.
I've been having the problem of very large .tmp files staying around since I installed CS2. Have been watching it closely and find that they stay under the following conditions: heavy editing on a 16-bit tif, at least 4 layers, most have masks. At some point I Apply the Mask to the layer. These are the only common elements I can identify. Last night after one such editing session on only 1 image I found 4 .tmp files ranging from 23-74MB ea.
"I'm reading it - but it doesn't make any sense, nor can we reproduce the problem." What does not make sense? It appears alot of folks using PSCS2 are finding that it creating and not properly disposing of ~psXX.tmp and _crop_x.tif. So I am not alone on this issue.
The renaming of these files was only a test to see if the tmp and _crop files contained any usable information that would allow us to backtrack to the event that might have been causing the creation of these files. The outcome would be then to trace it back to the section of PSCS2 programming that would require correction.
Yes, I do software beta testing for a few companies but not with Adobe.
PSCS appears to be stable, whereas PSCS2 is creating undesirable issues.
I am using a networked XPpro SP1, Dell 2.8ghz, 1gb ram, 60gb internal HD, and 1 external 60gb HD. PSCS2 is on the internal HD. All my production (where the tmp and _crop files are located) is on the external F:\\ 60gb firewire HD. PSCS2 was installed using default settings. Both internal and external drives are at 60% used space 40% free space.
Another wierd event: I have PSCS2 start the Bridge on loading. But when I Exit PSCS2.. the Bridge does not close. I will exit PSCS2 first, then the Bridge sometimes gives errors when closing.
Try having PS set not to open bridge automatically, and then open it manually. I do the latter and have not seen these temp files appear. If this solves your problem, then there would appear to be a bug related to automatically opening bridge.
360 - please stop exaggerating and give us the details.
It doesn't make sense because you seem to be leaving information out.
And it doesn't make sense because we haven't seen the problem nor should it even be possible without Photoshop crashing (in which case Photoshop cleans up the files the next time it launches).
Now, it is possible that some interaction with Photoshop, Bridge and maybe some third party application is causing this. But I don't know how. And I don't know which application(s) are involved.
Does this happen with JUST Photoshop running?
Does it happen with JUST Bridge running?
What utilities do you have installed?
What command(s) seem to create these files?
And please create a topic in the Bridge forum about it not quitting and giving errors when closing - and, again, provide details.
In my situation, seeing these residual .tmp files, I am working on .tif files that had been converted from RAW a few sessions before; so, I don't think the format makes any difference.
I am doing old photo restoration (yesterday I was working on a tintype), using many layers to which are applied various filters and then masks. Sometimes I flatten the final file and sometines I don't. Sometimes I'll merge down a layer; sometimes the file will have layer Groups, but have not determined any particular manner of working that is connected to the residual .tmp files. I also use Ctrl-Z a lot to roll back changes I don't like.
When I work I have both Bridge and Photoshop open, as I use Bridge to scan my files before deciding which one to work on.
I have encounterd one thing that may be connected to these .tmp files: since Ive been using CS2 I frequently get a message on saving a file that says, in effect, that CS2 cannot save the file as it's being used and to try later. I interpret that to mean that it may still be applying changes to the file and can't write them back to disk yet. If I wait about 10-20 seconds I can save the file. This message may occur several time during a work session as I save frequently. I've always worked this way but never saw the message until CS2.
Pierre, FWIW, I'm seeing them, too. Mine are not on an external drive, I found two of them on my PS scratch partition, which is an internal drive. Haven't had time to test to see what specifically causes them or whether they are created when running PS CS2 alone or with Bridge.
That's a good question. I don't have any external disks, but all my data files, which of course include my images, are on my second physical drive, Drive D. I always find the .tmp files laying around in the working subdirectory. Using Bridge I am able to see and then delete them.
After reading your post I went into the designated temp folder and did find 3 .tmp files dated this morning, when I first started some editing.
The directory was c:\Documents and Settings\Judith Lipmanson\Local Settings\temp\Adobelm.cleanup.0001.dir.0002\ and the 3 files were
CS2 has been leaving a file called AdobeFnt10.lst on my desk top after closing?? It's 4kb in size. It happens randomly, after using Bridge and CS2, no other programs open. I haven't noticed it when only using CS2.
This is a new Dell Computer XPS, 4gb ram, 2 hard drives, one for scratch.
I was playing with my laptop today (activating CS2). I found one of the tmp files in the recycle bin. I restored it, and changed the name from ~ps182.tmp to ~ps182.psd. As I had suspected, PSD was the correct extension. The thumbnail now shows in the Bridge and PS opens it fine. It is one of the images that was lost earlier.
This was from an interactive session, moving a copyright layer in 3-6 images at a time. The Bridge may have been running but it was not active. The final step was to simply close and save the image in its original location from PS.