Clarification on Windows Install Used in 2 different machines

May 29, 2008

Hello all,

I'm trying to settle an argument with someone about the following:

Is it possible to take a hard drive out of one system (say a custom

built machine) with a fresh Windows XP installation along with my

applications, and put it into another system (another custom built

machine with different hardware) and boot up normally?

My argument is because of the different hardware and internal things

specific to the first system, there is no way that it will work in

something that has totally different hardware. I remember trying

this

in Windows 98 long ago, but something about drivers and registry

things stopped that thought cold...

If I am right or wrong, please give some supporting links/

documentation or an argument as to why.

Thanks!

May 29, 2008

Re: Clarification on Windows Install Used in 2 different machines

Whether it will boot is dependant on the Mass Storage controller

driver. If the source machine has a VIA technology chipset it will

use a VIA Driver to mount/use the hard drive Windows is installed

on. If you move that drive to a PC with a Intel Chipset then XP

will likely fail to boot since the required Mass Storage driver will

not load. Platform matches between PC1/PC2 would boot but is

going to experience a number of issues, among them Activation

and a complete re-detection of all the hardware on the new PC.

The only "Workaround" solution is prior to a platform change to

change the Mass Storage driver to a generic type which will load

on almost any chipset vendor PC and then re-apply the correct

vendor driver after the switch-over is completed.

"Chris" <chris.hogan@gmail.com> wrote in message

news:d85a78d6-ce5f-4e04-b918-119ca6d1c01b@p25g2000hsf.googlegroups.com...

> Hello all,

>

> I'm trying to settle an argument with someone about the following:

>

> Is it possible to take a hard drive out of one system (say a custom

> built machine) with a fresh Windows XP installation along with my

> applications, and put it into another system (another custom built

> machine with different hardware) and boot up normally?

>

> My argument is because of the different hardware and internal things

> specific to the first system, there is no way that it will work in

> something that has totally different hardware. I remember trying

> this

> in Windows 98 long ago, but something about drivers and registry

> things stopped that thought cold...

>

> If I am right or wrong, please give some supporting links/

> documentation or an argument as to why.

>

> Thanks!

May 29, 2008

Re: Clarification on Windows Install Used in 2 different machines

Chris wrote:

> Hello all,

>

> I'm trying to settle an argument with someone about the following:

>

> Is it possible to take a hard drive out of one system (say a custom

> built machine) with a fresh Windows XP installation along with my

> applications, and put it into another system (another custom built

> machine with different hardware) and boot up normally?

>

> My argument is because of the different hardware and internal things

> specific to the first system, there is no way that it will work in

> something that has totally different hardware. I remember trying

> this

> in Windows 98 long ago, but something about drivers and registry

> things stopped that thought cold...

>

> If I am right or wrong, please give some supporting links/

> documentation or an argument as to why.

>

> Thanks!

It won't work because of XP and activation etc, and it is also a license

violation (OEM Version)...........

It is not a violation if the XP is of the upgrade license type, but

to get it to work,,,,,,,, would be to not to boot the unit to the moved hard

drive.

but boot instead to the XP install cd and choose install then choose a

repair install when XP see's the other installation of Windows XP.

when this repair install is completed you will need to activate XP again,

over the phone no doubt, just tell them it is a motherboard replacement

under warranty and Microsoft should give you a new product code..

Clark...

--

Don't you have Google in your part of the world?

May 29, 2008

Re: Clarification on Windows Install Used in 2 different machines

On May 29, 12:36 pm, "R. McCarty" <PcEngWork-NoSp...@mindspring.com>

wrote:

> Whether it will boot is dependant on the Mass Storage controller

> driver. If the source machine has a VIA technology chipset it will

> use a VIA Driver to mount/use the hard drive Windows is installed

> on. If you move that drive to a PC with a Intel Chipset then XP

> will likely fail to boot since the required Mass Storage driver will

> not load. Platform matches between PC1/PC2 would boot but is

> going to experience a number of issues, among them Activation

> and a complete re-detection of all the hardware on the new PC.

> The only "Workaround" solution is prior to a platform change to

> change the Mass Storage driver to a generic type which will load

> on almost any chipset vendor PC and then re-apply the correct

> vendor driver after the switch-over is completed.

>

> "Chris" <chris.ho...@gmail.com> wrote in message

>

> news:d85a78d6-ce5f-4e04-b918-119ca6d1c01b@p25g2000hsf.googlegroups.com...

>

> > Hello all,

>

> > I'm trying to settle an argument with someone about the following:

>

> > Is it possible to take a hard drive out of one system (say a custom

> > built machine) with a fresh Windows XP installation along with my

> > applications, and put it into another system (another custom built

> > machine with different hardware) and boot up normally?

>

> > My argument is because of the different hardware and internal things

> > specific to the first system, there is no way that it will work in

> > something that has totally different hardware. I remember trying

> > this

> > in Windows 98 long ago, but something about drivers and registry

> > things stopped that thought cold...

>

> > If I am right or wrong, please give some supporting links/

> > documentation or an argument as to why.

>

> > Thanks!- Hide quoted text -

>

> - Show quoted text -

Thank you for your response R. McCarty; This makes total sense as you

explained it. Could you point me to a few sources where this type of

information can be found? I've been out of the PC game for quite

sometime, so it would help to know where to look when I have future

issues.

Thanks

May 29, 2008

Re: Clarification on Windows Install Used in 2 different machines

Chris wrote:

> On May 29, 12:36 pm, "R. McCarty" <PcEngWork-NoSp...@mindspring.com>

> wrote:

>

>>Whether it will boot is dependant on the Mass Storage controller

>>driver. If the source machine has a VIA technology chipset it will

>>use a VIA Driver to mount/use the hard drive Windows is installed

>>on. If you move that drive to a PC with a Intel Chipset then XP

>>will likely fail to boot since the required Mass Storage driver will

>>not load. Platform matches between PC1/PC2 would boot but is

>>going to experience a number of issues, among them Activation

>>and a complete re-detection of all the hardware on the new PC.

>>The only "Workaround" solution is prior to a platform change to

>>change the Mass Storage driver to a generic type which will load

>>on almost any chipset vendor PC and then re-apply the correct

>>vendor driver after the switch-over is completed.

>>

>>"Chris" <chris.ho...@gmail.com> wrote in message

>>

>>news:d85a78d6-ce5f-4e04-b918-119ca6d1c01b@p25g2000hsf.googlegroups.com...

>>

>>>Hello all,

>>

>>>I'm trying to settle an argument with someone about the following:

>>

>>>Is it possible to take a hard drive out of one system (say a custom

>>>built machine) with a fresh Windows XP installation along with my

>>>applications, and put it into another system (another custom built

>>>machine with different hardware) and boot up normally?

>>

>>>My argument is because of the different hardware and internal things

>>>specific to the first system, there is no way that it will work in

>>>something that has totally different hardware. I remember trying

>>>this

>>>in Windows 98 long ago, but something about drivers and registry

>>>things stopped that thought cold...

>>

>>>If I am right or wrong, please give some supporting links/

>>>documentation or an argument as to why.

>>

>>>Thanks!- Hide quoted text -

>>

>>- Show quoted text -

>

> Thank you for your response R. McCarty; This makes total sense as you

> explained it. Could you point me to a few sources where this type of

> information can be found? I've been out of the PC game for quite

> sometime, so it would help to know where to look when I have future

> issues.

>

> Thanks

Look in the Microsoft Knowledge Base, example

How to move a Windows installation to different hardware

http://support.microsoft.com/kb/249694

May 29, 2008

Re: Clarification on Windows Install Used in 2 different machines

"Chris" <chris.hogan@gmail.com> wrote in message

news:d85a78d6-ce5f-4e04-b918-119ca6d1c01b@p25g2000hsf.googlegroups.com...

> Hello all,

>

> I'm trying to settle an argument with someone about the following:

>

> Is it possible to take a hard drive out of one system (say a custom

> built machine) with a fresh Windows XP installation along with my

> applications, and put it into another system (another custom built

> machine with different hardware) and boot up normally?

>

> My argument is because of the different hardware and internal things

> specific to the first system, there is no way that it will work in

> something that has totally different hardware. I remember trying

> this

> in Windows 98 long ago, but something about drivers and registry

> things stopped that thought cold...

>

> If I am right or wrong, please give some supporting links/

> documentation or an argument as to why.

>

> Thanks!

Chris:

The simple answer is...sometimes yes, sometimes no.

In most, but certainly not all, cases involving the transfer of a HDD from

one system to another system the result will be a failed initial boot.

But in a significant number of cases the initial boot will be successful.

It's always worth a try.

In working with hundreds of different systems (in an XP environment) we have

found no common denominator that will tell us beforehand whether the initial

boot under these circumstances will be successful or unsuccessful. And

that's regardless of whether we're dealing with Intel-based or AMD-based

systems or the HDD transfer occurs between an Intel-AMD system or AMD-Intel

system.

The fact that the two systems involved have "totally different hardware"

will not negate the possibility of a successful initial boot.

Obviously when the initial boot does fail the general "fix" is to run a

Repair install of the XP operating system. In most, but again not all, cases

the result will be a bootable system. Naturally, as I'm sure you're aware,

the necessary motherboard (and possibly other auxiliary) drivers will need

to be installed following a successful Repair installation.

Anna

May 29, 2008

Re: Clarification on Windows Install Used in 2 different machines

On May 29, 2:17 pm, "Anna" <myn...@myisp.net> wrote:

> "Chris" <chris.ho...@gmail.com> wrote in message

>

> news:d85a78d6-ce5f-4e04-b918-119ca6d1c01b@p25g2000hsf.googlegroups.com...

>

> > Hello all,

>

> > I'm trying to settle an argument with someone about the following:

>

> > Is it possible to take a hard drive out of one system (say a custom

> > built machine) with a fresh Windows XP installation along with my

> > applications, and put it into another system (another custom built

> > machine with different hardware) and boot up normally?

>

> > My argument is because of the different hardware and internal things

> > specific to the first system, there is no way that it will work in

> > something that has totally different hardware. I remember trying

> > this

> > in Windows 98 long ago, but something about drivers and registry

> > things stopped that thought cold...

>

> > If I am right or wrong, please give some supporting links/

> > documentation or an argument as to why.

>

> > Thanks!

>

> Chris:

> The simple answer is...sometimes yes, sometimes no.

>

> In most, but certainly not all, cases involving the transfer of a HDD from

> one system to another system the result will be a failed initial boot.

>

> But in a significant number of cases the initial boot will be successful.

> It's always worth a try.

>

> In working with hundreds of different systems (in an XP environment) we have

> found no common denominator that will tell us beforehand whether the initial

> boot under these circumstances will be successful or unsuccessful. And

> that's regardless of whether we're dealing with Intel-based or AMD-based

> systems or the HDD transfer occurs between an Intel-AMD system or AMD-Intel

> system.

>

> The fact that the two systems involved have "totally different hardware"

> will not negate the possibility of a successful initial boot.

>

> Obviously when the initial boot does fail the general "fix" is to run a

> Repair install of the XP operating system. In most, but again not all, cases

> the result will be a bootable system. Naturally, as I'm sure you're aware,

> the necessary motherboard (and possibly other auxiliary) drivers will need

> to be installed following a successful Repair installation.

> Anna- Hide quoted text -

>

> - Show quoted text -

Very good information indeed Anna, When I was a system tech, we

always did things in order, meaning if we wanted an installtion of

Windows on a machine, we would start with a fresh install or image;

hardly ever did a repair or any hard drive swapping. There are just

way too many variables when dealing with different hardware types, I

never wanted to take a chance.

I'm trying to explain this to a young technician that thinks

everything is possible with a little time and effort. My thing is,

with a fresh install, I know what I'm getting....Playing the swap game

has always looked as a quick fix that will be more unpredictable than

what I care an OS install to be.

Thanks for the input

May 29, 2008

Re: Clarification on Windows Install Used in 2 different machines

On May 29, 2:08 pm, Bob I <bire...@yahoo.com> wrote:

> Chris wrote:

> > On May 29, 12:36 pm, "R. McCarty" <PcEngWork-NoSp...@mindspring.com>

> > wrote:

>

> >>Whether it will boot is dependant on the Mass Storage controller

> >>driver. If the source machine has a VIA technology chipset it will

> >>use a VIA Driver to mount/use the hard drive Windows is installed

> >>on. If you move that drive to a PC with a Intel Chipset then XP

> >>will likely fail to boot since the required Mass Storage driver will

> >>not load. Platform matches between PC1/PC2 would boot but is

> >>going to experience a number of issues, among them Activation

> >>and a complete re-detection of all the hardware on the new PC.

> >>The only "Workaround" solution is prior to a platform change to

> >>change the Mass Storage driver to a generic type which will load

> >>on almost any chipset vendor PC and then re-apply the correct

> >>vendor driver after the switch-over is completed.

>

> >>"Chris" <chris.ho...@gmail.com> wrote in message

>

> >>news:d85a78d6-ce5f-4e04-b918-119ca6d1c01b@p25g2000hsf.googlegroups.com....

>

> >>>Hello all,

>

> >>>I'm trying to settle an argument with someone about the following:

>

> >>>Is it possible to take a hard drive out of one system (say a custom

> >>>built machine) with a fresh Windows XP installation along with my

> >>>applications, and put it into another system (another custom built

> >>>machine with different hardware) and boot up normally?

>

> >>>My argument is because of the different hardware and internal things

> >>>specific to the first system, there is no way that it will work in

> >>>something that has totally different hardware. I remember trying

> >>>this

> >>>in Windows 98 long ago, but something about drivers and registry

> >>>things stopped that thought cold...

>

> >>>If I am right or wrong, please give some supporting links/

> >>>documentation or an argument as to why.

>

> >>>Thanks!- Hide quoted text -

>

> >>- Show quoted text -

>

> > Thank you for your response R. McCarty; This makes total sense as you

> > explained it. Could you point me to a few sources where this type of

> > information can be found? I've been out of the PC game for quite

> > sometime, so it would help to know where to look when I have future

> > issues.

>

> > Thanks

>

> Look in the Microsoft Knowledge Base, example

> How to move a Windows installation to different hardwarehttp://support.microsoft.com/kb/249694- Hide quoted text -

>

> - Show quoted text -

Thanks Bob

May 29, 2008

Re: Clarification on Windows Install Used in 2 different machines

Yes, I find the same. Changing the disk controller to a generic type improves

your chances, but doesn't guarantee success.

Basically, it's a poor design, and needs rethinking. Excessive

interdependence of components in any system makes maintenance of that system

extremely hard.

For example, consider the situation where a single mobo socket failing leads

to the need for a total hardware AND software rebuild, and re-registering of

all licensed packages on it.

Instead of Von Neumann Architecture, maybe we should term this, "Ronan Point

Architecture." <g>

"Anna" wrote:

> In working with hundreds of different systems (in an XP environment) we have

> found no common denominator that will tell us beforehand whether the initial

> boot under these circumstances will be successful or unsuccessful. And

> that's regardless of whether we're dealing with Intel-based or AMD-based

> systems or the HDD transfer occurs between an Intel-AMD system or AMD-Intel

> system.

May 29, 2008

Re: Clarification on Windows Install Used in 2 different machines

> "Chris" <chris.ho...@gmail.com> wrote in message

> > Hello all,

>

> > I'm trying to settle an argument with someone about the following:

>

> > Is it possible to take a hard drive out of one system (say a custom

> > built machine) with a fresh Windows XP installation along with my

> > applications, and put it into another system (another custom built

> > machine with different hardware) and boot up normally?

>

> > My argument is because of the different hardware and internal things

> > specific to the first system, there is no way that it will work in

> > something that has totally different hardware. I remember trying

> > this

> > in Windows 98 long ago, but something about drivers and registry

> > things stopped that thought cold...

>

> > If I am right or wrong, please give some supporting links/

> > documentation or an argument as to why.

>

> > Thanks!

On May 29, 2:17 pm, "Anna" <myn...@myisp.net> wrote:

> Chris:

> The simple answer is...sometimes yes, sometimes no.

>

> In most, but certainly not all, cases involving the transfer of a HDD from

> one system to another system the result will be a failed initial boot.

>

> But in a significant number of cases the initial boot will be successful.

> It's always worth a try.

>

> In working with hundreds of different systems (in an XP environment) we

> have

> found no common denominator that will tell us beforehand whether the

> initial

> boot under these circumstances will be successful or unsuccessful. And

> that's regardless of whether we're dealing with Intel-based or AMD-based

> systems or the HDD transfer occurs between an Intel-AMD system or

> AMD-Intel

> system.

>

> The fact that the two systems involved have "totally different hardware"

> will not negate the possibility of a successful initial boot.

>

> Obviously when the initial boot does fail the general "fix" is to run a

> Repair install of the XP operating system. In most, but again not all,

> cases

> the result will be a bootable system. Naturally, as I'm sure you're aware,

> the necessary motherboard (and possibly other auxiliary) drivers will need

> to be installed following a successful Repair installation.

> Anna- Hide quoted text -

>

> - Show quoted text -

"Chris" <chris.hogan@gmail.com> wrote in message

news:2d4ed5c4-1288-4c4c-a1d9-3af68233141a@e53g2000hsa.googlegroups.com...

Very good information indeed Anna, When I was a system tech, we

always did things in order, meaning if we wanted an installtion of

Windows on a machine, we would start with a fresh install or image;

hardly ever did a repair or any hard drive swapping. There are just

way too many variables when dealing with different hardware types, I

never wanted to take a chance.

I'm trying to explain this to a young technician that thinks

everything is possible with a little time and effort. My thing is,

with a fresh install, I know what I'm getting....Playing the swap game

has always looked as a quick fix that will be more unpredictable than

what I care an OS install to be.

Thanks for the input

Chris:

I fully understand your position that as a general proposition it's best to

fresh install the OS following a transfer of one HDD to another HDD,

regardless of whether the recipient system will boot straightaway or a

Repair install of the OS may be necessary to accomplish a bootable,

functional system. I know that there are many technicians who agree with

your point of view. I ought to know having worked with a good number of

them!

But I must say (again, as a *general* proposition) that I do not hold to

that view.

By & large I see no reason why the transferred HDD, or more precisely the

system/data on that HDD, should not properly function in the recipient

system. Again, whether it booted with or without the necessity of a Repair

install of the OS. And, of course, all this is in reference to the XP OS.

I quickly add that I'm assuming the transferable HDD is unquestionably

non-defective and there's no reason to believe a corrupt OS is present on

the drive, i.e., the system from whence the HDD originates has not been

experiencing any problems that could be traced to a problem HDD. So that as

far as we know we're dealing with a sound HDD that has experienced no

problems.

On the other hand...

Should the user feel more comfortable (for whatever reason) with a fresh

install of the OS together with the installation of his/her

program-application files and user-created data, updates, etc., I have no

problem with this.

Anna

May 29, 2008

Re: Clarification on Windows Install Used in 2 different machines

The "general" answer is NO - you can't transfer HD from one system into

another. However, there are always exceptions to the general rule. For

example, if you have reconfigured your IDE ATA/ATAPI controllers to

"Standard dual channel PCI IDE controller" AND you use VLK instead of

retail or OEM key then you will be able to do it. I have done it many

times and also this is how SYSPREP works which allows you to install

image of one system to another without having to undergo the minimum 39

minutes torment!

Hope this helps.

Chris wrote:

>Hello all,

>

>I'm trying to settle an argument with someone about the following:

>

>Is it possible to take a hard drive out of one system (say a custom

>built machine) with a fresh Windows XP installation along with my

>applications, and put it into another system (another custom built

>machine with different hardware) and boot up normally?

>

>My argument is because of the different hardware and internal things

>specific to the first system, there is no way that it will work in

>something that has totally different hardware. I remember trying

>this

>in Windows 98 long ago, but something about drivers and registry

>things stopped that thought cold...

>

>If I am right or wrong, please give some supporting links/

>documentation or an argument as to why.

>

>Thanks!

>

May 30, 2008

Re: Clarification on Windows Install Used in 2 different machines

Chris wrote:

> Hello all,

>

> I'm trying to settle an argument with someone about the following:

>

> Is it possible to take a hard drive out of one system (say a custom

> built machine) with a fresh Windows XP installation along with my

> applications, and put it into another system (another custom built

> machine with different hardware) and boot up normally?

>

Possible? Yes. Likely? Not at all. The motherboard chipsets would

have to be very similar - almost certainly from the same manufacturer

and model series.

Normally, and assuming a retail license (many factory-installed OEM

installations are BIOS-locked to a specific motherboard chipset and

therefore are *not* transferable to a new motherboard - check yours

before starting), unless the new motherboard is virtually identical

(same chipset, same IDE controllers, same BIOS version, etc.) to the one

on which the WinXP installation was originally performed, you'll need to

perform a repair (a.k.a. in-place upgrade) installation, at the very least.

As you correctly reasoned, the "why" is quite simple, really, and

has nothing to do with licensing issues, per se; it's a purely technical

matter, at this point. You've pulled the proverbial hardware rug out

from under the OS. (If you don't like -- or get -- the rug analogy,

think of it as picking up a Cape Cod style home and then setting it down

onto a Ranch style foundation. It just isn't going to fit.) WinXP,

like Win2K before it, is not nearly as "promiscuous" as Win9x when it

comes to accepting any old hardware configuration you throw at it. On

installation it "tailors" itself to the specific hardware found. This

is one of the reasons that the entire WinNT/2K/XP OS family is so much

more stable than the Win9x group.

--

Bruce Chambers

Help us help you:

http://www.catb.org/~esr/faqs/smart-questions.html

http://support.microsoft.com/default.aspx/kb/555375

They that can give up essential liberty to obtain a little temporary

safety deserve neither liberty nor safety. ~Benjamin Franklin

Many people would rather die than think; in fact, most do. ~Bertrand Russell

The philosopher has never killed any priests, whereas the priest has

killed a great many philosophers.

~ Denis Diderot

Sign In

Clarification on Windows Install Used in 2 different machines

Recommended Posts

Guest Chris

Popular Days

Popular Days

Guest R. McCarty

Guest Clark...

Guest Chris

Guest Bob I

Guest Anna

Guest Chris

Guest Chris

Guest Anteaus

Guest Anna

Guest ANONYMOUS

Guest Bruce Chambers

Similar Content

Different type of User profile folder in windows machine Joined Entra ID

Windows Server 2019 Virtual Machine Transfer

Windows 11 Machine Crashing and Restarting - bugcheck 0x0000009f

Dns sever working properly only on virtual machine

can't connect to SMB share on a Windows Server 2022 machine

Browse

Activity

Site Info