Previously: Re: Creating a bootable partition on a new harddrive

[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?).

 

[Pegasus \(MVP\)]

======= 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?).

=----

Since you decided to start a new thread, I do not know what
the original discussion subject was.

There is no problem at all with running Win98 on drive
C: and Win2000 on drive D:. However, a problem
occurs if you now try to remove drive C: and make the
partition that carries drive D: the first (and possibly only)
partition.

I am also puzzled about the purpose of this post. Did you
want to ask a question?

 

[Michael Ernst]

I mostly wanted to clarify the possibilities, but yes it did
lead to a question. This was from a posting about a month
ago which comes pretty close to the situation I will be
undertaking shortly. Your description involving Win2000 &
Win2003 seem to imply, actually you state, "Win2000 must
always be visible on drive C:" . While my current setup is
slightly different, Win2000 exists just fine on something
other than c: .

I will soon be replacing my Win98 partition with 2003 and
leaving 2000 on my d: partition. I was hoping that your
generalization of where Win2000 must exist isn't altogether
accurate in "most" situations. As I've not yet done this, I
don't want to learn first hand that the situation you've
described (involving 2000 & 2003) is dead on accurate. Is
there some caveat I should be aware of involving the 2000 or
2003 boot loader?

Sorry I didn't snip the whole original thread, most of that
thread turned into the usual pissing match.

======= 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?).



----== Posted via Newsfeeds.Com -

Unlimited-Uncensored-Secure Usenet

 

[Pegasus \(MVP\)]

I mostly wanted to clarify the possibilities, but yes it did
lead to a question. This was from a posting about a month
ago which comes pretty close to the situation I will be
undertaking shortly. Your description involving Win2000 &
Win2003 seem to imply, actually you state, "Win2000 must
always be visible on drive C:" . While my current setup is
slightly different, Win2000 exists just fine on something
other than c: .

It seems you qupte this note out of context. If you
restore the context then the note reads: "If Win2000
started its life on drive X: then it must always be
visible on drive X:". "X:" can be any drive letter.