tmp files, WTF.

[CAMS]

Hi

I have Windows 98SE running realy well.
I was looking in C:Windows and found more than 400 tmp files that looked something like:
fffc29fb_{978c9c61-6fe9-11d5-a7bb-8b4be11db}.tmp with 0 size.

So I deleted them all, next time I rebooted 2 more where back, rebooted again and another 2 where there. These suckers are breading. I ran NAV 2001 (latest updates) and it came up clean.

Anybody know what this crap is about.

 

[Sundog]

<< These suckers are breading >>

\
LOL.

 

[julianf]

don't worry, it's registration database dumps... some program you install saved your whole database to rewrite, it's a backup... the installation just forgot to delete....

 

[thorin]

Start:Run:msconfig and see what you have running on startup.

Or delete the files and after you see the MS logo screen or just after you log on to the network press (and hold) shift so that your startup items don't load once Windows finishes loading go see if the tmp files are there again (then you'll know what's creating them).

You could also try this awesome utility HandleX / ProcessEx it allows you to view what files, reg keys, network prots, etc any process is using. You can also kill processes or change their priority, etc...

Thorin

 

[BraveSirRobbin]

You may want to write a line in your autoexec.bat that deletes these temp files on bootup

 

[MichaelD]

Wow. This is some really cool info to know. I always wondered what those 1,000+ &quot;0kb&quot; files were....I too, thought they were breeding! Good stuff here.

 

[MichaelD]

DP...sorry.

 

[afropick]

I can't remember exactly, but I think this problem has something to do with Microsoft Office 2000.

 

[CAMS]

<< You may want to write a line in your autoexec.bat that deletes these temp files on bootup >>



Sound good because I disable everything that was in startup in msconfig (except system tray) and they still get 2 more every reboot.

So how do I do that.

 

[Wizkid]

Add this to the bottom of your autoexec.bat:

del c:\windows\*.tmp /q

I'm not sure about that /q though, you may have to use /y (We run NT at work and I have no 95 machines to test this on).

 

[jaywallen]

Hi, CAMS.

The filname you listed started with &quot;fff&quot;, so I'm not absolutely sure about this. But I remember helping someone with a Win98SE machine. Her machine was collecting hundreds of files that began &quot;ffff&quot; (four of 'em, not three). I traced the proliferation of these files down to the Machine Debug Manager. If use IE's Tools | Internet Options dialog's Advanced tab to checkmark &quot;Disable script debugging&quot; and to uncheck the item called &quot;Display a notification about every script error&quot;, then use the Startup tab in MSCONFIG to uncheck Machine Debug Manager (I think that's what it was called there.), you should see those file cease to accumulate.

And I believe that afropick is correct in saying it may be related to Microsoft Office. For sure, every time this gal changes her Office installation she has to go back to repeat this change in the configuration, or the files will start accumulating again.

Again, since you specified three f's instead of four, I'm not absolutely sure this is the same phenomenon on your machine, but it's pretty suspicious. I'm not really familiar with Win9X, most of my experience with it being trying to help people figure out one weird problem or another. But I did just install it on a separate partition on my notebook so I can do some gaming without worrying about flubbing up my W2K partition! Works pretty well on the Inspiron. Who woulda thunk it?

Regards,
Jim

 

[afropick]

Cams,

I knew I remembered something about people having this problem with Microsoft Office 2000.

I found the workaround at the MS Knowledge Base: OFF2000: Files Whose Name Begins with &quot;fff&quot; Appear in Windows Folder

As jaywallen mentioned, it apparently has something to do with the Microsoft Script Editor, which installs a file called mdm.exe (Machine Debug Manager).

 

[jaywallen]

Thank you for posting that link, afropick. I guess I was misremembering the number of f's. Or maybe my ancient brain was stuttering!

 

[ukDave]

hehe! I just looked and i found over 250 of the biatches! I've never seen anything like it with Office 97, but recently upgraded to 2000, so that must be it. Well done guys for resolving the prob!

dave

 

[thorin]

Ok ok I have one too:

Does anyone know what these files are? The list grows and grows until I take time to delete them normally one or two are in use (I'm not sure what process). WinNT 4.0 SP 6 (build 1381).

c:\> c:
c:\> cd winnt
c:\winnt\> dir /b *.tmp
~DF10C.tmp
~DF12A.tmp
~DF147D.tmp
~DFCA66.tmp
~DFCADE.tmp
~DFCBB0.tmp
~DFCCE7.tmp
~DFCD9B.tmp
~DFCE45.tmp
~DFD13F.tmp
~DFDF5.tmp

Edit:
I was able to find out (using the utility I linked above) that the file is created by and in use by c:\winnt\system32\msdtc.exe (I love this utility!!!!!!!!!!!).

Thanks,
Thorin

 

[Nevo]

Thorin,

If one or two are in use, get HandleEx from www.sysinternals.com and find out which process has an open handle to the files.

That's your smoking gun!

Doh! I just re-read your post and see you've already done that. That's what I get for clicking 'reply' too quickly.

 

[CAMS]

<< Cams,

I knew I remembered something about people having this problem with Microsoft Office 2000.

I found the workaround at the MS Knowledge Base: OFF2000: Files Whose Name Begins with &quot;fff&quot; Appear in Windows Folder

As jaywallen mentioned, it apparently has something to do with the Microsoft Script Editor, which installs a file called mdm.exe (Machine Debug Manager). >>



And the winner is AFROPICK!!!

Thankyou.

 

[CAMS]

Wizkid.



<< Add this to the bottom of your autoexec.bat:

del c:\windows\*.tmp /q

I'm not sure about that /q though, you may have to use /y (We run NT at work and I have no 95 machines to test this on). >>



Thanks for that but I will try afropick's link first.