I used Eraser on two of my laptops to erase or overwrite unused disc space.
Now I am getting the same error on both computers. Everytime I boot, Windows
is telling me that the computer has just recovered from a major error and
that the BIOS does not match the processor inside of the computer. Then
after reporting the error I am taken directly to Microsoft's Processor and
BIOS ID Site. None of this ever occured prior to using Eraser and started
IMMEDIATLY after running Eraser, on two different computers. Therefore I can
only conclude eraser is the cause for these errors. Anyone else experience
this when using Eraser?

Jeff wrote:
> I used Eraser on two of my laptops to erase or overwrite unused disc space.
> Now I am getting the same error on both computers. Everytime I boot, Windows
> is telling me that the computer has just recovered from a major error and
> that the BIOS does not match the processor inside of the computer. Then
> after reporting the error I am taken directly to Microsoft's Processor and
> BIOS ID Site. None of this ever occured prior to using Eraser and started
> IMMEDIATLY after running Eraser, on two different computers. Therefore I can
> only conclude eraser is the cause for these errors. Anyone else experience
> this when using Eraser?
>
>

If you haven't done so already, I suggest posting this in the Eraser
Support Forum. I did a quick search there to see if there were similar
problems reported, and there was nothing comparable.

http://www.cipherserver.com/phpbb2/v...9f4e5c2e76e51d

What Windows OS are you using? Have you tried running any system disk
utilities such as chkdsk or scandisk to identify (and fix) possible
errors on the disk?

Jeff wrote:
> I used Eraser on two of my laptops to erase or overwrite unused disc space.
> Now I am getting the same error on both computers. Everytime I boot, Windows
> is telling me that the computer has just recovered from a major error and
> that the BIOS does not match the processor inside of the computer. Then
> after reporting the error I am taken directly to Microsoft's Processor and
> BIOS ID Site. None of this ever occured prior to using Eraser and started
> IMMEDIATLY after running Eraser, on two different computers. Therefore I can
> only conclude eraser is the cause for these errors. Anyone else experience
> this when using Eraser?

No problems whatsoever for 2+ years, using Eraser regularly with WinXP
Home.

"DaVinci" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Jeff wrote:
> > I used Eraser on two of my laptops to erase or overwrite unused disc
space.
> > Now I am getting the same error on both computers. Everytime I boot,
Windows
> > is telling me that the computer has just recovered from a major error
and
> > that the BIOS does not match the processor inside of the computer. Then
> > after reporting the error I am taken directly to Microsoft's Processor
and
> > BIOS ID Site. None of this ever occured prior to using Eraser and
started
> > IMMEDIATLY after running Eraser, on two different computers. Therefore I
can
> > only conclude eraser is the cause for these errors. Anyone else
experience
> > this when using Eraser?
> >
> >
>
> If you haven't done so already, I suggest posting this in the Eraser
> Support Forum. I did a quick search there to see if there were similar
> problems reported, and there was nothing comparable.
>
>
http://www.cipherserver.com/phpbb2/v...9f4e5c2e76e51d
>
> What Windows OS are you using? Have you tried running any system disk
> utilities such as chkdsk or scandisk to identify (and fix) possible
> errors on the disk?

Running Windows XP Pro on one and Home on the other. Ran all the disc
utilites and nothing showed up. I dont think its a fluke, there were
definitly some changes made to the system. Will post it to the forum. Thanks

(E-Mail Removed) wrote in
<(E-Mail Removed)>, on 12/08/2005,
H. Clarisse

> No problems whatsoever for 2+ years, using Eraser regularly with WinXP
> Home.

Same here, on W2000pro, never a problem and I use Eraser every day :-)

--
Alain (Albé) Reply-to is valid (only 4 days !)
http://home.tiscali.be/a.beguin
MesNews Translators Team (Dutch) http://www.mesnews.org/Plugins.htm
http://www.mesnews.net/

On Fri, 12 Aug 2005 15:00:00 GMT, Jeff wrote:

> I used Eraser on two of my laptops to erase or overwrite unused disc space.
> Now I am getting the same error on both computers. Everytime I boot, Windows
> is telling me that the computer has just recovered from a major error and
> that the BIOS does not match the processor inside of the computer. Then
> after reporting the error I am taken directly to Microsoft's Processor and
> BIOS ID Site. None of this ever occured prior to using Eraser and started
> IMMEDIATLY after running Eraser, on two different computers. Therefore I can
> only conclude eraser is the cause for these errors. Anyone else experience
> this when using Eraser?



I used to use Eraser on an old laptop I had which ran W98. No problems at
all. Then I got this fine HP Pavilion zv5000 with Windows XP and ran
Eraser once and it completely wrecked things. . .I had to run the recovery
disk to get things back. Sorry, no more Eraser for me.


--
Martin R. Howell
"Photographs From the Universe of Amateur Astronomy"
http://members.isp.com/universeofama...nomy%40isp.com

"Martin R. Howell" <(E-Mail Removed)> wrote in message
news:1xg99v5d59iw7$.kelbsaoab0t1$.(E-Mail Removed)...
> On Fri, 12 Aug 2005 15:00:00 GMT, Jeff wrote:
>
> > I used Eraser on two of my laptops to erase or overwrite unused disc
space.
> > Now I am getting the same error on both computers. Everytime I boot,
Windows
> > is telling me that the computer has just recovered from a major error
and
> > that the BIOS does not match the processor inside of the computer. Then
> > after reporting the error I am taken directly to Microsoft's Processor
and
> > BIOS ID Site. None of this ever occured prior to using Eraser and
started
> > IMMEDIATLY after running Eraser, on two different computers. Therefore I
can
> > only conclude eraser is the cause for these errors. Anyone else
experience
> > this when using Eraser?
>
>
>
> I used to use Eraser on an old laptop I had which ran W98. No problems at
> all. Then I got this fine HP Pavilion zv5000 with Windows XP and ran
> Eraser once and it completely wrecked things. . .I had to run the recovery
> disk to get things back. Sorry, no more Eraser for me.
>
>

Yes I dont want to have to use that recovery disk.

>On Fri, 12 Aug 2005 20:18:21 -0700, "Martin R. Howell" wrote:
>
>>On Fri, 12 Aug 2005 15:00:00 GMT, Jeff wrote:
>>
>> I used Eraser on two of my laptops to erase or overwrite unused disc space.
>> Now I am getting the same error on both computers. Everytime I boot, Windows
>> is telling me that the computer has just recovered from a major error and
>> that the BIOS does not match the processor inside of the computer. Then
>> after reporting the error I am taken directly to Microsoft's Processor and
>> BIOS ID Site. None of this ever occured prior to using Eraser and started
>> IMMEDIATLY after running Eraser, on two different computers. Therefore I can
>> only conclude eraser is the cause for these errors. Anyone else experience
>> this when using Eraser?
>>
>I used to use Eraser on an old laptop I had which ran W98. No problems at
>all. Then I got this fine HP Pavilion zv5000 with Windows XP and ran
>Eraser once and it completely wrecked things. . .I had to run the recovery
>disk to get things back. Sorry, no more Eraser for me.
>
Read the user reviews at:

http://www.download.com/Eraser/3640-...-10231813.html

A few more people experienced problems with Eraser.

Jeff wrote:
> I used Eraser on two of my laptops to erase or overwrite unused disc space.
> Now I am getting the same error on both computers. Everytime I boot, Windows
> is telling me that the computer has just recovered from a major error and
> that the BIOS does not match the processor inside of the computer. Then
> after reporting the error I am taken directly to Microsoft's Processor and
> BIOS ID Site. None of this ever occured prior to using Eraser and started
> IMMEDIATLY after running Eraser, on two different computers. Therefore I can
> only conclude eraser is the cause for these errors. Anyone else experience
> this when using Eraser?
>
>
I used it on a computer with Windows XP Home SP2 installed, last year.
It completely screwed up my installation of GO BACK and wiped out all
the restore points it had created.

I also used it recently on my new computer (same OS, without GO BACK
installed) and had no problems.

BTW have you tried using System Restore to roll back your computer to a
point before you used Eraser?

--
"I think computer viruses should count as life. I think it says
something about human nature that the only form of life we have created
so far is purely destructive. We've created life in our own image."

-- Stephen Hawking --

On Fri, 12 Aug 2005 15:00:00 GMT, "Jeff" <(E-Mail Removed)>
wrote:

>I used Eraser on two of my laptops to erase or overwrite unused disc space.
>Now I am getting the same error on both computers. Everytime I boot, Windows
>is telling me that the computer has just recovered from a major error and
>that the BIOS does not match the processor inside of the computer. Then
>after reporting the error I am taken directly to Microsoft's Processor and
>BIOS ID Site. None of this ever occured prior to using Eraser and started
>IMMEDIATLY after running Eraser, on two different computers. Therefore I can
>only conclude eraser is the cause for these errors. Anyone else experience
>this when using Eraser?
>

hiya,Jeff
I have used Eraser on an XP box for a good while and never had any
probs. I'm still using ver 5.6...liked it so well, I have never
upgraded.
Did you have the laptops defragged before overwriting the unused
space ?
Did you do a chkdisk before overwriting ?
What version of Eraser are you using ? Did you check for a bug report
on authors site ?

Using Eraser is a very secure way to delete files. I have checked
files that were deleted by Eraser w/ Directory Snoop <payware>
All file names are scrambled, file size is zeroed out and all dates
for*modified*,*accessed* and *created* are always bogused to
*1980-01-01 and w/ *time* as *00:00:00.00*
I have not used a shareware program that hid traces as well.
Hopefully you had fresh images of your laptops.
/bLB