Participating Frequently

Question

16 temp files from [cursing removed]

Forum|Forum|15 years ago
November 3, 2010
14 replies
36028 views

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)

Windows

This topic has been closed for replies.

km79

Participating Frequently

I've the same problem:

If I connect my Backup-USB-HDD, Bridge writes about 20 tmp files directly on it.

I don't want this. I want Bridge to store its tmp files if it needs them on one definded location (and this should never be the root of any disk).

My settings are:

in edit/preferences/cache:

C:\Users\Konrad\AppData\Roaming\Adobe\Bridge CS5\Cache\

and in edit/camera raw preferences:

C:\Users\Konrad\AppData\Roaming\Adobe\CameraRAW\Cache\

But I find the .tmp-Files also under

E:\

F:\

and on USB-Disks

Astraion

Participant

If you have Bridge active, try closing it / exit and watch those files dissapear.

A

ablichter

Participating Frequently

If you have Bridge active, try closing it / exit and watch those files dissapea

It has nothing to do with Bridge or Photoshop in particular. This MVM files are generated by some Photoshop filters, in other words by 8BFs files. So Lens Blur and Vanishing Point will create them, but USM not.

I get those files on C:\, D:\ and (in the picture) partition M:\ and N:\ - most files are on M:\ (to the left)

2844_ = PhotoImpact

4960_ = irfanView

3380_ = Photoshop

I launched Lens Blur or Vanishing Point, whatever is compatible with the host.

The first number is the PID (process identifier) of e.g. PS - check taskmanager

They should be removed when the filter ended its work, was canceld or latest when the Host (PS, Irfan view, Photo Impact etc.) was closed, but sometimes they are not.

ps

by this I believe it is initiated by a method in the 8BF and not to change by settings in the host programm or the OS

pps

For those who do not know: you can use some PS Filters in other programs (so called Hosts) like Irfanview, PhotoImpact, etc...

A

AznGothic

Participant

I've read almost this entire thread (skipping parts about windows indexing) and it seems this hasn't been solved yet?

I have 3 internal hard drives and 1 external hard drive. My C drive is 320GB SATA I Western Digital 8MB cache, D is 320GB SATA I Western Digital 8MB cache, F is 750GB SATA II Western Digital Green 16MB cache and my external is a 2TB USB2.0 Seagate drive. Photoshop is configured to use F as the scratch drive and Windows is configured to point both TEMP and TMP to C:\Temp. My C drive has 43GB of free space, D has 13GB of free space, F has 358GB of free space and my external has 1TB of free space. My external drive goes to sleep if not being used as with most externals. As long as my external is plugged in, Photoshop writes the MVM files to it. I do not have any plugins installed (that I am aware of) and Photoshop only writes the MVM files if I open an image. First starting PS does nothing. If I open a JPG or BMP file I get MVM files on my external drive. If I disconnect my external drive before opening anything, it will default the MVM files to my F drive (config'd as scratch drive). When it writes the MVM files to my external, I get 16 files. With my external unplugged, I only see 6 MVM files on my F drive and 1 MVM file in my C:\Temp folder.

Now I don't mind the whole "slow down" with PS while it waits for my external to spin up. What I do mind though is that, as others stated, it looks ugly. But mainly that after PS does this, I can not disconnect my external the "safe" way by having Windows shut it off first. Even after I close PS. When I close PS, it will delete the MVM files off of my external but my external is still marked as "In use by another program." I never have problems disconnecting my external if I don't start up PS. It is only after I start up PS and it writes the MVM files to the drive that I can not disconnect my external.

Are there any solutions on how to get the MVM files to write to my scratch drive (or any othe drive for that matter) even if my external is plugged in? It seems like PS is looking for the largest drive or most free space to write to.

E

ELC Infosec

Known Participant

I'd like to chime in that I ran similar experiments (starting PhotoShop without the external drive connected.). I got the same results. It is odd that more MVM files get created on the external drive when it is connected than on the internal drive.

K

King Wardrop

Participant

It definitely seems to correspond with the amount of free disk space you have. My C drive just dropped below 64GB, and I copied about 30GB of files to my D drive to get it down to 50GB free space. As predicted, the temp directory on my C drive now only has 1 MVM file, as does my D drive; both of which had 2 files when they had over 64GB free space.

K

K_Ichijou

Participant

Well, I have 64bit system and two editions of Photoshop CS5 installed (32bit and 64bit)

My drives are C: (internal/partition, 7Gb free), D: (internal/partition 65Gb free), G: (external, eSATA, 540Gb free), X: (virtual, points to folder on D:, so 64Gb free)

TEMP & TMP variables set to D:\TEMP

Opening the same PNG file:

With 32bit Photoshop I have 1 MVM file on C:, 2 in TEMP folder, 9 on G:, 2 on X:

With 64bit Photoshop I have the same number of files in same locations. Even with same names.

After closing PS, they are deleted.

I've disconnected G: drive and now have 1 on C:, 2 in TEMP, 2 on X:

That's why I have a hunch that these files are used for indexing the free space on drives.

To test this I plug another hard drive, I: with 306 Gb free space and should have nearly 5 or 6 MVM files on it (if we assume, that there is one per 60Gb)

and... now there is something not right.

C: - 0 files, TEMP - 2 files, G: - 9 files, I: 5 files and X: - 0 files

It needs 16 *_MVM_*.tmp files and writes it on the drives with most disk space.

All the tests were conducted with the same PNG file. We may assume that the amount of files on the drive is ceiling(free_space / 64Gb), where ceiling is the minimal integer value greater than argument.

To test this, I'll make a copy of 9Gb folder on drive D: Now it should have 56Gb of free space and 1 _MVM_*.tmp file on it.

Yep. 1 on C:, 1 in TEMP, 9 on G, 5 on I, 0 on X:

Also, numbers are the following: C: 15; D: 14; G: 0-7, 12; I: 8-11, 13

Also, judging from the names of files, I'll say that it takes the disk with the most free space, writes there (free_space % 64) files, then grabs the second disk, writes there files by these rules, and so on.

Still, there is nothing I can say about why it wants 64*16 = 1024Gb amount of temporary files.

I'll try toying with some Photoshop settings and write what I have found later.

UPD: Reassigned drive letter of I: to Z: - now G holds 9 files, TEMP holds 1 file, X: holds 1 file, C: - 1 file. Z: has 0. What the hell?

E

ELC Infosec

Known Participant

I haven't had problems since following the switch of the environment variables to point to C:\Temp mentioned earlier in this thread.

Has anyone tried this solution and not had resolution?

K

King Wardrop

Participant

Changing my %tmp% and %temp% environment variables to C:\TEMP doesn't change anything for me. Every time I open a PNG file, no matter how I open it (drag and drop, file -> open, etc). I also renamed my prests and plug-in's directory, including only the Standard MultiPlugin.8BF plug-in required for opening PNG files, and the MVM files still get created.

I get 2 MVM files under my temporary directory (they're obviously not a problem), 2 in the root of my D drive, and 1 in the root of my E drive. My C drive has 66 GB of free space, D drive 92.9 GB free space, and my E drive 14.8 GB free space.

Opening any PNG, GIF or BMP file causes the MVM files to be created in those locations mentioned. JPG's are fine though, and do not create any MVM files. Closing Photoshop deletes the files, but they're still a pain in the ass.

N

NNogi

Participant

Hi everyone,

I just found this thread. Are there still no solutions? I have exactly the same problem with liquify in CS5 (Win7/64bit).

When I perform liquify operations, Photoshop eventually creates files like "3532_1566374_MVM_0.tmp" in the root of a random disc (which is NOT in the photoshop scratch list NOR my tmp/temp path).

Since that disc is very slow this problem causes an annoying bottleneck in my workflow. I have fast scratch drives for that purpose and cannot understand what the logic behind this behaviour could possibly be. However, I really feel it should be fixed.

In addition, since I also have several GBs of free RAM I do not understand why the MVM tmp files are created in the first place, but I guess that's another issue..

Any comments appreciated!

Thanks!

E

ELC Infosec

Known Participant

I want to add that I have this problem and it delays PhotoShop work by spinning up a sleeping external USB hard drive.

My workstation is Windows 7, 64 bit, 4Gb Memory. Drive C is set to the scratch drive, 128Gb free disk there. External drives are not selected in Preferences>Performance.

I open PhotoShop, and using Windows explorer to view the scratch drive, eight files named *_MVM_N.tmp are created when I open a simple PNG image. The opening process is slowed perhaps by referencing the external disk.

The temp files are deleted only when PhotoShop exits, not when the image is closed within PhotoShop.

This problem occurs in PhotoShop CS5, 32 bit.

Noel Carboni

Legend

Open a CMD window and type the following command:

SET T

What are the current values of your TEMP and TMP environment variables?

Try this and report back whether it controls the location of the temporary files:

1. Locate a fast drive that you DO want large temporary files on, with at least 10 GB of free space (ideally hundreds of GB free).

2. Create a root folder on that drive: TEMP (for example, C:\TEMP).

3. Set permissions so that the Users group or your username specifically has Full Control permissions on that folder.

4. Edit (or add) user environment variables TEMP and TMP to contain the path to the above folder (e.g., C:\TEMP).

5. Log off Windows and back on, then re-test.

-Noel

G

GeoffVane

Inspiring

I'm not going to read through all these posts.

PS CS5 is creating these MVM files where I don't want them.

I've got a special scratch disk for these kind of app files, but PS refuses to put them there.

Is there any solution yet?

(no I will not submit a bug report - Adobe should skim the forum themselves)

Noel Carboni

Legend

GeoffVane wrote:
PS CS5 is creating these MVM files where I don't want them.

Those of you reporting this issue, please list where the files are actually being put, and whether they're hanging around after Photoshop is closed.

I'm especially interested in whether the files are showing up anywhere other than the TEMP folder or the drive(s) you have identified as scratch to Photoshop.

-Noel

G

GeoffVane

Inspiring

It's not a big issue, but PS uses the drive where you open images from.

As soon as I stop using PS, they disappear.

I just want all Adobe programs to use my special scratch disk all the time. No data disk or system disk usage.

A

Anonymous

The files are locked by Photoshop (it can be see by example throw Unlocker) and the files disappear when Photoshop is closed BUT they are created only if I open image dusing drag and drop direct from web page in Mozilla Firefox. In MS Explorer it not happen.

I have set the environment correctly - TEMP and TMP to bigger disc, scratch file to RAM disc and it works.

I try research more...

E

emil emil

Inspiring

I just decided to check what this thread is all about but didn't read all posts carefully (too long). I gather that there is no conclusion yet about what exactly makes these files. Right?

I checked all my hard drives and I found a lot of these files created a month ago (I use PS almost daily) on the root of my largest partition (2 TB) and several more on a smaller partition (1TB) created on the same date. Nothing on C drive. I have 4 partitions and all are checked to be used as scratch disk space for PS. I deleted the files, opened/closed Photoshop doing a few things but no MVM files were created.

If it will be helpful to make some specific test, please let me know.

Psych0HoliCAuthor

Participating Frequently

and by the way if this helps understanding. when i open photoshop. these files is not on my drive, they will turn up first when i open a photo for editing, i do not have the 32 bit installed so i cant check if the problem is only with the 64 bit version. that would be wierd though

Chris Cox

Legend

Well, those are not Photoshop files as far as I can determine.

That leaves the OS, third party plugins, drivers, and malware.

Psych0HoliCAuthor

Participating Frequently

@ chris: those files are used by ps only. they are created when i open a file inside ps and disapears when i close ps. its not malware the os is freshly installed, leaves os and drivers..

but here is the solution. VHD drives. i didnt really think about it but all files i work with lies on a *.vhd image located on my d:\ drive. on system startup this image is loaded as my b:\ drive. where i keep backups and a lot of write and read data so that these sectors are left alone on my storing drive. now i just tried to edit a image lying on my d:\ drive and the files did not appear....

EDIT:

pooper. when i copy the folder of images that where on my VHD drive to d:\ root and try to edit them, the same problem accures. mabye its because of the compression or bitlocker.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded