I'm getting one of those annoying boot loops and I don't know what to do. I'm not sure about the car's computer's components or setup, but it was working fine running windows XP when i bought the car (its a project the old owner was running).
I have two laptop harddrives, both running windows XP. One of them (the one I use in my car PC) I reformatted and installed the OS on recently to fix the problem that was ironically a repeated boot loop again. But the previous time it had been to do with mup.sys and I resolved it by reformatting. Both hard drives work fine on my laptop.
Plugging the laptop hard drive back into the car, it starts the bootup sequence and prompts me asking how i'd like to startup my computer. I've selected safe mode, normal mode and last known good configuration, all to no avail. Just as I see the windows load bar the computer restarts and runs through its black-screen setup before repeating itself. It's not a proper restart either, its almost as though the whole thing loses power (the load bar fades from screen for a split second).
Testing out my actual laptop's harddrive on it, it's loaded up the hibernate boot (my laptop is near permanently hibernated) to the full load bar but does not progress further.
I reiterate that both hard drives load windows fine on the laptop. I don't really want to reformat as i've only just recently set the hard drive up (as well as loaded a few gigs worth of songs).
What else could be the problem? As I said, before the original corruption of the hard-drive came about, the thing worked just fine. The corruption was probably because the computer couldnt sustain the CD drive (which was transferring music to the harddrive); its connected via USB and it was because the power cut itself out that the system restarted and couldnt load back up. I may have fiddled with the computer getting the laptop hard-drive out to put it into my laptop, but i'm positive i returned everything and connected it securely.
Help would be appreciated
plug the hdd into another computer as a second drive and it should run a chkdsk as windows is loading. This will most likely fix your problem.
Rob is right though: you should perform the install with the setup you plan to use.
You can perform the install on another machine and then when you move the hdd into the carputer place the setup cd in the drive and load setup from the cd, select the option to repair the damaged windows instalation and when you get to the prompt type "chkdsk /r" without the quote marks and this should sort your problem if it is a windows problem and not a hardware problem.
This is the method I used to use when replacing motherboards in a repair shop I worked in a few years ago, 9 out of 10 times it would boot into windows and ask for driver cd's.
No, you can't do this with WinXP.
When you install WinXP, it sets up the HAL (Hardware Abstraction Layer) based on the hardware it recognizes at setup time. You move that hard drive to another PC with a different motherboard chipset, different CPU, different video or different core PC component, the HAL is going to fail.
Install WinXP on the PC you're going to use, plain and simple.
CHKDSK /R isn't going to work for the OP because that will not reconfigure the HAL for different hardware. It will only detect and attempt to correct problems with the HDD, bad sectors and partition tables.
This "shortcut" might have worked for you with Win9x, but it's not going to with WinXP. Sorry to burst your bubble.
You might be able to get away with this if you install WinXP on a HDD that is connected to the same core hardware (motherboard, RAM & video, basically) and moving the hard drive to the new system. However, I have seen different BIOS revisions on motherboards cause this method to blow up.
The only guaranteed solution is, as Rob & GiODi both stated, to install WinXP onto the HDD connected to the hardware you inted to use.
DarquePervert I know you're not going to like this but you are wrong on this one. I used to do this on a daily basis, with win xp. I don't know how this would work with with a 9x environment as I have never tried it, personally I though it was an NT thing. Have you ever actually tried this method? If you have and it didn't work for you then you were just unlucky bud.
Trust me on this one, try it out for yourself if you don't want to trust a newbie - I promise you this works. I'm not just making it up as I go along, I have alot of experience with this. I worked in a crappy PC shop for just over a year and everyday I would be replacing damaged motherboards & processors and it was pretty rare I would have to rebuild the hdd.
Yes, i have done Windoze repairs from the CD many, many times for a multitude of reasons. You don't do support for over a decade and avoid repairs of Windoze.
Actually, I think it's more a case of you perfoming this on machines w/ very similar or identical hardware. That or you have been very lucky.
Here's why your method is no guarantee:
When the install is done, the HAL is set based on the hardware detected at installation.
When you boot from the Windoze CD and run CHKDSK /R, it is going to do nothing to detect (let alone correct) differences between the HAL and the actual hardware. CHKDSK only examines the hard drive and attempts to correct errors, work around bad sectors, correct partition tables, and so forth.
So you check the disk and correct any disk errors, but if Windoze is trying to operate on hardware X as defined in the HAL and the PC now uses hardware Y, it's going to probably fail. I would not expect Windoze to be stable if it does work.
Now, if the hardware is the same (say a replacement mothernboard of the same make & model), this method can work. I have even seen it work for replacment motherboards of different brands, but w/ the same chipset.
I have also seen this method fail for same make/model motherboard with a different BIOS revision.
I do not consider it a reliable option for porting an existing Windoze install onto different hardware. I recommend a clean install of Windoze if hardare is replaced so that Windoze will establish a new, correct HAL to match the new hardware.
And I recommend to anyone swapping hardware that they do the same if they want to insure stability and reliability, at least as much as Windoze can provide.
I'm not wanting to be some young upstart here DarquePervert I should imagine you do have more technical ability than myself being a mod here, but you're not the only one with a decade of pro IT experience. I have worked in IT since I left school, the first nine years in support and now I've moved into database management - I look after police, nhs, mod and prison service databases along with many others so don't think I'm some couch locked internet surfer (I wish I had time for that).
As I said in my previous post nine times out of ten it will work, personally I wouldn't use this method on my own equipment but CharlieSuave was looking for a lazy work around "I don't really want to reformat as i've only just recently set the hard drive up (as well as loaded a few gigs worth of songs)".
As for using this method to restore windows to boards using the same hardware, chipset etc sometimes this would be the case, but more often than not I would be replacing a well branded board with Pentium 3 processor with a crappy PC Chips board with an Athlon XP - very different hardware.
I'm not trying to stir anything up here I was originally trying to help CharlieSuave with his Windows boot problem, I'll keep quiet next time.
We are all here to learn, and we do.
And it's far from hard feelings. I'm simply trying to set the record straight as to what "lazy" methods will fix the user's boot problems.
I think most everyone here will recommend that they OP install Windoze on the system he's going to use, as it's the simplest method for a non-tech to use. Not everyone is familiar with the Windoze rRepair and/or a command line.
I believe I misinterpreted your original directive, so I went back and re-read it.
You need to actually do the Windoze Repair in addition to the CHKDSK to reset the HAL, and that wasn't clear to me.
No need to keep quiet. It's how we all learn, man.