WinXP Pro Will not Allow Windows Repair Installation

Leonardo

I am upgrading System No. 1 (in signature) to a quad system. The only hardware changes are the motherboard and processor, which now are an Abit IP35E and Intel Q6600.

The hardware setup went without a hitch. The computer booted immediately into POST and I entered the BIOS and made the changes I wanted. I had figured I could go into Windows and install the new motherboard/chipset drivers. I had also thought that if that didn't work, I could simply perform a repair installation of my existing WinXP Pro. Nope. Windows installation progresses normally to the first installation options screen, where I do NOT select recovery console, but select install Windows. The next screen shows the correct partitions and existing WinXP installation but there is no option to press 'R' to repair an existing installation?

Any ideas? This method has always worked before, even when migrating a system over from an AMD/VIA motherborad to an Intel/Intel motherboard. Aaaarggggh.

Leonardo

Let me add some more information. I tried the installation (attempted repair installation) with two different hard drives, one SATA and the other PATA. Both drives have exactly the same load as one is a clone of the other. Same exact problem with both drives as described in the post above.

The IP35-E does not have PATA or SATA RAID. My previous motherboard did have RAID, but I never used it.

In addition to using two different drives, I also took one of the drives and made a fresh restore with Acronis from a backup I made right before I took the system apart for upgrading.

If I can figure this out, I'm going to have to reassemble the previous system configuration, perform a files and settings transfer, and just make a fresh installation of Windows. Ohhhh, I REALLY don't want to do that.

Leonardo

In Recovery Console I performed a fixmbr and fixboot. When I selected fixmbr there was a message, "This computer appears to have a non-standard or invalid master boot record." After those two steps, I rebooted and tried a repair installation again. No go.

UPDATE: I let the computer restart without resetting to boot from CD, and right at the point where POST ends and Windows starts loading "bad boot.ini" displayed. Where do I go from here? I performed an internet search on this but believe I need more personalized help.

It's 4:00 a.m. and I'm going to bed!

Kentigern

Hi Leo, I'm no expert, however, just a few ideas for you.
If you boot from win xp cd
Can you use the bootcfg/rebuild in the recovery console, then modify the boot.ini file once windows loads.
If you can get drive to load on another system try going into device manager and changing your main motherboard/processor devices to win default drivers, should stop any conflict on startup on new m/board. You'd just have to go through the new device process(s)

Qeldroma

I'm also not convinced that you still don't have to preload some drivers (you know- F6 before the install CD fully loads). Sometimes it's not the RAID but the SATA controller that needs a kick start (my ASUS needed it with the Sil controller). Still, there should have been something in your mobo manual, and usually you get the PATA to take ... but this dad-gum newer stuff(?).

Usually when you don't get the R at that point of the install means that the XP doesn't see the previous installation of Windows and hence the HD.

You might want to check with ABIT too.

Qeldroma

I've done a little research and have a couple of more thoughts-

Do you have the latest BIOS flashed?

I don't know how applicable this might be (Vista users), but I've also read that some have had success plugging in their primary into SATA port 3 and playing with the AHCI/IDE mode reference.

Tex

I think the best advice was the rebuild of the boot.ini post above. It may be referancing a differant drive from that last computer in that boot.ini. When you get the option to repair its driven by finding a valid boot.ini.

If it were me I would first do a chkdsk on the drive, make sure the bios was set to boot from that drive and do as mentioned above and do the rebuild of the boot.ini.

I know its a pain at times to reinstall the apps but if you just threw on a new copy of XP without formating you would not lose your data. You just have to run through the XP updates and add your apps. Its funny as I used to install all kinds of apps and tweaks and anymore I have maybe ten apps including dvd burning software, office, iso software, virus and spyware prevention stuff, and registry tools that I throw on. The only tweaks I do anymore are a set of reg. tweaks I have and it takes a couple minutes. I bet I can throw on XP and get all my apps on and the updates for XP loaded these days in less time then you have had to spend now jacking with that drive trying to get that repair install done... Just throw a fresh copy on it and do not format. (wink)

Tex

Qeldroma

Dang. Thanks, Tex- didn't know that. I hope it works out

QCH

As for the Press "R" to Repair... I'm betting you have a slipstreamed copy of WinXP Install CD? It's turned off because of these settings in the winnt.sif file...

[Data]
    AutoPartition=1
    MsDosInitiated="0"
    [B]UnattendedInstall[/B]="[B]Yes[/B]"

[Unattended]
    [B]UnattendMode[/B]=[B]FullUnattended[/B]
    OemSkipEula=Yes
    OemPreinstall=No
    TargetPath=Windows

I believe UnattendedInstall is the one that makes the Repair function disappear. Two options...

Try an unmodified copy of WinXP install CD

Copy the winnt.sif to a floppy and remove the UnattendedInstall line. By default, WinXP install is suppose to look for a floppy and a winnt.sif BEFORE looking on the CD for its winnt.sif.

Leonardo

Alright guys, thanks. I'm out of bed and almost ready to start this again.

<!-- / message --><!-- sig -->

Can you use the bootcfg/rebuild in the recovery console, then modify the boot.ini file once windows loads.

"Once Windows loads" - well, it doesn't. Yes, I've already been in R. Console and did fixboot and fixmbr. I could perform a 'bootcfg rebuild' in the console, but would it accomplish anything since neither of these drives (PATA nor SATA) willl boot into Windows. It makes it as far as where the dots are moving in the progress bar. It crashes at that point.

If you can get drive to load on another system try going into device manager and changing your main motherboard/processor devices to win default drivers, should stop any conflict on startup on new m/board. You'd just have to go through the new device process(s)

I did that once before, but come to think of it, I probably didn't remove all the devices and drivers that I should have.I bet I can throw on XP and get all my apps on and the updates for XP loaded these days in less time then you have had to spend now jacking with that drive trying to get that repair install done... Just throw a fresh copy on it and do not format. (wink)

I bet I can throw on XP and get all my apps on and the updates for XP loaded these days in less time then you have had to spend now jacking with that drive trying to get that repair install done... Just throw a fresh copy on it and do not format. (wink)

That's about what I'm ready to do.

Try an unmodified copy of WinXP install CD

I've been using the factory hologram CD the whole time.

Someone mentioned checkdisk - already did it, but it wouldn't hurt to do it again, would it.

Alright, I think here's how I'm going to proceed:

1) Boot with drive in another machine (that works, did it last night). See what other drivers/devices I can remove.
2) Try a repair install again.
3) If no go, rebuild the original machine and run Files and Settings Transfer Wizzard.
4) Rebuild again to the new configurations.
5) Fresh WinXP installation.
6) Run Files and Settings Transfer Wizzard.

Tex

why all the rebuild and running the transfer wizard on multiple machines?

Just put the drive in the new box. Install XP. Use xq-setup to set all the pointers to the old directorys as much as possible. (my indispensible program btw...)

Leo quit making this harder then it is. Just put that drive in the new computer and install the apps you must have. A bunch may just need a shortcut put on your desktop as they are on the drive? Just reinstall Windows XP (quit using that hologramed cd and make an iso with sp2 and all the updates on it!!!!) Install Office and Nero and your almost done! Just install xq-setup and use it to point back to where your docs, pics, favs, videos (porn) etc.. are stored before.

This should take 1 hour. No moving of hard drives and moving your settings using the wizard etc.. My XP slipstreamed actually is a DVD that installs XP with SP2, a bunch of the XP updates, Nero, Office and most my regular apps. They all install when I install XP and it does the registry updates etc.

If you play with my install DVD iso you can have it include all your drivers and everything. You can make this install so that you just boot off the cd and friggin walk away and drink some beer and come back and go ahhhhhhhhh DONE!!

Tex

Leonardo

Use xq-setup to set all the pointers to the old directorys as much as possible.

Sounds interesting. "Old directories" - where? I don't know what you mean.

Tex

xq-setup is one of if not the very best tweaking programs around. Its free too. After anti spy ware and virus protection its the next program I always install

It lets you reset where "my docs", My pics, cookies, favs etc... etc.. is stored. So you do not have to keep copying it around.

I set my user up with a directory on another partition or another drive anyway.

THATS where I setup all my volatile directories that I need to keep backed up.

And I can use XQ-setup to change the pointers for XP to all those directories.

Yes I have to copy my desktop over and change a pointer in OUTLOOK to look for my data file there but thats pretty easy. It also makes backing all the crap up really easy too. After doing this a gazillion times I know what I can leave behind and what I have to have seperate and backed up.

But Leo... you REALLY have to come over to the dark side... You need to let me setup a XP DVD for you to install from that has XP, the service packs, hot fixes, drivers and all your extra apps you NORMALLY install like Office, Nero etc... all automatically install.

The worst case is you have to hit return to accept defaults a couple times and its not fully automatic.

You can make these XP installs so easy and sweet! If you only have a few differant platforms in your home its so sweet. I used to have MB chipset drivers for like 4 MB's, drivers for 3 differant Nics, 4 differant audio drivers etc... all on one XP dvd install. I could walk to any machine throw the DVD in to boot and run and walk away. Come back after a couple beers and maybe hit return a couple times to get all the apps installed and your done. Just fire up XQ-setup to redirect where XP is looking for the standard folders (takes 30 seconds) and tell Outlook where its datafiles are... (takes another minute or two) and your done.

Cheers! And hey dude! I have really missed talking to ya!

We need to start a computer repair place up in Alaska! LOL!

Cowboy

Leonardo

Tex, your post has a LOT of good content. I'll digest it later. As it is now, MAJOR BREAKTHROUGH! I'm in Windows installing motherboard drivers now.

The FIX was Thrax's blockbuster:

Repairing Windows XP in Eight Commands

Thrax

And to think, people had the gall to tell me it didn't work. You're welcome, sir.

Leonardo

The system is running perfectly and fast!! now.

Leonardo

And to think, people had the gall to tell me it didn't work.

This is the second time I've used it with complete success. That's 2 for 2.

Last night, around 2:00 a.m., I was brainstorming, looking up help threads, doing Internet searches. The solution just wouldn't come to me. I knew that the hardware in the new system was solid, I just couldn't get why it wouldn't work in Windows, even in Safe Mode. I even removed the drive, formatted it, restored it from a fresh backup (Acronis, thank you very much), ran checkdisk, ran fixboot, ran fixmbr, all to no avail. During these hours of headbanging, I actually had been smart enough to write down my brainstorming. One of the items on my list was to run the eight-command recovery console operation. $#^&*, why didn't I just do that hours earlier?

Again, thanks.

This quad system is flying, and I haven't even started overclocking.