can't initialize to MBR!

Did you delete the entry for XP and then see a new one replace it in EasyBCD? When setting up dual boots here and having any problems loading any second even third installation the firrst set of entries would be wiped seeing a fresh entry even for the host OS.

Since you verfied all necessary boot files were present the refresh on them can sometime be all it takes to get a stubborn OS moving. For XP boot problems of all types there's a roubdup of all types with various other solutions. Boot Dual Missing Ntldr Vista Xp

(Note 7 still uses same type boot loader as Vista)

Yes, I entered both drives new in EasyBCD.
I also just found out in the NeoSmart forum that I have to let EasyBCD add the drive "automatically", otherwise it will not work right! See "NST/ntldr" - The NeoSmart Forums, where I am advised to: Read the last two lines of my previous post, and stop changing the disk assignment.
That's why it's auto configure, to stop people pointing it to the wrong place.
I made a new clean install of XP tonight, and it booted fine, but W7 did not boot until I changed the BIOS back to default (RAID).
Then XP doesn't boot, neither in "normal" nor in "last good config".

I saw the thread you started over there while looking for some additional references and the reply as well about not all of the older wikis catching with the latest changes seen in the 2.0.2 release. "typical"!

As far as the drive mode that's been the main obstacle for XP all along and why I suggested finding someone running the 32bit flavor to see if the game would run on that. The 32bit 7 has quite a bit more backward compatibility to more then seen with the previous version it has been found.

In fact I slapped a fast install lately on an old XP clunker where every XP driver worked on 7! onboard sound, old video card, main chipset drivers, the works! But since that was to donated for student use the drive was wiped and I spent a good night downloading and installing the 100+ updates found for XP with SP3 already installed!
(Try 5am closing time for that one! sssslowww with repeat trips to the Windows update site)

If it runs on the 32bit the problem with drive modes would be solved for you rather then fussing with constant trips into the bios since XP isn't actually supported on that model to begin with. It would save all the headaches you've been running into.

At least you now know why the entry in the latest version of EasyBCD wasn't working for you. But the best idea is still considering a try of the game on the 32bit 7 especially since MS plans to repeat their reduced prices for the Home Premium edition this fall a year after 7's release.

It's not just for the game I want to get XP working on the second drive. Now that I have an actual dual boot screen popping up it seems a shame we can't overcome the last hurdle of XP actually booting up! It booted fine as long as I had the BIOS set to IDE, but that didn't work for W7, so I had to reset it to default.

Have you gone to the Windows update site since you got XP running again? You might just run into some optional hardware updates for the sata/Raid controllers there as well as anything else not seen at the HP support site. You'll need them!

Night Hawk said:

Have you gone to the Windows update site since you got XP running again? You might just run into some optional hardware updates for the sata/Raid controllers there as well as anything else not seen at the HP support site. You'll need them!

I tried while I was in XP, but couldn't get the Internet connection going. The TCP setting is not found.

That's always fun! What type of connection are you running there?

I know when swapping cases back and forth while working on a new build that will be seeing the 64bit Home Premium and reconnecting the main case later I had some fun getting back on with cable here.

The modem was turned off, unplugged, replugged, powered up again due to the other build grabbing it's own cofiguration. Looking under network adapters in the device manager is the first place to see is listed there. If you see more then one item the default you use is left enabled while anything else has to be disabled if not uninstalled.

Night Hawk said:

That's always fun! What type of connection are you running there?

I have a cable modem going to a wireless router. Using a cable connector from router to PC.

At first you may have to follow similar footsteps by looking over the ISP's own FFAQs. Adding a router in at first was a pain here for sure! That was solved however with a fast trip through the ISP's support pages.

I can't say this method would work well for you however depending on if you plugging into the router by usb or by a nic card installed in a pci slot to be hardwired out to the router. This would be a quick set of steps to take.
1) Review support for router as well as installation of software/drivers on XP
2) Review the Device Manager>network adapter sub section to if the adapter item is working properly with a right click for the properties screen and not seeing any yellow or red marked item(s).

Now depending on your ISP if you have an assigned user name/password you would then set up a new account in Outlook Express using that information to get mail going while if nothing is yellow marked in the network adapter sub.

3) Look at the "Network Connections" in the CP being XP there. It wouldn't be any good showing screens from the XP Mode for sure since that uses NAT virtual networking.

Your interest would be looking at the Local Area Connection Status to see if XP is all set as far as the router is concerned. Most likely XP is already synced with the router but may still need to get past that.

Have you connected with the same connection with XP previously with the router inline? If you start recycling power on both router and modem and synce the modem with the ISP while everything is shutdown you could lose the connection for 7.

The methods can be different at times between the two versions. Here while the router was inline it was still hardwired by the RJ-45 cables for both pc and modem.

I have a cable connection that is "always on", and usually gets picked up by any system without entering user/pass, which I don't have anyway.