%1 %2 and Memory Problems

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Rikki - 30 Sep 2004 14:57 GMT

I have ME and 512RAM memory. I've tried Mike's cure for
the %1 %1 problem when rebooting and I've saved the
instructions. I've run his instructions countless times
and they always do the job, except, it always goes back to
the same problem. It's getting so that I am hating System
Restore. Who ever uses it, anyway? The Wininit.exe file
keeps getting corrupted by something that I've never been
able to figure out. Some file, I'm told but how are you
supposed to know which one? I have a life and don't want
to spend it in front of this beast constantly fixing
something. I went to Newbie.org and they took a different
approach. They suggested deleting the Wininit.exe and
Wininit.ini (if you have it) then extract a new
wininit.exe file from the Me installation disk. It seemed
to work a little better but still doesn't cure it. They
suggested, when updating a program, to make sure nothing
else is running in the background. What is your oppinion?

They also said that for the memory problem to look at
C:\_RESTORE\TEMP and C:\_RESTORE\ARCHIVE folders and
delete what's inside. Is that OK to do, you think?

Reply to this Message

Muhammad-Ali - 30 Sep 2004 15:17 GMT

> I have ME and 512RAM memory. I've tried Mike's cure for
> the %1 %1 problem when rebooting and I've saved the
[quoted text clipped - 17 lines]
> C:\_RESTORE\TEMP and C:\_RESTORE\ARCHIVE folders and
> delete what's inside. Is that OK to do, you think?

I think that you should only empty C:\_restore\temp. You can also rename it.
Did you tried to uninstall or reinstall the last installed program first
(press F8 or Ctrl a lot of times to go to safe mode when your PC is
starting). If the problem still occurs, reinstall Me. If you want a clean
install, rename your Win folder first.

Reply to this Message

Mike M - 30 Sep 2004 15:43 GMT

> I think that you should only empty C:\_restore\temp. You can also
> rename it. Did you tried to uninstall or reinstall the last installed
> program first (press F8 or Ctrl a lot of times to go to safe mode
> when your PC is starting). If the problem still occurs, reinstall Me.
> If you want a clean install, rename your Win folder first.

No.

If you empty just C:\_RESTORE\TEMP you destroy the integrity of the
archive so you might as well blow away the lot.

As for reinstalling Win Me and your suggested method of doing so neither
is the solution.

Signature

Mike Maltby MS-MVP [2001-2004]
mcmaltby@hotmail.com

Reply to this Message

Mike M - 30 Sep 2004 15:18 GMT

Who uses system restore? Many people, myself included, to fix problems
created in the last few minutes, hours or perhaps days,such as when
testing the installation of a new driver. Personally I'd never use a
system now that didn't include such functionality. May I suggest you
learn about it and see for yourself how useful it can be. I image my
system volumes regularly to both backup files on remote hard disks and
also periodically to a DVD but only weekly whereas system restore enables
me to roll my system back sometimes just a few minutes.

Turning to your %1 %2 error. Either you are not removing the C:\)RESTORE
folder that is the root cause of the problem due to C:\_RESTORE\TEMP being
at the file limit for a FAT32 system (64K files) or you are running
Symantec malware and allowing that to repeatedly destroy your system.
However I've never heard of instances where Symantec products cause this
particular problem with the regularity that you seem to be seeing.

If however you think the problem is due to wininit.exe being corrupted,
although I see no evidence that it this is what is causing you your
problems, this is most likely to be the result of viral activity. Have you
checked your system?

Whoever wrote the article you saw at newbie.org seems to be clueless as to
the underlying cause of this problem. I'm surprised that they didn't also
suggest you sacrifice a nine-tailed cat before switching on your PC.

Signature

Mike Maltby MS-MVP [2001-2004]
mcmaltby@hotmail.com

Reply to this Message