Windows XP Installation Difficulties

[Gregg]

Hi,

I am in the process of trying to help a friend out with
his PC. He has a HP Pavilion 7955 that was given to him
(second hand)by a friend. It had Windows XP Home Edition
as the operating system and unfortunately the original cd
for the PC was not included in the "handing over".

He started experiencing a problem where the pc would not
boot up citing "Windows XP could not start because the
following file is missing or corrupt: \WINDOWS\SYSTEM32
\CONFIG\SYSTEM. I located the solution throught the
Microsoft KnowledgeBase and followed all the steps
presented. It did not seem to solve the issue.

I then created the six (6) start up disks (for Windows XP
Professional SP1) and have now tried a complete new
install for XP Professional (as opposed to the Home
Edition version). I deleted the existing partitions (which
from hindsight may have been a foolish move) and now I am
having extreme difficulty.

When I get to the area in Windows XP Profesional Setup
where it is to show the list of existing partitions and
unpartitioned space on the computer...all I see is this:

39078 MB Disk 0 at Id 0 on bus 0 on atapi
(Setup cannot access this disk.)

This is not highlighted at all (contrary to normal
appearance)
No matter what I try...whether to setup Windows XP (by
pressing ENTER) or trying to create a partition in the
unpartitioned space or to even delete the selected
partition (which is not available). I receive the same
results.

A Stop Error Message screen saying: A problem has been
detected and windows has been shut down to prevent damage
to your computer...

Check to make sure if you have adequate disk space etc...

Check with your hardware vendor for any BIOS updates
etc...

Technical information:

*** STOP: 0x0000008E (0xC0000005, 0xF99c5CFD, 0XF9E74800,
0x00000000)

*** setupdd.sys - Address F99C5CFD....
*** ini910u.sys - Address F9E74800....

I did download BIOS updates for the HP Pavilion 7955 from
the Hewlett Packard site and tried to update the system
first...(actually the BIOS had already been updated with
the most current version).

I have tried numerous methods to try and solve this
problem. I believe that the answer lies in the
BIOS...however I have gone over it with a "fine tooth
comb" and have failed to derive the solution. I may be
missing the obvious...can you please assist me in this
dilemma. I look forward to your comprehensive and rapid
response. Thank you.

Gregg.