windows 2000 and xp pro problems two hard drves d: has been imaged

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

A client of mine has windows 2000 and imaged (Norton ghost old) the second
hard with same programs etc. Now they tried to install windows xp pro on the
second drive and the computer will not boot now on either of the operating
systems. They tried to repair install windows xp again, and I guess it
didn't finish the install. So I thought I would do a repair on the windows xp
pro and now it boots, but windows 2000 missing files
winnt\system32\config\system. I know I should do a repair on the 2000
installation, but will all their programs still be in working order, on the
windows 2000? They don’t want windows 2000; they would like to have windows
xp pro and all their regular programs to work in xp pro. Should I do data
backs? What programs works the best? Should I uninstall the windows xp
install folder and then do a repair on the windows installation? How can I
make this all work two hard drives and all the programs imaged over to the
other one? Like they had it before it blue screened on them?
 
[email protected] said:
A client of mine has windows 2000 and imaged (Norton ghost old)
[to] the second hard with same programs etc. Now they tried to
install windows xp pro on the second drive and the computer will
not boot now on either of the operating systems.
Click to expand...


Did they tell the copying utility to
1) put the OS on a primary partition?
2) mark the destination partition "active"?
3) copy over the Master Boot Record (MBR)
as well?

The clone OS won't boot independently if not all 3 conditions
are met.

BTW, when booting the clone for the 1st time, don't have
the original OS visible to it. I'm not sure if Win2K works
like WinXP in this regard, but WinXP clones will bind themselves
to the "parent" if this occurs. After the 1st boot-up, the clone
can see the "parent" with no ill effects.

*TimDaniels*
 
What does ""clones will bind themselves to the 'parent'" mean?
What are the symptoms?
How can it be fixed?

Thanks.


Timothy Daniels said:
[email protected] said:
A client of mine has windows 2000 and imaged (Norton ghost old)
[to] the second hard with same programs etc. Now they tried to
install windows xp pro on the second drive and the computer will
not boot now on either of the operating systems.
Click to expand...


Did they tell the copying utility to
1) put the OS on a primary partition?
2) mark the destination partition "active"?
3) copy over the Master Boot Record (MBR)
as well?

The clone OS won't boot independently if not all 3 conditions
are met.

BTW, when booting the clone for the 1st time, don't have
the original OS visible to it. I'm not sure if Win2K works
like WinXP in this regard, but WinXP clones will bind themselves
to the "parent" if this occurs. After the 1st boot-up, the clone
can see the "parent" with no ill effects.

*TimDaniels*
Click to expand...
 
Martin said:
What does ""clones will bind themselves to the 'parent'" mean?
What are the symptoms?
How can it be fixed?
Click to expand...


It seems that pointers in the new clone will be set to point
to system files in the original OS. I had been warned about
that but it seemed not to occur consistently, so I ignored the
warning, then found that a clone called up the My Documents
folder from the "parent" partition rather than the one in its own
partition. How it recognizes it "parent" is probably privy only
to Microsoft, but I theorize that it occurs by Microsoft's design
as an effort to prevent multi-booting one copy of its WinXP
(and perhaps WinNT and Win2K) in a single machine.

Typical symptoms are simply that the clone doesn't work or
doesn't work right if the "parent" isn't present and accessible
by the clone. What you get is one "siamese" WinXP instead
of two independent ones. Cute, huh?

As far as I know, there is no way to separate the siamesed
"twins" - partly because no one I've heard of knows exactly
how it's done. There are probably many ways to prevent the
binding, some may be by software. "WinGuy" seems to use
a disk scan of the clone before starting it up. Perhaps a change
to the machine name could do it, or the product key. I expect,
though, that Longhorn will have a more elaborate mechanism
to thwart such uses. Whether this is a violation of the right to
"fair use" by the consumer is open to debate. After all, only
one copy of the OS can be in use at any one time, and then
only in the same machine.

*TimDaniels*
 
Back
Top