Andy said:
If I'm not mistaken, index.dat can be deleted; it's your IE cookie file.
You'll lose all your cookies for favorites sites and what not. Once you use
IE again, it will recreate it.
Correct me if I'm wrong, and I've been known to be.
You're right about the essential point. Safe to delete the MSIE index.dats;
and they will get automatically recreated. Recreated at a size significantly
smaller, and cleansed of their previous contents.
The one detail for correction is on the statement that "index.dat is your
IE cookie file. Your MSIE cookies exist as a whole bunch of files, and then
their is a master index.dat connected with them. As sort of a binary index
for them.. There are a number of MSIE index.dat files. As with cookies, there
are some for the MSIE history files. Add to the list, one special (trivial)
one in there, normally in a different path than norm, something to do with
history of locally accessed URLs. Then there is the one that likes to get
super huge - the one connected with the cache files.
When I run Index.dat Suite, I tell it the path to my MSIE temp files, and
it is very good about immediately identifying what is appropriate. In
contrast, Spider has a most serious problem.
I store my temp files on a specific path on D. but Spider lets me specify
only down to my /entire/ D drive. Then it wants to delete /every/ file on
that drive named index.dat. If were to let it proceed, that would break a
few of my programs. Those with happen to use a filename "indes.dat" for
their own stuff, nothing to do with MSIE. Spider has further shown a strange
inclination to want to delete some /additional/ independent files on my
system, ones not even having index.dat for their filenames..
I've found no such risks with Index.dat Suite. It's this one that is able
to hunt down on my system strictly the appropriate files. Even if I don't
take advantage of its feature where it will look in a specific path --
and I instead tell it to scour the entire D -- it does /not/ have Spider's
false positives. I assume the difference to do with Index.dat Suite having
the intelligence to take a peak at file headers, or something to that effect,
before coming up with its filelist.
Even after the file-list point in things, Index.dat Suite has more safety.
It lets you edit precisely what you want to delete, whether at the interface
stage, or even at the point when it will launch the planned .bat in notepad.
Spider, I had to do some emergency thing, forgot precisely, but think it was
to refuse to let it reboot and then to delete the startup registry entry it
wrote, in order to prevent its action of wrongful deletes.