I do it all the time in order to achieve full OS separation in
a multi-booting environment. However, you need a proper
boot manager to do this successfully. Windows cannot do
it by itself.
I find that ntldr can very well load an OS from an Extended
partition, but ntldr must reside in a Primary partition marked
"active" on the booting HD. The trick is to get "rdisk()" right
in the boot.ini file. The MS standard partition numbering
scheme begins with the all Primary partitions, then procedes
through the Logical Drives within the Extended partition.
Thus, even though the Extended partition may be the first
partition on the HD, any Primary partitions on the HD will be
numbered before the Logical Drives in the Extended partition.
Once you get rdisk() right, the boot.ini/ntldr team acts in the
usual way.
The OP must avoid installing WinXP on drive D: because
this is where Win98 resides. The installer will most likely
do this automatically but one never knows . . .
You misunderstand my question. Without an OS running, there
ARE no "C:" or "D:" or "E:" partitions. There are only partition #!,
partition #2, etc. So my question is when you say "Make sure it
goes to drive C:", do mean to *tell* the installer to make the OS
call its own partition "C:" or "D:", or do you mean that the installer
should put the OS in the 1st or 2nd or 3rd, etc., partition?
Remember the experiment you did with the clone wherein no
matter which partition you put it in, it continued to call its own
partition whatever its "parent" OS called *its* own partition.
That meant that the *name* that the OS calls a partition (e.g. "C:")
was not tied to the partition but to the OS that refers to it.
*TimDaniels*