clean installation problems

P

Pamela G

I finally got my bios to recognise the new HD by disabling the Promise
drivers and making sure the SATA drivers were loaded. I am trying to load
Windows XP on it as a clean install. But I am running into a bunch of errors
that stop the installation and cannot find them discussed in the MS
knowledgebase. I have both an OEM version of XP Pro, and aftermarket XP home
and Pro. I have tried using both, with similar problems. It would make more
sense if I got the same error message each time, but no! Ideas please?

With the OEM disc:
1st try: File pci.sys is corrupted
2nd try:File intelide.sys is corrupted
3rd try: File \i386\ntkrnlmp.exe could not be loaded. Error code 4

So I switched to trying the aftermarket full XP home disc
1st try: File qi1240.sys is corrupted
2nd try: File acpeic.sys caused an unexpected error (8192) at line 5964 in
d:\xpsprtm\base\boot\setup\setupic
3rd try: Got all the way through to the install/repair page, only to have
the error message that Windows XP couldn't find my HD again!!!!!!
4th try: same as #3 before


Arrgghh!
 
P

Pamela G

I did! That is the way I finally got my bios to recognise the new SATA
drive. (for more details, see my post of 8/6/08 about the crash and trying
to get the computer to even recognise I installed a new HD!)

The drive shows up in my boot sequence, after floppy and CD. That is fine,
but how come the XP install disc isn't seeing it now?

Pamela
 
P

Pamela G

I did, that is how I finally got the bios to recogise the new hard drive!

Anyway, the problem is now fixed. What I had to do: disable the Promise RAID
drivers in my bios, use my laptop to download new SATA drivers from
viaarena.com (the drivers from my motherboard manufacturer did NOT work) and
thin them out based on information on one of the tech forums I looked at,
burn the XP drivers onto a floppy (had to buy an external floppy that would
run on my Vista laptop :( ) then try a clean install from the retail XP
disks using the F6 command and loading the viaarena drivers. It took 3-4
tries, but it finally got all the way through the sequence and the computer
is usable again. (after new drivers and firmware for other things were added
and software and security measures taken, LOL)
Pamela
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top