There must be a way to do this. I have to sort of work the project in, can't work at it uninterrupted, but won't give it up until every option is exhausted.
You guys have a huge range of knowledge, so I would welcome any suggestions.
Thanks in advance.
Edit 04 November 2012:
This project completed successfully. The entire process is outlined in post 35 on page 4 of the HP forum topic linked above. And there is a bit more about it in post number 43 here.
In a nutshell, so far I have used nLite to slipstream the installer files into ISOs and saved the files as ISOs and folders. Then try to install them into Oracle's Virtualbox.
2 of 8 ISOs have installed successfully so far, and wxp pro loads and runs in vbox. It updates, accepts new software, etc.
(Yep, its a legal xp pro disk, had it for years. )
But for installing into the new, NTFS formatted 1 tb hard drive, so far thats a nogo.
The chief suspect for causing this difficulty is the UEFI boot protocol.
Windows XP requires SATA drivers for your harddrive, which need to be loaded when you install it, or else it wont boot. Repackage an nLite installation with your drive's sata drivers and you should be golden.
Superfast, the computer has win 7 home prem. preinstalled. Xp will go onto a 2nd HD, 1 tb.
Winapp, the guys over at HP forums linked me to what I believe are the correct drivers, and I slipstreamed them. That is a chore in itself. Ugh. They are here: LINK to drivers. Top download button.
The latest effort to install the slipstreamed files & drivers got almost all the way through the install process but stopped at this error screen. This was an effort to install wxp to the new HD with the original HD unplugged.
Thank you, mta. Your memory is right on target. That is an accurate and concise summary of several tutorials I have read during this project. Some of them go on to suggest the use of EasyBCD to repair the bootloader issues.
If win xp will ever install cleanly, then we are on to step 2, repair the bootloader. But the install stops at the error message shown in post 6. Don't know how to get past that.
So far, I have only tried installing win xp to the new hard drive while the original win 7 hard drive is unplugged. Didn't want to mess up the factory installation. I wouldn't mind leaving the original HD plugged in if I knew that those bootloader issues are fixable, and that win xp would install to the new HD, not the original.
Have no idea what is causing that BSOD error ... the only change to the computer is swapping HDs and installing to the new one.
Maybe I should install EasyBCD into win 7 first, then point it toward the new HD?
It is a real pity that you cannot get hold of a friends XP Pro SP3 install disc (or even XP SP2) and use that to install instead of the nlite one just for troubleshooting purposes.
It is possible you could borrow one?
Perhaps select the legacy options boot in bios for your dvd drive and see if xp installs then although this could complicate things
Perhaps if you read login123's link to the HP forums he has kindly posted you will be better informed.
Also read this thread's title.
I was feeling lazy at the moment, & sleepy too since I was up late. I probably saw the title, but I was about to crash.
Anyway, Sata drivers are pretty simple to slip stream. Point & click process via nLite. I know it sounds complex, but just use integrate drivers & let it do it's thing.
I just have a question. Why would u want to dual boot XP & 7? I am asking because if it is because of a certain feature, I got some XP features working in 7.
I recall having a similar issue getting XP to boot on a computer I wanted to move away from Vista (when Vista was a naughty fledgeling)
Installing XP will break the win7 bootloader, because installing windows overwrites bootloaders (installing XP then Win7 will retain the XP boot record, but not the other way around)
I remember it being quite a pain to load XP onto the SATA drive, but once that was done, it was relatively smooth sailing. If you boot into Win7 and check your exact drive model, you may have better luck finding the correct drivers for it.
It's because newer versions of Windows preserve the older boot settings and add theirs, while older ones will overwrite the older ones with theirs. Has something to do with version number, I believe.
You probably could. I think what happens is that Windows XP can't "detect" the win7 boot.ini, so it overwrites it with its own, whereas Windows 7 can see XP's and it just adds it's own information into that one.
Well, sure didn't make it back in 3 hours. Hazel, I have read both those articles now. Thanks for the links.
The one from the win 7 forums is what I used to learn about nLite. Am now rereading the 18 pages of comments.
After some preset word limit, the brain just goes to mush and ones life force wavers.
For Winapp and Super, do either of you know what happens after installing xp over win 7 ... the boot loader is zapped, I gather, but what happens, that is, what do I see on the screen and how do I fix it? I don't have a win 7 install disk, just the oem recovery disks and a system disk made by win 7.
Super, the reason for wanting to dual boot win xp is just that I like win xp at least as much as win 7, and have some apps that simply will not run on win 7.
mta: Thanks. The system I would actually prefer is what you seem to be suggesting. At startup, tap the escape key, get to the boot menu, and select which HD to boot. Not actually change the boot order, just select which HD. From reading other tutorials, it seems most folks don't want that, but it would be perfect for me.
The step I have not done yet is to boot up with Both HDs connected. I went back to the original HD with win 7 after the blue screen in post 6.
Edit: Just booted with both HDs connected, Win explorer recognizes the new HD but there are no files or folders on it. So I guess booting from it is not likely.
I have to quit this for a while. Will post more if anything develops.
In the meantime, if anybody has any suggestions . . .anybody . . . anybody??
