Master/Slave

[Guest]

My old computer had windows xp home edition. The mother board went out, I
finally got a computer to put my hard drive in. As a master it will not
acknowledge windows. As a slave, it will not let me into my documents and
settings folder. I believe because I had my computer password protected.

This is how I see it. Because part of windows is embedded into the bios and
the cmos, that is why it will not fully load window while being connected to
another motherboard. Now I know a bit about DOS And the Registry, so I
imagine that is were I will have to change things. Also I had a slave drive
along with this master that is now the slave. Lol anyway the in slaved one,
shows no files when I hook it to the master I now have. This one totally
baffles me, cause when I check it's properties, it shows it's full.

I have 60 gigs full of graphics music and zipped programs and all my BOS
stuff.

 

[DL]

In order to use the old hd as the win boot disk you would need to run a
repair installation of win and install drivers supplied with your mobo
http://michaelstevenstech.com/XPrepairinstall.htm
This assumes your version of win is not an OEM version which is bios locked
to the oronal hw

In edition if hooked up as slave
http://support.microsoft.com/kb/308421/en-us

 

[DL]

Typo: "origonal hardware"

In order to use the old hd as the win boot disk you would need to run a
repair installation of win and install drivers supplied with your mobo
http://michaelstevenstech.com/XPrepairinstall.htm
This assumes your version of win is not an OEM version which is bios locked
to the oronal hw

In edition if hooked up as slave
http://support.microsoft.com/kb/308421/en-us

connected

 

[Tim Slattery]

My old computer had windows xp home edition. The mother board went out, I
finally got a computer to put my hard drive in. As a master it will not
acknowledge windows. As a slave, it will not let me into my documents and
settings folder. I believe because I had my computer password protected.

This is how I see it. Because part of windows is embedded into the bios and
the cmos,

No, no part of Windows is in the BIOS. There is an ID key of some sort
in the BIOS, and pre-installed OEM versions of Windows that come on a
Dell or HP or other large manufacturer will probably be locked to that
ID code. When the machine boots, they will retrieve that code and if
it's not what's expected, they won't boot. That makes it impossible to
transfer that copy of the OS to another machine.

that is why it will not fully load window while being connected to
another motherboard.

That could be why you can't boot using that disk as a boot disk. But
if you connect it as an extra disk (slave or different EIDE
controller), you should be able to access it.

 

[Patrick Keenan]

My old computer had windows xp home edition. The mother board went out, I
finally got a computer to put my hard drive in. As a master it will not
acknowledge windows.

It sounds like you didn't do the required repair install. Without that,
Windows is trying to load drivers for hardware that isn't there anymore.

As a slave, it will not let me into my documents and
settings folder. I believe because I had my computer password protected.

If the password was with the BIOS, that won't be correct. You may need
to remove the password protection, via Safe Mode, possibly from the
Administrator account.

Because you're booting from another account, you almost certainly need to
take ownership of the folders, also from Safe Mode. That will give that
account access to that folder structure.

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

But at least this is XP Home, not Pro, so you can't have invoked encryption.
Your situation would almost certainly cause permanent data loss (so few
people actually back up the account credentials, essential for getting out
of a situation like this).

This is how I see it. Because part of windows is embedded into the bios
and
the cmos,

Actually, no part of it is. Windows will occasionally read from the the
BIOS, but not that often, and does not insert itself into the BIOS. The
BIOS knows basically nothing about Windows.

that is why it will not fully load window while being connected to
another motherboard.

More likely, you just have jumpers incorrectly set on the hard disks, and
also must do a repair install. Then, install the motherboard drivers, then
all the Windows updates.

Now I know a bit about DOS And the Registry, so I
imagine that is were I will have to change things.

You don't access the registry through DOS or a command prompt, and the fix
is most likely the jumpers and the repair install and the new drivers.
The repair install and the new drivers should take care of the registry
changes. You should *not* have to edit the registry manually.

Also I had a slave drive
along with this master that is now the slave.

Remove other drives on the same IDE channel while you do the repair install.
Connect the CD/DVD drive to the other channel. This will prevent any
conflicts. Sometimes drives from different manufacturers have to be
jumpered in non-standard ways.

Lol anyway the in slaved one,
shows no files when I hook it to the master I now have. This one totally
baffles me, cause when I check it's properties, it shows it's full.

Sounds more and more like the jumpers are incorrectly set.

I have 60 gigs full of graphics music and zipped programs and all my BOS
stuff.

You might want to back that up to another system before you go any further.
Alternately, get a new larger hard disk to go with the new motherboard; they
are not particulary expensive now, are often faster, and are often
considerably cheaper than the value of your data.

Attach the new drive by itself to the primary IDE channel, and do a new
install. Then, attach the old drive somewhere, possibly in a USB2 case.

In any case, simply removing excess hardware for now, setting the jumpers
properly, and doing the required installs should get you going.

HTH
-pk

 

[Bruce Chambers]

My old computer had windows xp home edition. The mother board went out, I
finally got a computer to put my hard drive in. As a master it will not
acknowledge windows.

Normally, and assuming a retail license (many factory-installed OEM
installations are BIOS-locked to a specific 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:

How to Perform an In-Place Upgrade of Windows XP
http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q315341

Changing a Motherboard or Moving a Hard Drive with WinXP Installed
http://www.michaelstevenstech.com/moving_xp.html

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.

As always when undertaking such a significant change, back up any
important data before starting.

This will also probably require re-activation, unless you have a
Volume Licensed version of WinXP Pro installed. If it's been more than
120 days since you last activated that specific Product Key, you'll most
likely be able to activate via the Internet without problem. If it's
been less, you might have to make a 5 minute phone call.

As a slave, it will not let me into my documents and
settings folder. I believe because I had my computer password protected.

If you hadn't encrypted the data files (which could not have been
done with WinXP Home), you may be facing nothing more than a simple
permissions issue. Have you tried taking ownership of the old folders?

HOW TO Take Ownership of a File or Folder in WinXP
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q308421

This is how I see it. Because part of windows is embedded into the bios and
the cmos, .....

That completely wrong. *NO* part of Windows, or any other standard
operating system is, or can be, embedded into the BIOS.

... that is why it will not fully load window while being connected to
another motherboard.

No. You need to perform a repair installation.

Now I know a bit about DOS And the Registry, so I
imagine that is were I will have to change things.

Then you know that DOS is not part of WinXP and would have nothing to
do with the registry, which you would also know, based upon your
statement, cannot be accessed from DOS.





--

Bruce Chambers

Help us help you:



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

 

[Rock]

My old computer had windows xp home edition. The mother board went out, I
finally got a computer to put my hard drive in. As a master it will not
acknowledge windows. As a slave, it will not let me into my documents and
settings folder. I believe because I had my computer password protected.

This is how I see it. Because part of windows is embedded into the bios
and
the cmos, that is why it will not fully load window while being connected
to
another motherboard. Now I know a bit about DOS And the Registry, so I
imagine that is were I will have to change things. Also I had a slave
drive
along with this master that is now the slave. Lol anyway the in slaved
one,
shows no files when I hook it to the master I now have. This one totally
baffles me, cause when I check it's properties, it shows it's full.

I have 60 gigs full of graphics music and zipped programs and all my BOS
stuff.

Is the copy of XP retail or OEM? Did it come preinstalled on your old
computer (such as from Dell or HP)? If that's the case it's an OEM version
and by the license it cannot be moved to a different computer. You can
however retrieve the data from it.

To do this you need to take ownership of the files. See this link:
How to take ownership of a file or folder in Windows XP
http://support.microsoft.com/?kbid=308421

If the computer this drive is slaved to has XP Home you'll need to start in
safe mode and login to the built in Administrator account to take ownership
of the files.

If the copy of XP you had is retail then it might work in the new computer
if you do a repair install on it. See this article on moving a hard drive
with XP installed to a different computer.

http://www.michaelstevenstech.com/moving_xp.html