HELP

  • Thread starter Thread starter Joe D
  • Start date Start date
J

Joe D

I'm trying to fix a computer that is hosed up really bad. It's running
WindowsXP Home. I read about mwav.exe and wget.exe in a previous post
and ran those in safe mode. I tried to go back in and do some more
clean up with AdAware and Spybot. It appeared to be cleaning the
system but then I started getting all kinds of memory errors on start
up. Now I can only work in Safe Mode. I downloaded F-Prot in Safe
Mode. Can I insall it in Safe Mode? Any other suggestions? Thanks
 
From: <Joe D>

| I'm trying to fix a computer that is hosed up really bad. It's running
| WindowsXP Home. I read about mwav.exe and wget.exe in a previous post
| and ran those in safe mode. I tried to go back in and do some more
| clean up with AdAware and Spybot. It appeared to be cleaning the
| system but then I started getting all kinds of memory errors on start
| up. Now I can only work in Safe Mode. I downloaded F-Prot in Safe
| Mode. Can I insall it in Safe Mode? Any other suggestions? Thanks

You said... "...but then I started getting all kinds of memory errors on start up."

Please state the EXACT error messages you got.
 
From: <Joe D>

| I'm trying to fix a computer that is hosed up really bad. It's running
| WindowsXP Home. I read about mwav.exe and wget.exe in a previous post
| and ran those in safe mode. I tried to go back in and do some more
| clean up with AdAware and Spybot. It appeared to be cleaning the
| system but then I started getting all kinds of memory errors on start
| up. Now I can only work in Safe Mode. I downloaded F-Prot in Safe
| Mode. Can I insall it in Safe Mode? Any other suggestions? Thanks

You said... "...but then I started getting all kinds of memory errors on start up."

Please state the EXACT error messages you got.

Here's one of them:

The instruction at "0x77e7650d" referenced memory at "0xfc85c6ff". The
memory at "0xfc85c6ff". The memory could not be "read".
Click OK to terminate the program.
 
From: <Joe D>


|
| Here's one of them:
|
| The instruction at "0x77e7650d" referenced memory at "0xfc85c6ff". The
| memory at "0xfc85c6ff". The memory could not be "read".
| Click OK to terminate the program.

From Safe Mode run System Restore and restore the system back to a point prior to the error
messages and then start the cleaning process again.

Take note and be careful of removing any; OS system or OS kernel files that may be deleted.
 
From: <Joe D>


|
| Here's one of them:
|
| The instruction at "0x77e7650d" referenced memory at "0xfc85c6ff". The
| memory at "0xfc85c6ff". The memory could not be "read".
| Click OK to terminate the program.

From Safe Mode run System Restore and restore the system back to a point prior to the error
messages and then start the cleaning process again.

Take note and be careful of removing any; OS system or OS kernel files that may be deleted.

I wonder if Spybot's Immunize feature is adding to his misery. Maybe
removing Spybot from Startup items would help in getting back into
Normal mode. Just a hunch based on a bad experience with Spybot's
"realtime" protection ... something I'd never use.

Art

http://home.epix.net/~artnpeg
 
Art said:
I wonder if Spybot's Immunize feature is adding to his misery. Maybe
removing Spybot from Startup items would help in getting back into
Normal mode. Just a hunch based on a bad experience with Spybot's
"realtime" protection ... something I'd never use.

I believe that would be Tea Timer, Art. Immunize in itself is not a Startup
item, nor iirc is SD Helper, which is accessed from the Immunize page (it's
a BHO).

However, I've uninstalled Spybot because in an apparent attempt to alleviate
US mirror overload, UK users are denied access while, less understandably,
other mirrors get updated late.
iow we're effectively being moved to one side so's American's can go first.
Patric Kolla is therefore cordially invited to bite my shiny metal ass.

Shane
 
I believe that would be Tea Timer, Art. Immunize in itself is not a Startup
item, nor iirc is SD Helper, which is accessed from the Immunize page (it's
a BHO).

You're probably right. As I said before in a post to you, I don't know
which of the optional functions I was trying screwed up my Win 2K Pro.
All I know is that they're forever disabled on my PCs since I'm not
interested in them anyway.

Art

http://home.epix.net/~artnpeg
 
Art said:
You're probably right. As I said before in a post to you, I don't know
which of the optional functions I was trying screwed up my Win 2K Pro.
All I know is that they're forever disabled on my PCs since I'm not
interested in them anyway.

I get the impression Tea Timer has caused problems before. But I've never
used it.

Shane
 
Art said:
may be deleted.

I wonder if Spybot's Immunize feature is adding to his misery. Maybe
removing Spybot from Startup items would help in getting back into
Normal mode. Just a hunch based on a bad experience with Spybot's
"realtime" protection ... something I'd never use.

Art

If you uninstall SpyBot, I believe there are certain things you have to undo
before uninstalling it.
I believe one of them is the immunize and there is another one, can't think of
it now, but I believe it is in the Help section of SpyBot.
 
David said:
From: "Shane" <[email protected]>

| I get the impression Tea Timer has caused problems before. But I've never
| used it.

Ditto. I don't use it either.

i installed it some time ago, just because (it was part of spybot, why
not?)...

near as i can tell the only thing it does on my system is monitor
registry changes for certain key registry hives and ask whether or not i
want to allow those changes to take place... i've not had any real
problem with it...
 
Back
Top