Reinstall of windows for new board & chip???

[cliffro]

Ok, so you want an upgrade. Well, your previous plan is sounding good, namely:

"So basically, I might as well build a whole new machine and use Laplink between them while this one still works, and then sell the old case or keep it in the garage.:

Yep, if you're going to change chipsets (NForce 4 to n750), this is the only reliable path I know of. Yes, it's a PITA.

The New Number 2

No it's not a PITA

You can usually do a "repair install" when replacing hardware, even the motherboard/cpu including one with a different chipset. I have a friend that did it countless times on his. And I've performed it on a few new builds/upgrades as well.

Here is a site that explains it and some warnings, and work-arounds if the Repair option is not listed(it will enable the repair option if its not present).

Repair Install Instructions

Anyway, this is very trivial, I'm surprised no one has mentioned the Repair Install method.

 

[shutterspeed]

I did that with the hard disc from my Acer laptop to my Dell and kept getting various errors on boot.

So nope...didnt work. The Acer was an AMD and the Dell is an Intel Core Duo. so very different, which might be the issue. But I am past it on the laptop, and dont want ot go through it again in the desktop.

So from my experience, that doesnt always work either. I have no idea why. It should.

SRM

 

[thenewnumber2]

Anyway, this is very trivial, I'm surprised no one has mentioned the Repair Install method.

Because it rarely works... you've been more fortunate than most.

The New Number 2

 

[shutterspeed]

Agreed. I think it might work, like someone here said...when you have two chipsets from the same manufacturer that are maybe one version apart. Beyond that, I think you are stuck.

 

[croc]

Shutterspeed, open up a console window and type in 'regedit'. Now look for your favourite app (control-f works well, keep looking until you run out of entries...)

That's one app. You mentioned, what ~70 some apps? Tedious, long slow and scary proposition for someone who doesn't know what the registry entries really do, or what the binary keys really mean. I've done it several times, the last to switch from an asus socket 939 MB to a dfi socket 939 in XP when the repair option didn't work. Frankly, took longer than just doing a fresh install... (and I am supposed to know what I'm doing)

 

[apache_lives]

Reinstalls are good for your system and should be done ever year or so depending on usage - keeps the system running fresh!

 

[cliffro]

All I know is that Ive gone from an A7S333(Athlon XP/SiS chipset) to an A8V-Deluxe(Athlon64/Via) to a Gigabyte Nforce 4 SLI(A64 X2) using the Repair Install/Dirty Install method.

 

[shutterspeed]

Shutterspeed, open up a console window and type in 'regedit'. Now look for your favourite app (control-f works well, keep looking until you run out of entries...)

That's one app. You mentioned, what ~70 some apps? Tedious, long slow and scary proposition for someone who doesn't know what the registry entries really do, or what the binary keys really mean. I've done it several times, the last to switch from an asus socket 939 MB to a dfi socket 939 in XP when the repair option didn't work. Frankly, took longer than just doing a fresh install... (and I am supposed to know what I'm doing)

I dont think you have read the thread. This isnt what we are talking about.

Are you saying that each app has registry parameters and their own drivers and such that address the chipset and specific CPU? Are you saying that when they are installed, that they install files and such that are specific to a given chipset and/or CPU? If so, and if that is the case, then it makes a lot more sense.

I do not think that it works that way however, as to me, that would seem to be the point of having and operating system to begin with; to create a common environment and interface for all the apps to function within.

However, it seems to be the belief of most here (and not that that means a whole lot because we don't really know the knowledge and experience level of those chiming in...) that the files that are specfic to the chipset are OS based only.

If that is the case, then it stand to reason that one could change those regsitry files that are specific to the chipset.

Boy, it sure would be nice to have someone who is a high level programmer who could at least explain the situation here and why this migration thing is such a pain, and why it cannot be rectified or simplified.

Is there anyone here on that level???

 

[croc]

I dont think you have read the thread. This isnt what we are talking about.

Are you saying that each app has registry parameters and their own drivers and such that address the chipset and specific CPU? Are you saying that when they are installed, that they install files and such that are specific to a given chipset and/or CPU? If so, and if that is the case, then it makes a lot more sense.

I do not think that it works that way however, as to me, that would seem to be the point of having and operating system to begin with; to create a common environment and interface for all the apps to function within.

However, it seems to be the belief of most here (and not that that means a whole lot because we don't really know the knowledge and experience level of those chiming in...) that the files that are specfic to the chipset are OS based only.

If that is the case, then it stand to reason that one could change those regsitry files that are specific to the chipset.

Boy, it sure would be nice to have someone who is a high level programmer who could at least explain the situation here and why this migration thing is such a pain, and why it cannot be rectified or simplified.

Is there anyone here on that level???

I don't program to that level any more, but I do know some that still do. Many apps install different registry keys based on what hardware they are running on. Photoshop and Acad are two such apps, they will search the local_machine registries, then write their own entries based on what they find. So, CS4 for instance, will install differently based on the number of cores it finds, as well as the amount of physical memory. Acad is more concerned with graphics and pointing devices, but you get the point. Many games also load differently based on the platform that they find as well. Want easy? try Unix... (Croc makes joke)

 

[shutterspeed]

I would think that those programs verify those settings when they start up not on boot-up, and then make corrections as needed. Even so, reinstalling one or two programs instead of all of them is still better.

Secondly, whatever the apps are doing would have nothing to do with windows booting/startup...would it? Why would something photoshop does give a hal.dll error?

Beyond that, Pshop is the one I am most concerned about because I have so many actions and plug ins for my photography business. Each has their own settings that I have tweaked to get just right for my signature look and style. There appears to be no way to retain that on migration. I image my drives regularly, in case of an HDD failure, but this is entirely different.

The Pshop migration is not as simple as to copy the actions folder over, because some of them have their own dll files, and plug-ins are like their own mini-program anyway.

So it is more than simply the reinstall process. Eve nreinstalling will set me back dramatically.

 

[thenewnumber2]

Windows "could have been" designed to be migrated between systems with little difficulty. It wasn't. This was completely intentional... think about things like "security" and "anti-piracy", and stuff like that. Microsoft (and other app developers) have no interest in giving you an easy path to perform this operation.

You aren't on to anything novel here, Shutterspeed. The seamless migration tool that you desire would have existed for years if such a thing were possible. A high level programmer could give you a more erudite answer, but it will not help you resolve your situation.

I think Laplink is the closest you're going to find, and it's not nearly perfect. You should also check and see if the specific apps you are concerned about have any tools to make the migration less painful.

The New Number 2