Now I Can't Load Anything @ ALL

-----Original Message-----
This is a continuation of an earlier post, (kinda
sorta)
I've gone from the first post problem, to the present
post problem. Here's part 1------------

I have an XP Home Presario that does not start at all.
The
only thing that pops up is Master Boot Record Error
Press a key When I press any key, I get PRESS A KEY
TO
REBOOT

The last thing done to it before this happened was
attempting to use system restore to go back to a date
within the month of Jan 2004. (Don't ask me, I didn't do
it.)
I have tried using F8 to get to 'Last Known Good
Configuration' but no go. The only thing it does is go
thru the cycle of trying to reboot without anything
showing up on the screen. As soon as I stop hitting F8,
it
goes to the same screen as I forementioned. I've tried
hitting other keys as well to no avail. Is this the
correct way of trying to get this thing up and running
again or does this have something to do with Boot.ini
file
and therefore I should be trying recovery console.

Present problem------------ The pc's owner said to
just
install another OS. So I bypassed the recovery console
option and just attempted to load XP Pro on it. I got as
far as trying to setup a third partition on this 80 gig
HD
and out of nowhere I got an error message that took up
the
whole screen. Now, I'm not able to load anything because
it's saying that it's unable to format the partition.
The
disk may be damaged. The two partitions that I did get
done
shows as 'unformatted or damaged'

I understand that this happens, but what confuses me is
that when I installed another HD and tried to load that
one, the setup cycle "loops" after the restarting part
of
it. Besides booting off of the HD, it goes back to
booting
off of the cd without any prompting. I took that one out
and tried another, thinking that 'maybe' it's hardware
related. Same results. Looping -It even happened when
I
tried Win2K Pro. (Just 2 C what would happen)

Now, the original reason that the owner had tried
system restore was because it was running real slow and
the application log was filled up with warnings and
errors.

Event Type: Warning
Event Source: EventSystem
Event Category: (54)
Event ID: 4353

Event Type: Warning
Event Source: EventSystem
Event Category: (52)
Event ID: 4354

Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000

My question is - Could all of this mess have been caused
by a virus and now it's in the memory and/or motherboard
someway??
If this sounds feasible, what needs to be done to
correct
this crap?

Thank You For Any And All Constructive And Useable
Advice!!
The Rookie/Wayne B.
.
I have a Dos 6.22 I use to fdisk when ever I have one of
those hard to start By CD installs. I first move Floppy
to #1 in boot order in BIOS, do the Dos then put CD-rom
#1 in boot order and that has worked for me . Now do you
have a any Dos?

wrote in message
...

-----Original Message-----
This is a continuation of an earlier post, (kinda
sorta)
I've gone from the first post problem, to the present
post problem. Here's part 1------------

I have an XP Home Presario that does not start at all.
The
only thing that pops up is Master Boot Record Error
Press a key When I press any key, I get PRESS A KEY
TO
REBOOT

The last thing done to it before this happened was
attempting to use system restore to go back to a date
within the month of Jan 2004. (Don't ask me, I didn't do
it.)
I have tried using F8 to get to 'Last Known Good
Configuration' but no go. The only thing it does is go
thru the cycle of trying to reboot without anything
showing up on the screen. As soon as I stop hitting F8,
it
goes to the same screen as I forementioned. I've tried
hitting other keys as well to no avail. Is this the
correct way of trying to get this thing up and running
again or does this have something to do with Boot.ini
file
and therefore I should be trying recovery console.

Present problem------------ The pc's owner said to
just
install another OS. So I bypassed the recovery console
option and just attempted to load XP Pro on it. I got as
far as trying to setup a third partition on this 80 gig
HD
and out of nowhere I got an error message that took up
the
whole screen. Now, I'm not able to load anything because
it's saying that it's unable to format the partition.
The
disk may be damaged. The two partitions that I did get
done
shows as 'unformatted or damaged'

I understand that this happens, but what confuses me is
that when I installed another HD and tried to load that
one, the setup cycle "loops" after the restarting part
of
it. Besides booting off of the HD, it goes back to
booting
off of the cd without any prompting. I took that one out
and tried another, thinking that 'maybe' it's hardware
related. Same results. Looping -It even happened when
I
tried Win2K Pro. (Just 2 C what would happen)

Now, the original reason that the owner had tried
system restore was because it was running real slow and
the application log was filled up with warnings and
errors.

Event Type: Warning
Event Source: EventSystem
Event Category: (54)
Event ID: 4353

Event Type: Warning
Event Source: EventSystem
Event Category: (52)
Event ID: 4354

Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000

My question is - Could all of this mess have been caused
by a virus and now it's in the memory and/or motherboard
someway??
If this sounds feasible, what needs to be done to
correct
this crap?

Thank You For Any And All Constructive And Useable
Advice!!
The Rookie/Wayne B.
.
I have a Dos 6.22 I use to fdisk when ever I have one of
those hard to start By CD installs. I first move Floppy
to #1 in boot order in BIOS, do the Dos then put CD-rom
#1 in boot order and that has worked for me . Now do you
have a any Dos?

The next things I'd suspect would be the memory , the hard drive, or the
hard drive controller. Try the memory one stick at a time to see if it works
any better. Try a different, empty hard drive and see if it malfunctions.