Hi 
For some reason a set of 16 temp files is created on my store drive (D:\) when i start up PS. its not the scratch drive. that is located on my ramdrive. these files are named "****_********_MVM_*.tmp" where the first and second line of stars is a random number while the last star is the numbers from 0 to 15. all the 16 files will be named the same but whith a different count at the end.
this is really bugging me since that disk is for storing ONLY (eco green crap 2tb drive), and it looks ugly to. anyway, all the temp files are at 0kb and i cant seem to find any way to 'fill them' so i have no idea what they are for.
what i want is to move them to a specific folder or at least another drive. A:\ in my case
--------
Adobe Photoshop Version: 12.0 (12.0x20100407 [20100407.r.1103 2010/04/07:14:00:00 cutoff; r branch]) x64 (CS5 Extended)
Operating System: Windows 7 64-bit
Built-in memory: 8183 MB
Free memory: 4488 MB
Memory available to Photoshop: 7183 MB
Memory used by Photoshop: 55 %
Video Card: NVIDIA GeForce GTS 250
Video Card Memory: 1024 MB
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS5 (64 Bit)\
Temporary file path: A:\Temp\USERTE~1\
Scratch volume(s): A:\, 2,00G, 1,91G free (RAMDRIVE)
C drive 25gb free (ssd)
D drive 1,5tb free (store)
Explore related tutorials & articles
104
Replies
Hi Chris,
as I said here those files are created when f.e. the Lens Correction Filter or HDR merge was launched. It was 221 MB large when I launched lens correcting to a 100MB PSD (see the last allocation size statement in the dump of Procmon) and filled with zeros 😉
Hi,
thank to your post I know I should have used process monitor instead of process explorer.
I must mention those events came right after I open a file (left.png, 183 bytes, on a 12gb ram system). C and E drives are ticked in the scratch disk, not F and G. Nothing was done on the file, simple opening (no filter, operation, script, or anything else).
Don't know if that could help.
Regards
Bruno
ablichter wrote:
Those files are always generated in the root of a volume and it's totally unpredictable on which.
Not true on every system.
Armed with the new information (specifically that Merge to HDR Pro and Lens Correction could be responsible), I ran ProcMon and while capturing events (filtered on Process Name is Photoshop.exe) on Win 7 x64 Ultimate, I ran Merge to HDR Pro using Photoshop x64 12.0.2 and two images as input.
Files with MVM in the name and matching the aforementioned pattern were observed being created in my temporary folder (C:\TEMP, which is identified by both my User TEMP and TMP environment variables).
The specific file pattern was 6012_565852036_MVM_0.tmp through 6012_565852036_MVM_15.tmp, and they initially were accessed in numerical order. These were created *just* after the plug-in file HDRMergeUI.8BF was read.
Then about half a minute later, they were all accessed again, but this time in reverse numerical order (i.e., 6012_565852036_MVM_15.tmp through 6012_565852036_MVM_0.tmp). Notably this followed not long after another temporary file, PhotoshopHDRtmpa06215.pfm was accessed, and the MVM file accesses were interspersed with writes to C:\$LogFile. No C:\$LogFile could later be found.
For anyone investigating further, a ProcMon log file encompassing the entire Photoshop run above can be found here: http://Noel.ProDigitalSoftware.com/temp/Logfile_Containing_MVM_Files.zip
Notably during the Merge to HDR Pro run, an "Updating Lens Database Cache" message was displayed briefly.
The nnnn_nnnnnnnnn_MVM_n.tmp files were accessed only in the two blocks mentioned above, and were NOT left in my TEMP folder after the Merge to HDR Pro operation was completed and Photoshop was closed.
Are these files a bother somehow? They seem to me to be just transient temporary files. Is it because they're showing up in unexpected places that they are being discussed? Are they not being deleted under some conditions?
For those of you seeing these files, what are the values of your TEMP and TMP environment variables? Type SET T into a command prompt to check.
C:\>SET T
TEMP=C:\TEMP
TMP=C:\TEMP
C:\>
Just a hunch, but perhaps you can set a deterministic folder for these files if you create a simple, short folder name containing no spaces for your temporary files and set your TEMP and TMP environment variables to point to it.
-Noel
Not true on every system.
conditional
true on one 64 bit Win7 with only one partition, C:\temp; files are in C:\root
as well as on one 64bit Win7 with two partitions, C:\temp; files are on C:\root and D:\root
and one 64bit win7, nine partions, C:\temp; files are on M:\root and N:\root only, Not C: - D:, not on O: - R: nore X:)
No files related to this issue in C:\temp
Did you reboot after setting up TEMP and TMP variables to point to C:\TEMP?
No need for that. Every app wich would be started after you changed this env variable, will recognize it.
An active command prompt doesn't, because it runs in it own "sandbox"/context. Any new started command prompt does immediately.
Setting up C:\TEMP has always been a good strategy, ever since wayyy back.
You are not alone regarding this
ps
I forget to tell that pointing temp/tmp to c:\temp is the first thing I do when setting up a system.
ablichter wrote:
No need for that. Every app wich would be started after you changed this env variable, will recognize it.An active command prompt doesn't, because it runs in it own "sandbox"/context. Any new started command prompt does immediately.
It used to be the system would notify all running apps of the environment change right away. That doesn't seem to be as sure a thing any more with Windows 7 (or it could be with certain apps or certain conditions). This is based, for example, on observing apps like Visual Studio not responding to changes in the environment until restarted. The simplest way to be sure, since we're not completely sure what's causing these files, was to suggest a reboot.
ablichter wrote:
I forget to tell that pointing temp/tmp to c:\temp is the first thing I do when setting up a system.
Great minds...
-Noel
In addition to creating a C:\TEMP folder on your hard drive, you'll need to set two User environment variables, TEMP and TMP.
In Windows 7 here's how:
1. Click Start and type Environment into the search box.
2. When Edit environment variables for your account comes up, click it.
3. Look at the top list (User variables). If you see TEMP in the list, double click it. If not, press the [ New... ] button.
4. Set these values... Variable name: TEMP Variable value: C:\TEMP (make sure and not include any spaces)
5. Repeat steps 3, 4 for variable TMP
6. OK out.
7. Reboot your computer.
I will be interested to hear whether this causes those MVM temp files to go into C:\TEMP.
-Noel
AdChoices