Add 'old' XPsp2 drive to NEW XPMedia machine-want to boot old syst

hi all-
after my old machine's mobo gave up i bought a new XP Media machine
i added the old drive to the new machine and, through bootcfg, successfully
edited the boot.ini to give me access to both drives.
[old XP2 drive is partitioned in to 5 partitions, including - C: (active
part) Win2000sp5; D: swap(ext. part.); E: apps(ext. part.); F: XPsp1(ext.
part.); G: XPsp2(ext. part.) ]

On the boot screen i can successfully start Win2000, but neither of the XP
partitions will boot (even in safe mode)
For both 'old' XP installations i get a blue screen (which i see for only a
second and cannot read) but includes "if this is the first time you've seen
this screen..."

Other info: The 'old' drive is solid newish Seagate 200 ATA tested for
errors through CHKDSK and NORTON DD

I understand that i need to update many system files and device drivers for
these OSes to work on the new box, but the thing that confuses me is that
Win2000 seems fine, whereas the XP OSes are goofed up.

Have not tried fixmbr or fixboot yet

thanks

Forget what youre thinking...Thiers no way,a hd configured for another board
can be expected to run on a diffrent type,specially with what youre now
running.
I guess if you spend the hours or days working on it it's possible,but any
tech
will tell you otherwise.

"xkater" wrote:

> hi all-
> after my old machine's mobo gave up i bought a new XP Media machine
> i added the old drive to the new machine and, through bootcfg, successfully
> edited the boot.ini to give me access to both drives.
> [old XP2 drive is partitioned in to 5 partitions, including - C: (active
> part) Win2000sp5; D: swap(ext. part.); E: apps(ext. part.); F: XPsp1(ext.
> part.); G: XPsp2(ext. part.) ]
>
> On the boot screen i can successfully start Win2000, but neither of the XP
> partitions will boot (even in safe mode)
> For both 'old' XP installations i get a blue screen (which i see for only a
> second and cannot read) but includes "if this is the first time you've seen
> this screen..."
>
> Other info: The 'old' drive is solid newish Seagate 200 ATA tested for
> errors through CHKDSK and NORTON DD
>
> I understand that i need to update many system files and device drivers for
> these OSes to work on the new box, but the thing that confuses me is that
> Win2000 seems fine, whereas the XP OSes are goofed up.
>
> Have not tried fixmbr or fixboot yet
>
> thanks

sorry you responded to my original post Andrew, i'm glad i didn't listen to
you.

Regarding my initial posting, all i had to do (no thanks to you) was to
choose - 'press R to repair Windows XP' on booting from the CD - my
installation of 'an old XP2 drive' works fine now.


"Andrew E." wrote:

> Forget what youre thinking...Thiers no way,a hd configured for another board
> can be expected to run on a diffrent type,specially with what youre now
> running.
> I guess if you spend the hours or days working on it it's possible,but any
> tech
> will tell you otherwise.
>
> "xkater" wrote:
>
> > hi all-
> > after my old machine's mobo gave up i bought a new XP Media machine
> > i added the old drive to the new machine and, through bootcfg, successfully
> > edited the boot.ini to give me access to both drives.
> > [old XP2 drive is partitioned in to 5 partitions, including - C: (active
> > part) Win2000sp5; D: swap(ext. part.); E: apps(ext. part.); F: XPsp1(ext.
> > part.); G: XPsp2(ext. part.) ]
> >
> > On the boot screen i can successfully start Win2000, but neither of the XP
> > partitions will boot (even in safe mode)
> > For both 'old' XP installations i get a blue screen (which i see for only a
> > second and cannot read) but includes "if this is the first time you've seen
> > this screen..."
> >
> > Other info: The 'old' drive is solid newish Seagate 200 ATA tested for
> > errors through CHKDSK and NORTON DD
> >
> > I understand that i need to update many system files and device drivers for
> > these OSes to work on the new box, but the thing that confuses me is that
> > Win2000 seems fine, whereas the XP OSes are goofed up.
> >
> > Have not tried fixmbr or fixboot yet
> >
> > thanks