files help please

[zubzero]

Under C:\documentsand steetings\owner\Local settings\Temp
In that temp folder is a file called
VCLCFH ect and they are really big files.
Are they necessary to run windows xp home edition?
Are they safe to delete?
Thanks in advance.

 

[John John]

Temporary (Temp) files are usually safe to delete but as a precaution
you should reboot before you delete them.

John

 

[Ken Blake, MVP]

Temporary (Temp) files are usually safe to delete but as a precaution
you should reboot before you delete them.

Although doing as you suggest, and rebooting, doesn't hurt, it should be
noted that Windows won't let you delete any file that are open (in use). So
there's really no danger in deleting without rebooting.

There's one exception to this, however. If you are in the midst of an
installation that proceeds in two steps, with the second one running after a
reboot, be aware that the first step probably saved temp files that will
need to be there after rebooting. In that case, do *not* delete temp files
before rebooting and finishing the installation.

 

[DanS]

Although doing as you suggest, and rebooting, doesn't hurt, it should
be noted that Windows won't let you delete any file that are open (in
use). So there's really no danger in deleting without rebooting.

There's one exception to this, however. If you are in the midst of an
installation that proceeds in two steps, with the second one running
after a reboot, be aware that the first step probably saved temp files
that will need to be there after rebooting. In that case, do *not*
delete temp files before rebooting and finishing the installation.

Also, the Visual Studio 6 IDE uses temp files when programming Visual Basic
that are not locked. You have a project open that you have been working on
for several hours, DON'T close VB, delete all the temp files under Docs &
Settings, go back to VB, and you current session is hosed. Hopefully
everything was saved before the temp file wipe.

 

[Ken Blake, MVP]

Also, the Visual Studio 6 IDE uses temp files when programming Visual
Basic that are not locked. You have a project open that you have been
working on for several hours, DON'T close VB, delete all the temp
files under Docs & Settings, go back to VB, and you current session
is hosed. Hopefully everything was saved before the temp file wipe.

Thanks for the info. I didn't know that.

I know nothing about Visual Studio, so can you help me understand how it
gets around the normal Windows restriction that you can not delete *any*
open file?

 

[DanS]

DanS wrote:


Thanks for the info. I didn't know that.

I know nothing about Visual Studio, so can you help me understand how it
gets around the normal Windows restriction that you can not delete *any*
open file?

I'm not sure of the details, but the files must not actually be locked.

(Super short background) When programming VB in the IDE, you can run the
program you are writing thru the IDE, do debugging, step through code line
by line, etc., without having to compiling an exe. Just press F5.

I ascertain that in the course of a programming session, VB writes temp
files as your running your code in the IDE, but their only open if you're
actually running the code, then it closes them.

Regards,

DanS

 

[zubzero]

Hi,
I have removed those files and so far no trouble happened as of
yet. I want to say " Thank you " to all of those who helped and have a
great Christmas!

 

[Ken Blake, MVP]

I'm not sure of the details, but the files must not actually be
locked.

(Super short background) When programming VB in the IDE, you can run
the program you are writing thru the IDE, do debugging, step through
code line by line, etc., without having to compiling an exe. Just
press F5.

I ascertain that in the course of a programming session, VB writes
temp files as your running your code in the IDE, but their only open
if you're actually running the code, then it closes them.

Thanks.