K
Kris Hyde
Hi,
I'm using a fully patched version of Win 2000, but have have recently
been suffering from spuradic IE slowdown, during which IE uses up 100%
of CPU resources. Using filemon.exe I found that during this time tens
of thousands of attempted accesses were being made to the index.dat
files for each page loaded. Close inspection showed that two of the
index.dat files were 0k long (located in the ...local
settings\temporary index files\content.ie5 and, rather curiously, in
the ...local settings\temp\temporary index files\content.ie5 folders).
Thus, I'm guessing that they have got somehow corrupted and IE is
slowing down because of the effort of trying to repeatedly read them.
Using sofware available (IDSuite.exe - can recommend), I deleted all
index.dat files on my system. When logging back in, it should recreate
the index.dat files it needs with a starting size of 32k - yet sure
enough they were back again at 0k.
I'm guesing that to recreate the files to 32k each time there must be
a template or something somewhere on the system, which I'm guesing is
the part that is corrupted. Can anyone know where this is located, or
offer any other suggestions about what is going on??
Cheers,
Kris Hyde
I'm using a fully patched version of Win 2000, but have have recently
been suffering from spuradic IE slowdown, during which IE uses up 100%
of CPU resources. Using filemon.exe I found that during this time tens
of thousands of attempted accesses were being made to the index.dat
files for each page loaded. Close inspection showed that two of the
index.dat files were 0k long (located in the ...local
settings\temporary index files\content.ie5 and, rather curiously, in
the ...local settings\temp\temporary index files\content.ie5 folders).
Thus, I'm guessing that they have got somehow corrupted and IE is
slowing down because of the effort of trying to repeatedly read them.
Using sofware available (IDSuite.exe - can recommend), I deleted all
index.dat files on my system. When logging back in, it should recreate
the index.dat files it needs with a starting size of 32k - yet sure
enough they were back again at 0k.
I'm guesing that to recreate the files to 32k each time there must be
a template or something somewhere on the system, which I'm guesing is
the part that is corrupted. Can anyone know where this is located, or
offer any other suggestions about what is going on??
Cheers,
Kris Hyde