17 replies
by seanferd Accepted solution
by Former member Accepted solution
by darryl~ Accepted solution
by darryl~ Accepted solution
Have you also deleted ALL partitions then recreated a partition for a fresh install of XP? I've seen times when that's helped solve similar problems.
And like senferd said....try pressing F6 at the beginning of the install when prompted to install external HDD drivers...I've even seen situations where I've had to press F5 & not F6 to do things a little differently...have a look at the following link....it may give you some ideas.
by seanferd Accepted solution
I've found that particularly useful especially when an install fails on the HAL. Repeatedly.
So, you may actually want to nuke the disk as well with something like DBAN or Killdisk before creating new partition(s) and formatting.
by Former member Accepted solution
by seanferd Accepted solution
All those keys are relevant only to Windows. As you very well know, you Windows install has failed. hence, those keys will do nothing. You will not ever get disable restart, lat known good config, etc without an installed OS.
The F6 to install drivers may be moot - your machine came out circa 2000, so most drivers should be covered by what ships with XP. If, somehow, the drive is SATA (not IDE/ATA), then you would have to press F6 to install additional drivers when prompted thus in the early stages of installation, only then, and not at any other time.
But, as Darryl~ mentions, it might just be that you need to entirely wipe the drive before attempting to install. This is why I suggest using DBAN or Killdisk on the drive, then partion, format, install. Leftover bits from previous installs (even after formatting!) can really bugger your attempt at a fresh installation.
Until the Windows installation recognizes 1) a hard drive 2) with installation files already copied to this drive, the install will loop as you have experienced.
Is this system known to have functioned properly prior to this attempted install of XP, with all the same hardware, including the hard drive? If not, you may want to run a hard drive test with the vendor's utility (get it from the HDD maker's site) before wiping the drive as suggested and trying to install again.
http://www.tyan.com/archive/support/html/drivers_support.html
Find out which hardware shipped with you exact system - there is the distinct possibilty that you do need to install AMD chipset/processor drivers and/or SATA/RAID drivers as XP does not ship with any SATA drivers.
Check all manuals/FAQs etc., at the Tyan site until you know what is exactly required by your particular system.
If you do need to install the drivers, make sure you have them ready in a usable form (unzipped, follow instructions, etc.) on a floppy, CD, or whatever removable media for when XP installation asks you to press F6 (may be different, as Darryl~ mentions) to install any necessary drivers. It doesn't matter if BIOS can see the drive, it matters that Windows can see the drive when it first attempts to take control of the hardware.
by darryl~ Accepted solution
You are just much better at explaining it than I am :)
PurpleSkys had an old computer about the same age....every time I had to reinstall XP, I always had to delete the partitions & recreate them or else I would have all kinds of weird things happeniing....Blue Screens...reboot loops....it was very frustrating until I figured it out.
by seanferd Accepted solution
I thought that maybe being entirely long-winded and explicit might help.
But the fact that all the hardware has been replaced it a total game-changer! No point in even considering the original system!
I'm on a headdesk safari now. :p
by darryl~ Accepted solution
by Former member Accepted solution
by darryl~ Accepted solution
From: elong904
Subject: All of the things you asked are true
Message:
The motherboard, case, cd, hd,power supply are all new to each other. When the ASUS MB went bad I switched cases and put new DVD and so on in it.
_____________________________________________
You must delete all current partitions on the HDD...you would have a totally different chipset because of the different MB...that's where your trouble is coming from.
So....
You're booting with the XP Pro CD....right?
It loads the system files needed to install XP....it stops at one point and asks which partition you want to iinstall on. (this is all happening with a "blue" screen & "white" text)
At this point...highlight each partition (one at a time) by using the up/down arrows...press "D" to delete then "L" to confirm.
After they are all deleted, press "C" to create a partition (whatever size you like) & install XP on that partition....format it NTFS.
by seanferd Accepted solution
by oh smeg Accepted solution
Which just means that it's not one of the new ones and has a few years on it.
If this came from a working system I would say replace the BIOS Battery and then enter the BIOS and set the Date & Time then set the System to Performance Defaults and set the Boot Order. Remember to save the changes as you exit the BIOS and try again to load the system.
If this came as a replacement M'Board make sure that you have the right family of CPU on it and that the BIOS Clear Jumper isn't set to Clear. If it is set to clear it saves the BIOS Battery but doesn't save any changes that you make to the BIOS so what you are describing will happen every time that you try to load the system.
You also have to check that the HDD is correctly identified as well as the installed RAM and CPU. If any of this is incorrect you need to reset the BIOS to get this right before attempting to install the OS.
Also after the system gets to the first reboot after formatting the HDD and copying files you can try removing the Install Disc and see if that makes any difference when the system reboots. Most times you do not need the Install Disc in the Optical Drive to install the OS but if you are prompted for it you can always refit it to the drive to allow the install to complete.
You could also set the HDD in the BIOS to Manual and set the Drive Parameters as some times Auto doesn't work well.
Also if this is a SATA Drive it should be connected to the 0 or 1 SATA Socket on the M'Board or the M'Board will not recognize it as a Boot Drive just a HDD that it can not access directly to boot from.
If it is a IDE Drive it should be set to Master and connected tot he Primary or number 1 IDE Socket on the M'Board not the Secondary IDE Socket and it should not be set to Slave on any IDS Channel.
Lets know if that was of any help. ;)
Col
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending