I have 2 harddisk, 1 installed with Win2K and one with WinXP. Both
have the same drive letters, C,D,E. The OS is installed on C.

I would attached 1 drive at a time to start up the OS. I need to copy
some files across (without using an external HDD). What would happen
if I attached both the drives ? Would the OS be corrupted and then
not be bootable ?

Thanks.

"flahmeshess" <(E-Mail Removed)> wrote in message
news:007958a8-21cc-4eba-a7e5-(E-Mail Removed)...
>I have 2 harddisk, 1 installed with Win2K and one with WinXP. Both
> have the same drive letters, C,D,E. The OS is installed on C.
>
> I would attached 1 drive at a time to start up the OS. I need to copy
> some files across (without using an external HDD). What would happen
> if I attached both the drives ? Would the OS be corrupted and then
> not be bootable ?
>
> Thanks.

One disk will be the primary master disk. It will retain the
existing drive letters C:, D: and E:. The other will be a
slave disk or a secondary master disk. It will be assigned
the next available letters. When you reconnect it by itself
later on, it will use the original letters C:, D: and E:.

Thanks Pegasus.
That's interesting. That means that I didn't have to unplug the
harddisk in the first place.

What do I need to do in this case ? When I'm in WinXP, before I
reboot, I mark the Win2K partition as active and then reboot ? Then
when I want to reboot WinXP, I mark the Win2K as active ? Is that
what I need to do ?

As I have unplug the Win2K to install my WinXP, now I don't have dual
boot. How do I create dual boot now that both the OS are running ?
In my Win2K, I have a panel that allows me to select to boot to OS or
Recovery console, can I make use of that ? Can point me to any
website that teaches me how to update the file to include WinXP as
another OS to boot ?

Thanks !!!!!!!

On Jul 22, 1:24*am, "Pegasus \(MVP\)" <I....@fly.com.oz> wrote:
> "flahmeshess" <dingdongdingd...@yahoo.com> wrote in message
>
> news:007958a8-21cc-4eba-a7e5-(E-Mail Removed)...
>
> >I have 2 harddisk, 1 installed with Win2K and one with WinXP. *Both
> > have the same drive letters, C,D,E. *The OS is installed on C.
>
> > I would attached 1 drive at a time to start up the OS. *I need to copy
> > some files across (without using an external HDD). *What would happen
> > if I attached both the drives ? *Would the OS be corrupted and then
> > not be bootable ?
>
> > Thanks.
>
> One disk will be the primary master disk. It will retain the
> existing drive letters C:, D: and E:. The other will be a
> slave disk or a secondary master disk. It will be assigned
> the next available letters. When you reconnect it by itself
> later on, it will use the original letters C:, D: and E:.

"flahmeshess" <(E-Mail Removed)> wrote in message
news:24a460ff-4a7f-460f-8985-(E-Mail Removed)...
Thanks Pegasus.
That's interesting. That means that I didn't have to unplug the
harddisk in the first place.

What do I need to do in this case ? When I'm in WinXP, before I
reboot, I mark the Win2K partition as active and then reboot ? Then
when I want to reboot WinXP, I mark the Win2K as active ? Is that
what I need to do ?

As I have unplug the Win2K to install my WinXP, now I don't have dual
boot. How do I create dual boot now that both the OS are running ?
In my Win2K, I have a panel that allows me to select to boot to OS or
Recovery console, can I make use of that ? Can point me to any
website that teaches me how to update the file to include WinXP as
another OS to boot ?

Thanks !!!!!!!

==============================

Multi-booting is a completely different question than the one you
started off with. There are several ways to do it:
- Use the native Windows boot manager, by adjusting c:\boot.ini
to suit your requirements. Very primitive and in your case not
an option.
- Use the BIOS to make one or the other disk the primary master.
Some BIOSs can do it, others can't. I think it's a clumsy method.
- Use a proper boot loader. The good ones let you boot into
any partition and hide other partitions selectively.

The one I use is XOSL (free). In your case I would create a
15 MByte XOSL partition on either disk and take it from there.
However, I would first play with it, using a spare disk, until I
was completely at ease with it. If you have a free IDE slot and
if you can lay your hands on an old hard disk (ask your friendly
computer dealer if he has a very small disk!) then you could use
it for XOSL, completely risk-free.

There are several other boot loaders. Create another post,
asking for further suggestions.

Hi ! Wow...thanks very much for the detail explanation. But if I
decided to just plug in 2 harddisk and just use the BIOS to select
which one to boot up, it will work, right ? When I select Win2K
harddisk, all the drive letters on that HDD will be correctly assigned
and the driver letter on the WinXP will be changed by Win2K. When I
use BIOS to select the WinXP, all the drive letters on the WinXP HDD
will be correctly assigned while the drive letter on the Win2K HDD
will be changed by WinXP.... so did I understand your post correctly ?

On Jul 22, 2:11*pm, "Pegasus \(MVP\)" <I....@fly.com.oz> wrote:
> "flahmeshess" <dingdongdingd...@yahoo.com> wrote in message
>
> news:24a460ff-4a7f-460f-8985-(E-Mail Removed)...
> Thanks Pegasus.
> That's interesting. *That means that I didn't have to unplug the
> harddisk in the first place.
>
> What do I need to do in this case ? *When I'm in WinXP, before I
> reboot, I mark the Win2K partition as active and then reboot ? *Then
> when I want to reboot WinXP, I mark the Win2K as active ? * Is that
> what I need to do ?
>
> As I have unplug the Win2K to install my WinXP, now I don't have dual
> boot. *How do I create dual boot now that both the OS are running ?
> In my Win2K, I have a panel that allows me to select to boot to OS or
> Recovery console, can I make use of that ? *Can point me to any
> website that teaches me how to update the file to include WinXP as
> another OS to boot ?
>
> Thanks !!!!!!!
>
> ==============================
>
> Multi-booting is a completely different question than the one you
> started off with. There are several ways to do it:
> - Use the native Windows boot manager, by adjusting c:\boot.ini
> * *to suit your requirements. Very primitive and in your case not
> * *an option.
> - Use the BIOS to make one or the other disk the primary master.
> * *Some BIOSs can do it, others can't. I think it's a clumsy method.
> - Use a proper boot loader. The good ones let you boot into
> * *any partition and hide other partitions selectively.
>
> The one I use is XOSL (free). In your case I would create a
> 15 MByte XOSL partition on either disk and take it from there.
> However, I would first play with it, using a spare disk, until I
> was completely at ease with it. If you have a free IDE slot and
> if you can lay your hands on an old hard disk (ask your friendly
> computer dealer if he has a very small disk!) then you could use
> it for XOSL, completely risk-free.
>
> There are several other boot loaders. Create another post,
> asking for further suggestions.

"flahmeshess" <(E-Mail Removed)> wrote in message
news:11664415-778d-4bf5-91fa-(E-Mail Removed)...
Hi ! Wow...thanks very much for the detail explanation. But if I
decided to just plug in 2 harddisk and just use the BIOS to select
which one to boot up, it will work, right ? When I select Win2K
harddisk, all the drive letters on that HDD will be correctly assigned
and the driver letter on the WinXP will be changed by Win2K. When I
use BIOS to select the WinXP, all the drive letters on the WinXP HDD
will be correctly assigned while the drive letter on the Win2K HDD
will be changed by WinXP.... so did I understand your post correctly ?

=================

I have never used the BIOS method myself - I only read about it
in reports from other posters. You would have to try it for yourself
or create another thread to get more details. Whatever you do, you
must ensure that the current drive letters remain as they are. Since
both installations use C: as the system drive, they must retain C:. If
you attempt to launch Windows off D:, for example, then you will
either have a system that uses some files on D: and others on C:
(which is bad) or you won't be able to log on (which is worse).
Having a second PC that is networked to the test PC would essential
for the subsequent repair/recovery process.

Create another post and ask about multi-booting!

Ok. Thanks for your help. I'll think about using the SOXL or stick
to my plug unplug method. Once my migration to WinXP is complete, I
won't need my Win2K.

On Jul 22, 7:44 pm, "Pegasus \(MVP\)" <I....@fly.com.oz> wrote:
> "flahmeshess" <dingdongdingd...@yahoo.com> wrote in message
>
> news:11664415-778d-4bf5-91fa-(E-Mail Removed)...
> Hi ! Wow...thanks very much for the detail explanation. But if I
> decided to just plug in 2 harddisk and just use the BIOS to select
> which one to boot up, it will work, right ? When I select Win2K
> harddisk, all the drive letters on that HDD will be correctly assigned
> and the driver letter on the WinXP will be changed by Win2K. When I
> use BIOS to select the WinXP, all the drive letters on the WinXP HDD
> will be correctly assigned while the drive letter on the Win2K HDD
> will be changed by WinXP.... so did I understand your post correctly ?
>
> =================
>
> I have never used the BIOS method myself - I only read about it
> in reports from other posters. You would have to try it for yourself
> or create another thread to get more details. Whatever you do, you
> must ensure that the current drive letters remain as they are. Since
> both installations use C: as the system drive, they must retain C:. If
> you attempt to launch Windows off D:, for example, then you will
> either have a system that uses some files on D: and others on C:
> (which is bad) or you won't be able to log on (which is worse).
> Having a second PC that is networked to the test PC would essential
> for the subsequent repair/recovery process.
>
> Create another post and ask about multi-booting!

You can toggle the drives in the BIOS (without unplugging them) and the
installations will maintain their respective drive letter assignment
when they are booted, the Mount Manager's drive letter assignment is
persistent and it will be respected.

You can also boot the Windows 2000 installation from the Windows XP boot
menu, you just need to add a line to the Windows 2000 installation in
the boot.ini file (the one on the XP drive) and it will allow you to
dual boot with the Ntldr boot loader. There again, the Mount Manager's
drive letter assignment will still be respected and the booted
installation will retain its assigned drive letter. You can also boot
the Windows XP installation from the Windows 2000 boot menu, but to do
so you will have to replace the Windows 2000 version of the shared files
ntldr & NTDETECT.COM, the Windows 2000 version of these files cannot
boot the newer Windows XP, the XP version of the files can boot the
older Windows 2000.

John

flahmeshess wrote:
> Ok. Thanks for your help. I'll think about using the SOXL or stick
> to my plug unplug method. Once my migration to WinXP is complete, I
> won't need my Win2K.
>
> On Jul 22, 7:44 pm, "Pegasus \(MVP\)" <I....@fly.com.oz> wrote:
>
>>"flahmeshess" <dingdongdingd...@yahoo.com> wrote in message
>>
>>news:11664415-778d-4bf5-91fa-(E-Mail Removed)...
>>Hi ! Wow...thanks very much for the detail explanation. But if I
>>decided to just plug in 2 harddisk and just use the BIOS to select
>>which one to boot up, it will work, right ? When I select Win2K
>>harddisk, all the drive letters on that HDD will be correctly assigned
>>and the driver letter on the WinXP will be changed by Win2K. When I
>>use BIOS to select the WinXP, all the drive letters on the WinXP HDD
>>will be correctly assigned while the drive letter on the Win2K HDD
>>will be changed by WinXP.... so did I understand your post correctly ?
>>
>>=================
>>
>>I have never used the BIOS method myself - I only read about it
>>in reports from other posters. You would have to try it for yourself
>>or create another thread to get more details. Whatever you do, you
>>must ensure that the current drive letters remain as they are. Since
>>both installations use C: as the system drive, they must retain C:. If
>>you attempt to launch Windows off D:, for example, then you will
>>either have a system that uses some files on D: and others on C:
>>(which is bad) or you won't be able to log on (which is worse).
>>Having a second PC that is networked to the test PC would essential
>>for the subsequent repair/recovery process.
>>
>>Create another post and ask about multi-booting!
>
>

Thanks very much John ... and thanks Pegasus....

On Jul 22, 11:44 pm, "John John (MVP)" <audetw...@nbnet.nb.ca> wrote:
> You can toggle the drives in the BIOS (without unplugging them) and the
> installations will maintain their respective drive letter assignment
> when they are booted, the Mount Manager's drive letter assignment is
> persistent and it will be respected.
>
> You can also boot the Windows 2000 installation from the Windows XP boot
> menu, you just need to add a line to the Windows 2000 installation in
> the boot.ini file (the one on the XP drive) and it will allow you to
> dual boot with the Ntldr boot loader. There again, the Mount Manager's
> drive letter assignment will still be respected and the booted
> installation will retain its assigned drive letter. You can also boot
> the Windows XP installation from the Windows 2000 boot menu, but to do
> so you will have to replace the Windows 2000 version of the shared files
> ntldr & NTDETECT.COM, the Windows 2000 version of these files cannot
> boot the newer Windows XP, the XP version of the files can boot the
> older Windows 2000.
>
> John
>
> flahmeshess wrote:
> > Ok. Thanks for your help. I'll think about using the SOXL or stick
> > to my plug unplug method. Once my migration to WinXP is complete, I
> > won't need my Win2K.
>
> > On Jul 22, 7:44 pm, "Pegasus \(MVP\)" <I....@fly.com.oz> wrote:
>
> >>"flahmeshess" <dingdongdingd...@yahoo.com> wrote in message
>
> >>news:11664415-778d-4bf5-91fa-(E-Mail Removed)...
> >>Hi ! Wow...thanks very much for the detail explanation. But if I
> >>decided to just plug in 2 harddisk and just use the BIOS to select
> >>which one to boot up, it will work, right ? When I select Win2K
> >>harddisk, all the drive letters on that HDD will be correctly assigned
> >>and the driver letter on the WinXP will be changed by Win2K. When I
> >>use BIOS to select the WinXP, all the drive letters on the WinXP HDD
> >>will be correctly assigned while the drive letter on the Win2K HDD
> >>will be changed by WinXP.... so did I understand your post correctly ?
>
> >>=================
>
> >>I have never used the BIOS method myself - I only read about it
> >>in reports from other posters. You would have to try it for yourself
> >>or create another thread to get more details. Whatever you do, you
> >>must ensure that the current drive letters remain as they are. Since
> >>both installations use C: as the system drive, they must retain C:. If
> >>you attempt to launch Windows off D:, for example, then you will
> >>either have a system that uses some files on D: and others on C:
> >>(which is bad) or you won't be able to log on (which is worse).
> >>Having a second PC that is networked to the test PC would essential
> >>for the subsequent repair/recovery process.
>
> >>Create another post and ask about multi-booting!

oh... one thought came to my mind...

is that case, should I have unplug my Win2K before I install my
WinXP ? Would I still be able to get the proper drive letter for
WinXP even thought the C, D, E drives are already assigned to Win2K ?

On Jul 23, 12:24*am, flahmeshess <dingdongdingd...@yahoo.com> wrote:
> Thanks very much John ... and thanks Pegasus....
>
> On Jul 22, 11:44 pm, "John John (MVP)" <audetw...@nbnet.nb.ca> wrote:
>
>
>
> > You can toggle the drives in the BIOS (without unplugging them) and the
> > installations will maintain their respective drive letter assignment
> > when they are booted, the Mount Manager's drive letter assignment is
> > persistent and it will be respected.
>
> > You can also boot the Windows 2000 installation from the Windows XP boot
> > menu, you just need to add a line to the Windows 2000 installation in
> > the boot.ini file (the one on the XP drive) and it will allow you to
> > dual boot with the Ntldr boot loader. *There again, the Mount Manager's
> > drive letter assignment will still be respected and the booted
> > installation will retain its assigned drive letter. *You can also boot
> > the Windows XP installation from the Windows 2000 boot menu, but to do
> > so you will have to replace the Windows 2000 version of the shared files
> > ntldr & NTDETECT.COM, the Windows 2000 version of these files cannot
> > boot the newer Windows XP, the XP version of the files can boot the
> > older Windows 2000.
>
> > John
>
> > flahmeshess wrote:
> > > Ok. *Thanks for your help. *I'll think about using the SOXL or stick
> > > to my plug unplug method. Once my migration to WinXP is complete, I
> > > won't need my Win2K.
>
> > > On Jul 22, 7:44 pm, "Pegasus \(MVP\)" <I....@fly.com.oz> wrote:
>
> > >>"flahmeshess" <dingdongdingd...@yahoo.com> wrote in message
>
> > >>news:11664415-778d-4bf5-91fa-(E-Mail Removed)...
> > >>Hi ! Wow...thanks very much for the detail explanation. *But if I
> > >>decided to just plug in 2 harddisk and just use the BIOS to select
> > >>which one to boot up, it will work, right ? *When I select Win2K
> > >>harddisk, all the drive letters on that HDD will be correctly assigned
> > >>and the driver letter on the WinXP will be changed by Win2K. *When I
> > >>use BIOS to select the WinXP, all the drive letters on the WinXP HDD
> > >>will be correctly assigned while the drive letter on the Win2K HDD
> > >>will be changed by WinXP.... so did I understand your post correctly ?
>
> > >>=================
>
> > >>I have never used the BIOS method myself - I only read about it
> > >>in reports from other posters. You would have to try it for yourself
> > >>or create another thread to get more details. Whatever you do, you
> > >>must ensure that the current drive letters remain as they are. Since
> > >>both installations use C: as the system drive, they must retain C:. If
> > >>you attempt to launch Windows off D:, for example, then you will
> > >>either have a system that uses some files on D: and others on C:
> > >>(which is bad) or you won't be able to log on (which is worse).
> > >>Having a second PC that is networked to the test PC would essential
> > >>for the subsequent repair/recovery process.
>
> > >>Create another post and ask about multi-booting!- Hide quoted text -
>
> - Show quoted text -