M
Martin Kochanski
Whenever I run a 16-bit application on Windows XP, a file named
VDMxxx.TMP is created, where xxx is a hexadecimal number, and is never
deleted. The directory thus fills up with zero-length files-- by the
time there are a few hundred of them, performance begins to be affected.
There have been various responses on newsgroups but all of them seem to
miss the point one way or another. To clarify:
- The application does not create the VDMxxx.TMP file. I know it
doesn't, because some of the 16-bit apps are ones I wrote!
- Networking software is not creating the VDMxxx.TMP file. In fact,
there is no networking software installed (in particular, there is
nothing from Novell, which many newsgroup posts mentioned).
- I am running as administrator and so have delete access everywhere.
Thus "failure to delete" is not a possible cause.
- The same problem has been reported to me by people running Windows
2000.
Does anyone have an authoritative answer to the following questions?
- What is creating the VDMxxx.TMP files, and why?
- When, if ever, is it safe to delete a VDMxxx.TMP file?
- In particular, is it safe for an application to attempt to delete any
VDM files it sees, on the assumption that if one of these files is
essential to the stability of Windows then it will be locked and the
deletion will fail safely?
VDMxxx.TMP is created, where xxx is a hexadecimal number, and is never
deleted. The directory thus fills up with zero-length files-- by the
time there are a few hundred of them, performance begins to be affected.
There have been various responses on newsgroups but all of them seem to
miss the point one way or another. To clarify:
- The application does not create the VDMxxx.TMP file. I know it
doesn't, because some of the 16-bit apps are ones I wrote!
- Networking software is not creating the VDMxxx.TMP file. In fact,
there is no networking software installed (in particular, there is
nothing from Novell, which many newsgroup posts mentioned).
- I am running as administrator and so have delete access everywhere.
Thus "failure to delete" is not a possible cause.
- The same problem has been reported to me by people running Windows
2000.
Does anyone have an authoritative answer to the following questions?
- What is creating the VDMxxx.TMP files, and why?
- When, if ever, is it safe to delete a VDMxxx.TMP file?
- In particular, is it safe for an application to attempt to delete any
VDM files it sees, on the assumption that if one of these files is
essential to the stability of Windows then it will be locked and the
deletion will fail safely?