M
Michael Ernst
======= snipped from previous posting ========
Here is the picture:
- You have a single disk with two partitions.
- Partition 1 is a primary NTFS partition with a new Win2003
Server installation.
- Partition 2 is a primary FAT32 partition. It has Win2000
that
was copied from an old hard disk, using the Seagate
cloning
tool.
And here are the facts of life:
- Win2003 Server will boot happily.
- Win2000 must always be visible on drive C:, because this
is
how it was born. On your machine it would show as drive
D:.
- It is not possible to boot into Win2000 on your PC when
using the native Windows boot manager.
=========== end of snipped posting ================
Sorry Pegasus, but I believe your information to be
inaccurate. I may have missed a detail or two in the mix of
the off topic garbage contained in that thread, but I've
been running Win98 on drive c: & Win2000Pro on drive d: for
several years- without a hitch. I have a single drive, two
partitions and I have my boot.ini on drive c: to boot either
OS as follows:
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows 2000
Professional"
/fastdetect
C:\="Windows 98"
When I boot to my FAT32 Win98 partition (c, my NTFS 2kPro
partition (d remains unseen. When booting 2kpro, as I
normally do, I have my Win98 c: drive & Win2kpro d: drive
totally accessible. Unless your mentioning problems due to
copying the previous c: drive to the new d: drive, which I
have no doubts causes problems with all the c: references,
the situation you describe above is certainly possible
(unless of course Win2003's boot loader is non-configurable-
is it?).
Here is the picture:
- You have a single disk with two partitions.
- Partition 1 is a primary NTFS partition with a new Win2003
Server installation.
- Partition 2 is a primary FAT32 partition. It has Win2000
that
was copied from an old hard disk, using the Seagate
cloning
tool.
And here are the facts of life:
- Win2003 Server will boot happily.
- Win2000 must always be visible on drive C:, because this
is
how it was born. On your machine it would show as drive
D:.
- It is not possible to boot into Win2000 on your PC when
using the native Windows boot manager.
=========== end of snipped posting ================
Sorry Pegasus, but I believe your information to be
inaccurate. I may have missed a detail or two in the mix of
the off topic garbage contained in that thread, but I've
been running Win98 on drive c: & Win2000Pro on drive d: for
several years- without a hitch. I have a single drive, two
partitions and I have my boot.ini on drive c: to boot either
OS as follows:
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows 2000
Professional"
/fastdetect
C:\="Windows 98"
When I boot to my FAT32 Win98 partition (c, my NTFS 2kPro
partition (d remains unseen. When booting 2kpro, as I
normally do, I have my Win98 c: drive & Win2kpro d: drive
totally accessible. Unless your mentioning problems due to
copying the previous c: drive to the new d: drive, which I
have no doubts causes problems with all the c: references,
the situation you describe above is certainly possible
(unless of course Win2003's boot loader is non-configurable-
is it?).