Also be careful about not having any encrypted files or folders made
private. I remember that once I could not access my data after a new install
because I had password. Or learn how to back up your encryption keys.


"TT" wrote in message
...
one_red_eye wrote:

"jim" wrote in message
...

I'd like to ask some questions about replacing/changing a mobo in an XP

pro

system. I've done some research on this issue and have come to the

following

conclusions.

XP is not quite as Plug & Play as 98[SE] was in this regard. One can not
just take the OS HD and put it in another box and expect it to boot and
re-find everything and install all the appropriate drivers etc. like it
would in 98SE.

The limitations appear to be in two areas. The first is the HAL which is

a

function of the CPU and number thereof and presence/absence of ACPI mobo
BIOS. The second is the HD drivers.

I've found all sorts of site/articles regarding how to do this and fix

these

issues for the mobo ATA controller case. Other HD cases seem to be
tractable using the F6 install drivers(SCSI technique). One that seems
to
be similar to many others regarding the mobo ATA HD issue is:
www.mostlycreativeworkshop.com/article11.html

My conclusion is that one should make the registry and file additions on

any

XP system so that failure recovery on new hardware is more convenient at
a
later time. Am I missing something here or is that about right.

The second issue is that HAL. If the old and new systems are single CPU
ACPI mobos then everything works. It makes no difference is one is a VIA
chipset and Athlon and the other an Intel chipset and an Intel CPU. Do I
have this right so far?

If one is going from a single CPU case to a new P4 supporting HT then one
must force in a new HAL for multiprocessor ACPI. Apparently that can be
done in Recovery console or by putting the HD in another system where

files

may be manipulated before attempting a boot on the new mobo. Right so

far?

Are the above the only two issues? Will all the other gadgets and

chipsets

etc. be redetected and appropriate drivers installed? Will one be able
to
boot and move forward in most all cases if the above two issues are dealt
with?



Why not back up your data and reinstall on the new setup?
If the old MB is bad, install your drive as a slave in another PC then
backup.

I agree-why all the extra headache when you could just either back up
or install it as a slave or partition it first and dual boot?...