How would I dual-boot in this scenario?

[gregrocker]

That's technically impossible as far as I know. You can't merge an unbootable (or any) OS into a reinstall. I would not even copy over settings as they are a corruption path defeating the purpose of a Clean Reinstall.

I tried to tell you this.

If you need your old install then there were other steps I offered to try everything possible to get it started. I suggest you go back to the top of the thread and work through every step given on your clone, plugged in by itself, leaving out your lengthy flights of fantasy which interrupted the flow so badly you've likely missed the fix.

 

[desertoth]

If that's the case, then I suppose I have much work ahead of me in manually restoring everything piece by piece. I'll post if I encounter troubles.

Perhaps we'll postpone that XP business for after New Years'...

 

[gregrocker]

As long as you stick with the tools and methods given in Clean Reinstall - Factory OEM Windows 7
you'll have a perfect install.

 

[desertoth]

I've tried to figure out a solution, but I'm finding certain major issues to be insurmountable.

1. Windows 7 will only permit very low resolution settings, a maximum of something like 1200 x 1000 or thereabout. Before this incident, my setting was 1900 x 1600 or thereabout. Everything is also ineffably uglier, somehow.

2. Windows 7 can not find my adapter/DSL router. It is attached to the computer via Ethernet and is also wireless capable. In fact, Hiren's BootCD can connect to the Internet through it; this post was typed on Hiren's browser. No amount of reboots (of either PC or router) can induce Windows to recognize the router. It stubbornly refuses to recognize the presence of any network hardware.

3. I set up a dummy account to test how Windows would react to my copying in my old Desktop, which amounted to at least 3/4 of the content on my old install. I had to do this from Hiren's BootCD, as Windows does not permit me to access the folder for my old profile on the external. I receive a prompt to gain permissions to access the directory, but no developments come from clicking "Continue". I checked the permissions and set them to full where available, yet still the same nonsense.

3.a. The dummy account is broken. Near any operation I attempt to perform returns an error claiming a lack of privileges on my part. As the dummy account is has admin privileges, this is clearly related to the aforementioned bug. While the dummy account is no loss, what it all amounts to is that I am left without means to access the majority of my files and programs from or within Windows.

I'm at a loss.

 

[gregrocker]

Did you follow the step in the tutorial which says to put your wireless/ethernet driver on stick or CD so that if it isn't provided during install you can install it to get online quickly? Do that now.

First run the adapter driver's installer as Adminstrator, watch the connection icon in bottom right system tray for network to show up to connect.

If that fails what shows up under network adapters in Device Manager? For the related device, from the Driver tab>Update driver choice, browse to where the driver installler unzipped the driver files to pick up the driver. It may take some trial and error.

If this fails try it for the other network adapter. I've never seen it not work for both. It has nothing do do with the router or modem unless one or both of them need rebooting. Try ethernet with wire connected directly to modem.

 

[desertoth]

Drivers! How could I not have thought of it.

I installed a slew of drivers (though not to my knowledge any for motherboard or chipset - can't figure that out), and items 1 & 2 have been resolved.

#3 is still troubling me, however. I don't have proper access to the majority of my files!

Further, I will need to reconfigure or even reinstall most of my programs. I really can't start on that in earnest until I have one solid user profile set up with all my old User Profile content.

To be more specific, it's something like this.

Changing sharing properties does nothing, and in the owners tab for advanced security settings the owner is listed as:

Unable to display current owner.

The folder is listed as being 0 bytes big, though the partition as a whole is still the same size so the contents must still be within. They in fact are, as I can see them in Hiren's and am able to copy them over. Attempting to operate on the copied files within Windows leads to the error described in my previous post. What be the prognosis?

 

[desertoth]

It's nice when things come together of their own accord. I gave the machine another reboot and found access had spontaneously been granted.

Merry Christmas indeed!

 

[gregrocker]

I'm assuming since you had to install a bunch of drivers that you didn't follow the instructions to install all of your Important and Optional Windows Updates first thing until all the necessary rounds were completed with reboots?

Try Take Ownership Shortcut on the XP file backup.

If that fails since you know that it works boot into Hirens XP Explorer to copy the files into the Win7 User folders thereby bypassing all permissions.

I don't know what you mean by setting up a Dummy account. You should have set up your User account during install. Will you please not mess with this to try something outlandish like everything else you've done in the thread, but instead do what everyone else does which is populate the User folders, install your programs?

 

[desertoth]

Oh sure, that's what I had done earlier - but the noted bugs wrecked everything. Hopefully that's all in the past now.

 

[desertoth]

I'm prepared to take on this project once more. This time, I'm considering a different approach:

1. Wipe the external.
2. Make a disk image backup of my W7/internal HD (which is almost exactly as it used to be by now) onto the external.
3. Clone the XP drive onto the internal, using Macrium.
4. Ensure all partitions are inactive on the internal, using Partition Wizard.
5. Using Macrium bootable media, reimage the backup from the external onto the internal.
6. Ensure the reimaged partition containing W7 is active, using Partition Wizard.
7. Boot normally, with the expectation that W7 will boot.

I think I've got it this time.

 

[gregrocker]

Your PM says that you confirmed that adding a HD will not in fact void your warranty as I told you weeks ago in the 2nd post in this thread. So I don't understand why you don't just add the extra HD to boot it via the BIOS after making the adjustments if necessary using Win7 Paragon Virtualization Manager. No need for EasyBCD, boot XP using the BIOS Boot menu key.

Otherwise if you're still not able to cooperate then what I would do is Clean Install Win7 following the steps I gave you to get a perfect install, then image XP to a partition, add it with EasyBCD then if necessary to start it run Paragon to adapt it to the new hardware.

 

[desertoth]

Well, as I'd mentioned, W7 was back in perfect order some time ago.

Edit: To save confusion with the following paragraph, which may be imperfectly worded, just take away that I attempted both your plan and my own, starting and ending with yours through three separate attempts.

I see that your (software solution) recommendation was the old one. Well, I did it, and now look: over the past few days I even tried it my way as outlined in the last post Page 10, using the Ubuntu machine to store the XP image so that the W7 image (from my plan) could be preserved. On the third attempt I repeated your variant. The result has been the same throughout the attempts, and it's a very interesting one. Listen to this...

1. I have the W7 partition and the XP partition on my machine.

2. The XP partition is inaccessible through Windows Explorer.
2.a. W7, of course, is working.

3. The XP partition is the active one.
3.a. Setting either System Reserved or C Active leads to the same old error screens I described a while back. HOWEVER, setting the XP partition Active allows W7 to load normally and perfectly, with all settings and files.

How could that even be possible? This techno-wizardry is beyond me. If you've got any further advice for me, I'm open to it, but I think this conclusively shows that in my case something bizarre and insurmountable is at work.

Images to illustrate some of this:

It's too much for me to comprehend, and is honestly rather disheartening.
Perhaps at some future time I'll work up the courage to attempt a hardware install...

 

[desertoth]

I have downloaded the files, and unzipped them. The folders have .inf files within. The download site claims that they are compatible with both W7 and XP Media Center Edition.

I can not claim to understand how to check that the chipset of the files I downloaded is the XP chipset for my model PC. To be honest, I don't know what that means. If I understand the term "chipset" correctly, then mine should be Intel Sandy Bridge. Beyond that...

 

[gregrocker]

On the Intel downloads page you would choose your XP version.

 

[desertoth]

Well, yes, that's what I did. I downloaded all the versions in theog's link that were compatible with my XP (Media Center).

Supports SATA RAID 5/10 on specific desktop platforms, SATA RAID 0/1, AHCI,

ore> Windows Server 2003 *, Windows Server 2003 Enterprise x64 Edition*, Windows Server 2003 Standard Edition*, Windows Server 2003 Standard x64 Edition*, Windows Server 2008 *, Windows Vista *, Windows Vista 32*, Windows Vista 64*, Windows XP *, Windows XP Home Edition*, Windows XP Media Center Edition*, Windows XP Professional x64 Edition*, Windows XP Professional*

The f6flpy zips, both 32 and 64 bit (where available).

I really don't see why not one of these would work.