wininit.ini file

I was having a problem running system restore and tracked it down to a
winit.ini file. I renamed the file, but it kept reappearing on bootup. I
have also tried scanreg /fix but it still appears each time.

I have opened the file and it says each time.

[Rename]
NUL=C:\WINDOWS\TEMPOR~1\CONTENT.IE5\INDEX.DAT
NUL=C:\WINDOWS\COOKIES\INDEX.DAT

I thought it might be something to do with Avant Browser which I had
recently installed, but having uninstalled it the problem still appears.

Short of reistalling windowsME, or renaming the file every time I wish to
use system restore, could anyone advise me of a possible solution please?

TIA

Renamed it to what?

If wininit.ini exists at startup, it is used and renamed wininit,bak
so it won't be used again.
Why not delete it?

....Alan

--
Alan Edwards, MS MVP W95/98 Systems
http://dts-l.org/index.html



In microsoft.public.windowsme.general, "Tritoneur"
wrote:

I was having a problem running system restore and tracked it down to a
winit.ini file. I renamed the file, but it kept reappearing on bootup. I
have also tried scanreg /fix but it still appears each time.

I have opened the file and it says each time.

[Rename]
NUL=C:\WINDOWS\TEMPOR~1\CONTENT.IE5\INDEX.DAT
NUL=C:\WINDOWS\COOKIES\INDEX.DAT

I thought it might be something to do with Avant Browser which I had
recently installed, but having uninstalled it the problem still appears.

Short of reistalling windowsME, or renaming the file every time I wish to
use system restore, could anyone advise me of a possible solution please?

TIA

Alan Edwards wrote:
Renamed it to what?

If wininit.ini exists at startup, it is used and renamed wininit,bak
so it won't be used again.
Why not delete it?

...Alan

Hi Alan,

Thanks for replying. I renamed the extension .xxx as per Microsoft Knowledge
Base Article 274092. I tried deleting it also but it kept reappearing on
boot-up, so it seems it wasn't being renamed to .bak as it should have been.

I have been using CCleaner on startup to clean up various files on boot-up
including index.dat files. I have unchecked that item (only because
index.dat appears in the wininit.ini file - I am not particularly
technically knowledgable!)

I have also run scanreg /fix and rebooted a few times and the problem seems
to have been fixed for now, but if you have any further observations on it,
I would be pleased to know!

Tritoneur

There's your cause - those two files are protected system files, and cannot
be deleted while the OS is running.
Your cleaner is obviously creating a new wininit.ini file at boot time to
get around this, allowing the deletion of the files at the next boot.
I'd recommend ditching the cleaner - or only switching it on when you
actually NEED to delete the index files (which is never! - unless perhaps
you have something to hide)

--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

"Tritoneur" wrote in message
...
Alan Edwards wrote:
Renamed it to what?

If wininit.ini exists at startup, it is used and renamed wininit,bak
so it won't be used again.
Why not delete it?

...Alan

Hi Alan,

Thanks for replying. I renamed the extension .xxx as per Microsoft
Knowledge
Base Article 274092. I tried deleting it also but it kept reappearing on
boot-up, so it seems it wasn't being renamed to .bak as it should have
been.

I have been using CCleaner on startup to clean up various files on boot-up
including index.dat files. I have unchecked that item (only because
index.dat appears in the wininit.ini file - I am not particularly
technically knowledgable!)

I have also run scanreg /fix and rebooted a few times and the problem
seems
to have been fixed for now, but if you have any further observations on
it,
I would be pleased to know!

Tritoneur

Why not post the contents here if it keeps re-appearing?
It usually reappears only if it is incorrect but renaming it correctly
should take care of that.

Sorry, but I have no idea what CCleaner is, nor what the connection is
with index.dat and I can only suggest you supply more information as
any of the idex.dat files may be difficult to clean or remove if done
incorrectly.

....Alan

--
Alan Edwards, MS MVP W95/98 Systems
http://dts-l.org/index.html


In microsoft.public.windowsme.general, "Tritoneur"
wrote:

Alan Edwards wrote:
Renamed it to what?

If wininit.ini exists at startup, it is used and renamed wininit,bak
so it won't be used again.
Why not delete it?

...Alan

Hi Alan,

Thanks for replying. I renamed the extension .xxx as per Microsoft Knowledge
Base Article 274092. I tried deleting it also but it kept reappearing on
boot-up, so it seems it wasn't being renamed to .bak as it should have been.

I have been using CCleaner on startup to clean up various files on boot-up
including index.dat files. I have unchecked that item (only because
index.dat appears in the wininit.ini file - I am not particularly
technically knowledgable!)

I have also run scanreg /fix and rebooted a few times and the problem seems
to have been fixed for now, but if you have any further observations on it,
I would be pleased to know!

Tritoneur

Thanks Noel and Alan for your information and advice. Sorted :-)

Noel Paton wrote:
There's your cause - those two files are protected system files, and
cannot be deleted while the OS is running.
Your cleaner is obviously creating a new wininit.ini file at boot
time to get around this, allowing the deletion of the files at the
next boot.
I'd recommend ditching the cleaner - or only switching it on when you
actually NEED to delete the index files (which is never! - unless
perhaps you have something to hide)


"Tritoneur" wrote in message
...
Alan Edwards wrote:
Renamed it to what?

If wininit.ini exists at startup, it is used and renamed wininit,bak
so it won't be used again.
Why not delete it?

...Alan

Hi Alan,

Thanks for replying. I renamed the extension .xxx as per Microsoft
Knowledge
Base Article 274092. I tried deleting it also but it kept
reappearing on boot-up, so it seems it wasn't being renamed to .bak
as it should have been.

I have been using CCleaner on startup to clean up various files on
boot-up including index.dat files. I have unchecked that item (only
because index.dat appears in the wininit.ini file - I am not
particularly technically knowledgable!)

I have also run scanreg /fix and rebooted a few times and the problem
seems
to have been fixed for now, but if you have any further observations
on it,
I would be pleased to know!

Tritoneur

Good Luck!

(sorry to butt into your thread, Alan)

--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

"Tritoneur" wrote in message
...
Thanks Noel and Alan for your information and advice. Sorted :-)

Noel Paton wrote:
There's your cause - those two files are protected system files, and
cannot be deleted while the OS is running.
Your cleaner is obviously creating a new wininit.ini file at boot
time to get around this, allowing the deletion of the files at the
next boot.
I'd recommend ditching the cleaner - or only switching it on when you
actually NEED to delete the index files (which is never! - unless
perhaps you have something to hide)


"Tritoneur" wrote in message
...
Alan Edwards wrote:
Renamed it to what?

If wininit.ini exists at startup, it is used and renamed wininit,bak
so it won't be used again.
Why not delete it?

...Alan

Hi Alan,

Thanks for replying. I renamed the extension .xxx as per Microsoft
Knowledge
Base Article 274092. I tried deleting it also but it kept
reappearing on boot-up, so it seems it wasn't being renamed to .bak
as it should have been.

I have been using CCleaner on startup to clean up various files on
boot-up including index.dat files. I have unchecked that item (only
because index.dat appears in the wininit.ini file - I am not
particularly technically knowledgable!)

I have also run scanreg /fix and rebooted a few times and the problem
seems
to have been fixed for now, but if you have any further observations
on it,
I would be pleased to know!

Tritoneur

CCLeaner
Crap Cleaner
at
http://www.ccleaner.com/



"Alan Edwards" wrote in message
...
Why not post the contents here if it keeps re-appearing?
It usually reappears only if it is incorrect but renaming it correctly
should take care of that.

Sorry, but I have no idea what CCleaner is, nor what the connection is
with index.dat and I can only suggest you supply more information as
any of the idex.dat files may be difficult to clean or remove if done
incorrectly.

....Alan

--
Alan Edwards, MS MVP W95/98 Systems
http://dts-l.org/index.html


In microsoft.public.windowsme.general, "Tritoneur"
wrote:

Alan Edwards wrote:
Renamed it to what?

If wininit.ini exists at startup, it is used and renamed wininit,bak
so it won't be used again.
Why not delete it?

...Alan

Hi Alan,

Thanks for replying. I renamed the extension .xxx as per Microsoft
Knowledge
Base Article 274092. I tried deleting it also but it kept reappearing on
boot-up, so it seems it wasn't being renamed to .bak as it should have
been.

I have been using CCleaner on startup to clean up various files on boot-up
including index.dat files. I have unchecked that item (only because
index.dat appears in the wininit.ini file - I am not particularly
technically knowledgable!)

I have also run scanreg /fix and rebooted a few times and the problem seems
to have been fixed for now, but if you have any further observations on it,
I would be pleased to know!

Tritoneur

Thanks. What an unfortunate choice of a name. (IMHO)
I think I may live without it.

....Alan

--
Alan Edwards, MS MVP W95/98 Systems
http://dts-l.org/index.html

In microsoft.public.windowsme.general, "AAH"
wrote:

CCLeaner
Crap Cleaner
at
http://www.ccleaner.com/



"Alan Edwards" wrote in message
.. .
Why not post the contents here if it keeps re-appearing?
It usually reappears only if it is incorrect but renaming it correctly
should take care of that.

Sorry, but I have no idea what CCleaner is, nor what the connection is
with index.dat and I can only suggest you supply more information as
any of the idex.dat files may be difficult to clean or remove if done
incorrectly.

...Alan

Better to butt into his thread than thread into.......oh, never mind!


Shane


"Noel Paton" wrote in message
...
Good Luck!

(sorry to butt into your thread, Alan)

--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

"Tritoneur" wrote in message
...
Thanks Noel and Alan for your information and advice. Sorted :-)

Noel Paton wrote:
There's your cause - those two files are protected system files, and
cannot be deleted while the OS is running.
Your cleaner is obviously creating a new wininit.ini file at boot
time to get around this, allowing the deletion of the files at the
next boot.
I'd recommend ditching the cleaner - or only switching it on when you
actually NEED to delete the index files (which is never! - unless
perhaps you have something to hide)


"Tritoneur" wrote in message
...
Alan Edwards wrote:
Renamed it to what?

If wininit.ini exists at startup, it is used and renamed wininit,bak
so it won't be used again.
Why not delete it?

...Alan

Hi Alan,

Thanks for replying. I renamed the extension .xxx as per Microsoft
Knowledge
Base Article 274092. I tried deleting it also but it kept
reappearing on boot-up, so it seems it wasn't being renamed to .bak
as it should have been.

I have been using CCleaner on startup to clean up various files on
boot-up including index.dat files. I have unchecked that item (only
because index.dat appears in the wininit.ini file - I am not
particularly technically knowledgable!)

I have also run scanreg /fix and rebooted a few times and the problem
seems
to have been fixed for now, but if you have any further observations
on it,
I would be pleased to know!

Tritoneur