Can't boot to 2nd disk

[Thomas G. Marshall]

Ok, I have a brand new Dell 8300 with windows XP pro installed on the
primaryIDE/master.

This is what the boot.ini originally looked like on the primary/master:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=
"Microsoft Windows XP Professional" /fastdetect

(last line is broken up just for this post)

Now I have my old Windows 2000 pro HD that I've put on the
primaryIDE/slave position on the IDE cable. My system regards it as E:.
All seems well enough and normal.

But I cannot seem to modify boot.ini to find it.

On my old win2000 disk, when it was the only disk in the win2000 system, its
boot.ini OS entry was as follows:

multi(0)disk(0)rdisk(0)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

So I figured that the entry that I needed to place now in my new system,
where the XP installation is the primary/master, and my old 2000
installation is the primary/slave (and E, would be this:

multi(0)disk(0)rdisk(1)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

But it doesn't work.

My understanding was that rdisk() indicated the disk on the particular
controller. No? I've tried a few permutations without success.

I've even tried assuming that the primary/slave would be the 3rd disk in the
lineup:

multi(0)disk(0)rdisk(2)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

---------> NOW GET THIS BIT OF HORSE@#$%........

When I boot off the installation CD and then issue a:

bootcfg /rebuild

....which isn't a bootcfg option unless you're in the XP recovery console,
it's supposed to search through all drives looking for operating systems
and then make appropriate mods to boot.ini

So I booted from the CD, and tried that. It searched through both drives,
found
both the OS's

C:\Windows (my new winXP)
E:\WINNT (my old Win2k)

BUT THEN DECIDED TO ADD THE FOLLOWING LINE:

scsi(0)disk(1)rdisk(0)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

WTF??????????????????????????

This is /not/ what disk() is supposed to mean, as near as I can tell. And
WHY did it chose "scsi()" and not "multi()" like it should (both are IDE)!

I tried some more permutations, like changing "scsi()" to "multi()".
Nothing works.

AND THIS WAS WHAT THE RECOVERY CONSOLE "BOOTCFG" CAME UP WITH!

Total confusion.

Am I screwed out of getting my e:/WINNT windows 2000 install from working
because it was originally it's own C:, or something?

Thanks in advance.

 

[dglock]

get boot magic or system commander and save yourself a
lot of trouble!
don

 

[Thomas Wendell]

At a quick glance (90% probability) the problem your W2k doesn't work is as
you stated at the end, i.e. it was on C: when in its own machine. Now it
doesn't know how to boot from anything else. And no, the _socalled_
bootmanager provided by MS, does NOT reletter drives....

--
Tumppi
Reply to group
=================================================
Most learned here on nntp://news.mircosoft.com
Helsinki, Finland (remove NO _SPAM)
(translations from FI/SE not always accurate)
=================================================

Ok, I have a brand new Dell 8300 with windows XP pro installed on the
primaryIDE/master.

This is what the boot.ini originally looked like on the primary/master:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=
"Microsoft Windows XP Professional" /fastdetect

(last line is broken up just for this post)

Now I have my old Windows 2000 pro HD that I've put on the
primaryIDE/slave position on the IDE cable. My system regards it as E:.
All seems well enough and normal.

But I cannot seem to modify boot.ini to find it.

On my old win2000 disk, when it was the only disk in the win2000 system, its
boot.ini OS entry was as follows:

multi(0)disk(0)rdisk(0)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

So I figured that the entry that I needed to place now in my new system,
where the XP installation is the primary/master, and my old 2000
installation is the primary/slave (and E, would be this:

multi(0)disk(0)rdisk(1)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

But it doesn't work.

My understanding was that rdisk() indicated the disk on the particular
controller. No? I've tried a few permutations without success.

I've even tried assuming that the primary/slave would be the 3rd disk in the
lineup:

multi(0)disk(0)rdisk(2)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

---------> NOW GET THIS BIT OF HORSE@#$%........

When I boot off the installation CD and then issue a:

bootcfg /rebuild

...which isn't a bootcfg option unless you're in the XP recovery console,
it's supposed to search through all drives looking for operating systems
and then make appropriate mods to boot.ini

So I booted from the CD, and tried that. It searched through both drives,
found
both the OS's

C:\Windows (my new winXP)
E:\WINNT (my old Win2k)

BUT THEN DECIDED TO ADD THE FOLLOWING LINE:

scsi(0)disk(1)rdisk(0)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

WTF??????????????????????????

This is /not/ what disk() is supposed to mean, as near as I can tell. And
WHY did it chose "scsi()" and not "multi()" like it should (both are IDE)!

I tried some more permutations, like changing "scsi()" to "multi()".
Nothing works.

AND THIS WAS WHAT THE RECOVERY CONSOLE "BOOTCFG" CAME UP WITH!

Total confusion.

Am I screwed out of getting my e:/WINNT windows 2000 install from working
because it was originally it's own C:, or something?

Thanks in advance.

 

[Thomas Wendell]

Addendum: Also, even W2k should need boot files on boot disk, regardless of
what disk system is on..


--
Tumppi
Reply to group
=================================================
Most learned here on nntp://news.mircosoft.com
Helsinki, Finland (remove NO _SPAM)
(translations from FI/SE not always accurate)
=================================================

Ok, I have a brand new Dell 8300 with windows XP pro installed on the
primaryIDE/master.

This is what the boot.ini originally looked like on the primary/master:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=
"Microsoft Windows XP Professional" /fastdetect

(last line is broken up just for this post)

Now I have my old Windows 2000 pro HD that I've put on the
primaryIDE/slave position on the IDE cable. My system regards it as E:.
All seems well enough and normal.

But I cannot seem to modify boot.ini to find it.

On my old win2000 disk, when it was the only disk in the win2000 system, its
boot.ini OS entry was as follows:

multi(0)disk(0)rdisk(0)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

So I figured that the entry that I needed to place now in my new system,
where the XP installation is the primary/master, and my old 2000
installation is the primary/slave (and E, would be this:

multi(0)disk(0)rdisk(1)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

But it doesn't work.

My understanding was that rdisk() indicated the disk on the particular
controller. No? I've tried a few permutations without success.

I've even tried assuming that the primary/slave would be the 3rd disk in the
lineup:

multi(0)disk(0)rdisk(2)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

---------> NOW GET THIS BIT OF HORSE@#$%........

When I boot off the installation CD and then issue a:

bootcfg /rebuild

...which isn't a bootcfg option unless you're in the XP recovery console,
it's supposed to search through all drives looking for operating systems
and then make appropriate mods to boot.ini

So I booted from the CD, and tried that. It searched through both drives,
found
both the OS's

C:\Windows (my new winXP)
E:\WINNT (my old Win2k)

BUT THEN DECIDED TO ADD THE FOLLOWING LINE:

scsi(0)disk(1)rdisk(0)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

WTF??????????????????????????

This is /not/ what disk() is supposed to mean, as near as I can tell. And
WHY did it chose "scsi()" and not "multi()" like it should (both are IDE)!

I tried some more permutations, like changing "scsi()" to "multi()".
Nothing works.

AND THIS WAS WHAT THE RECOVERY CONSOLE "BOOTCFG" CAME UP WITH!

Total confusion.

Am I screwed out of getting my e:/WINNT windows 2000 install from working
because it was originally it's own C:, or something?

Thanks in advance.

 

[Pegasus \(MVP\)]

Ok, I have a brand new Dell 8300 with windows XP pro installed on the
primaryIDE/master.

This is what the boot.ini originally looked like on the primary/master:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=
"Microsoft Windows XP Professional" /fastdetect

(last line is broken up just for this post)

Now I have my old Windows 2000 pro HD that I've put on the
primaryIDE/slave position on the IDE cable. My system regards it as E:.
All seems well enough and normal.

But I cannot seem to modify boot.ini to find it.

On my old win2000 disk, when it was the only disk in the win2000 system, its
boot.ini OS entry was as follows:

multi(0)disk(0)rdisk(0)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

So I figured that the entry that I needed to place now in my new system,
where the XP installation is the primary/master, and my old 2000
installation is the primary/slave (and E, would be this:

multi(0)disk(0)rdisk(1)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

But it doesn't work.

My understanding was that rdisk() indicated the disk on the particular
controller. No? I've tried a few permutations without success.

I've even tried assuming that the primary/slave would be the 3rd disk in the
lineup:

multi(0)disk(0)rdisk(2)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

---------> NOW GET THIS BIT OF HORSE@#$%........

When I boot off the installation CD and then issue a:

bootcfg /rebuild

...which isn't a bootcfg option unless you're in the XP recovery console,
it's supposed to search through all drives looking for operating systems
and then make appropriate mods to boot.ini

So I booted from the CD, and tried that. It searched through both drives,
found
both the OS's

C:\Windows (my new winXP)
E:\WINNT (my old Win2k)

BUT THEN DECIDED TO ADD THE FOLLOWING LINE:

scsi(0)disk(1)rdisk(0)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

WTF??????????????????????????

This is /not/ what disk() is supposed to mean, as near as I can tell. And
WHY did it chose "scsi()" and not "multi()" like it should (both are IDE)!

I tried some more permutations, like changing "scsi()" to "multi()".
Nothing works.

AND THIS WAS WHAT THE RECOVERY CONSOLE "BOOTCFG" CAME UP WITH!

Total confusion.

Am I screwed out of getting my e:/WINNT windows 2000 install from working
because it was originally it's own C:, or something?

Thanks in advance.

If your second disk contains a Win2000 installation that saw the
light of the day as drive C: then it must end its life as drive C:.
This is not achievable with the WinXP boot loader - you must use
a third-party boot loader such as XOSL. It lets you hide individual
partitions.

 

[Jim Macklin]

Since you have XP and 2000 Pro already install and XP can
see the files on E:, why do you want to dual boot 2000 Pro?
But if you must, the easy way is to use Partition Magic to
create the MBR.


|
| "Thomas G. Marshall"
<[email protected]>
| wrote in message
| >
| > Ok, I have a brand new Dell 8300 with windows XP pro
installed on the
| > primaryIDE/master.
| >
| > This is what the boot.ini originally looked like on the
primary/master:
| >
| > [boot loader]
| > timeout=30
| > default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
| > [operating systems]
| > multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=
| > "Microsoft Windows XP Professional"
/fastdetect
| >
| > (last line is broken up just for this post)
| >
| > Now I have my old Windows 2000 pro HD that I've put on
the
| > primaryIDE/slave position on the IDE cable. My system
regards it as E:.
| > All seems well enough and normal.
| >
| > But I cannot seem to modify boot.ini to find it.
| >
| > On my old win2000 disk, when it was the only disk in the
win2000 system,
| its
| > boot.ini OS entry was as follows:
| >
| > multi(0)disk(0)rdisk(0)partition(1)\WINNT=
| > "Microsoft Windows 2000 Professional"
/fastdetect
| >
| > So I figured that the entry that I needed to place now
in my new system,
| > where the XP installation is the primary/master, and my
old 2000
| > installation is the primary/slave (and E, would be
this:
| >
| > multi(0)disk(0)rdisk(1)partition(1)\WINNT=
| > "Microsoft Windows 2000 Professional"
/fastdetect
| >
| > But it doesn't work.
| >
| > My understanding was that rdisk() indicated the disk on
the particular
| > controller. No? I've tried a few permutations without
success.
| >
| > I've even tried assuming that the primary/slave would be
the 3rd disk in
| the
| > lineup:
| >
| > multi(0)disk(0)rdisk(2)partition(1)\WINNT=
| > "Microsoft Windows 2000 Professional"
/fastdetect
| >
| > ---------> NOW GET THIS BIT OF HORSE@#$%........
| >
| > When I boot off the installation CD and then issue a:
| >
| > bootcfg /rebuild
| >
| > ...which isn't a bootcfg option unless you're in the XP
recovery console,
| > it's supposed to search through all drives looking for
operating systems
| > and then make appropriate mods to boot.ini
| >
| > So I booted from the CD, and tried that. It searched
through both drives,
| > found
| > both the OS's
| >
| > C:\Windows (my new winXP)
| > E:\WINNT (my old Win2k)
| >
| > BUT THEN DECIDED TO ADD THE FOLLOWING LINE:
| >
| > scsi(0)disk(1)rdisk(0)partition(1)\WINNT=
| > "Microsoft Windows 2000 Professional"
/fastdetect
| >
| > WTF??????????????????????????
| >
| > This is /not/ what disk() is supposed to mean, as near
as I can tell. And
| > WHY did it chose "scsi()" and not "multi()" like it
should (both are IDE)!
| >
| > I tried some more permutations, like changing "scsi()"
to "multi()".
| > Nothing works.
| >
| > AND THIS WAS WHAT THE RECOVERY CONSOLE "BOOTCFG" CAME UP
WITH!
| >
| > Total confusion.
| >
| > Am I screwed out of getting my e:/WINNT windows 2000
install from working
| > because it was originally it's own C:, or something?
| >
| > Thanks in advance.
| >
| >
| >
|
| If your second disk contains a Win2000 installation that
saw the
| light of the day as drive C: then it must end its life as
drive C:.
| This is not achievable with the WinXP boot loader - you
must use
| a third-party boot loader such as XOSL. It lets you hide
individual
| partitions.
|
|

 

[Pegasus \(MVP\)]

Not quite. If you use an appropriate boot loader (e.g. XOSL) then
you can install any MS OS on any disk in any primary or logical
partition, complete with its boot files, and get it to boot from there.
I couldn't believe it myself until I tried it.

While NT systems can boot from logical volumes they must nonetheless be on
the primary master. Linux can boot from the secondary/slave etc, but no MS
OS can.

Shane


"Thomas G. Marshall"

wrote in message news:[email protected]...

Ok, I have a brand new Dell 8300 with windows XP pro installed on the
primaryIDE/master.

This is what the boot.ini originally looked like on the primary/master:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=
"Microsoft Windows XP Professional" /fastdetect

(last line is broken up just for this post)

Now I have my old Windows 2000 pro HD that I've put on the
primaryIDE/slave position on the IDE cable. My system regards it as E:.
All seems well enough and normal.

But I cannot seem to modify boot.ini to find it.

On my old win2000 disk, when it was the only disk in the win2000 system, its
boot.ini OS entry was as follows:

multi(0)disk(0)rdisk(0)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

So I figured that the entry that I needed to place now in my new system,
where the XP installation is the primary/master, and my old 2000
installation is the primary/slave (and E, would be this:

multi(0)disk(0)rdisk(1)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

But it doesn't work.

My understanding was that rdisk() indicated the disk on the particular
controller. No? I've tried a few permutations without success.

I've even tried assuming that the primary/slave would be the 3rd disk in the
lineup:

multi(0)disk(0)rdisk(2)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

---------> NOW GET THIS BIT OF HORSE@#$%........

When I boot off the installation CD and then issue a:

bootcfg /rebuild

...which isn't a bootcfg option unless you're in the XP recovery console,
it's supposed to search through all drives looking for operating systems
and then make appropriate mods to boot.ini

So I booted from the CD, and tried that. It searched through both drives,
found
both the OS's

C:\Windows (my new winXP)
E:\WINNT (my old Win2k)

BUT THEN DECIDED TO ADD THE FOLLOWING LINE:

scsi(0)disk(1)rdisk(0)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

WTF??????????????????????????

This is /not/ what disk() is supposed to mean, as near as I can tell. And
WHY did it chose "scsi()" and not "multi()" like it should (both are IDE)!

I tried some more permutations, like changing "scsi()" to "multi()".
Nothing works.

AND THIS WAS WHAT THE RECOVERY CONSOLE "BOOTCFG" CAME UP WITH!

Total confusion.

Am I screwed out of getting my e:/WINNT windows 2000 install from working
because it was originally it's own C:, or something?

Thanks in advance.

 

[Thomas G. Marshall]

....[john jacob jingleheimer snip]...

If your second disk contains a Win2000 installation that saw the
light of the day as drive C: then it must end its life as drive C:.
This is not achievable with the WinXP boot loader - you must use
a third-party boot loader such as XOSL. It lets you hide individual
partitions.

I had thought that the bigest reason for MS to use variables to the effect
of %windowsdir% (or whatever) was so that the installation could be
/anywhere/, including any letter-colon or directory. Ah well...

 

[Rick \Nutcase\ Rogers]

Hi,

I had thought that the bigest reason for MS to use variables to the effect
of %windowsdir% (or whatever) was so that the installation could be
/anywhere/, including any letter-colon or directory. Ah well...

It is, but that is so that installers, etc. can locate it (the windows,
user, and temp directories among others) once the system itself is
installed. This is the purpose behind using variables. You cannot
relocate/reletter the system partition itself to a different position or
drive designation once installed. there are too many pointers in the
registry and other system files for that, they do not use variables, they
are hard-coded to the installation location.

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Windows
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone

...[john jacob jingleheimer snip]...

If your second disk contains a Win2000 installation that saw the
light of the day as drive C: then it must end its life as drive C:.
This is not achievable with the WinXP boot loader - you must use
a third-party boot loader such as XOSL. It lets you hide individual
partitions.

I had thought that the bigest reason for MS to use variables to the effect
of %windowsdir% (or whatever) was so that the installation could be
/anywhere/, including any letter-colon or directory. Ah well...

 

[Shane]

Interesting to know.

Shane

Not quite. If you use an appropriate boot loader (e.g. XOSL) then
you can install any MS OS on any disk in any primary or logical
partition, complete with its boot files, and get it to boot from there.
I couldn't believe it myself until I tried it.

While NT systems can boot from logical volumes they must nonetheless be on
the primary master. Linux can boot from the secondary/slave etc, but no MS
OS can.

Shane


"Thomas G. Marshall"

wrote in message news:[email protected]...

Ok, I have a brand new Dell 8300 with windows XP pro installed on the
primaryIDE/master.

This is what the boot.ini originally looked like on the primary/master:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=
"Microsoft Windows XP Professional" /fastdetect

(last line is broken up just for this post)

Now I have my old Windows 2000 pro HD that I've put on the
primaryIDE/slave position on the IDE cable. My system regards it as E:.
All seems well enough and normal.

But I cannot seem to modify boot.ini to find it.

On my old win2000 disk, when it was the only disk in the win2000

system,
its

boot.ini OS entry was as follows:

multi(0)disk(0)rdisk(0)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

So I figured that the entry that I needed to place now in my new system,
where the XP installation is the primary/master, and my old 2000
installation is the primary/slave (and E, would be this:

multi(0)disk(0)rdisk(1)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

But it doesn't work.

My understanding was that rdisk() indicated the disk on the particular
controller. No? I've tried a few permutations without success.

I've even tried assuming that the primary/slave would be the 3rd disk

in
the

lineup:

multi(0)disk(0)rdisk(2)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

---------> NOW GET THIS BIT OF HORSE@#$%........

When I boot off the installation CD and then issue a:

bootcfg /rebuild

...which isn't a bootcfg option unless you're in the XP recovery console,
it's supposed to search through all drives looking for operating systems
and then make appropriate mods to boot.ini

So I booted from the CD, and tried that. It searched through both drives,
found
both the OS's

C:\Windows (my new winXP)
E:\WINNT (my old Win2k)

BUT THEN DECIDED TO ADD THE FOLLOWING LINE:

scsi(0)disk(1)rdisk(0)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

WTF??????????????????????????

This is /not/ what disk() is supposed to mean, as near as I can tell. And
WHY did it chose "scsi()" and not "multi()" like it should (both are IDE)!

I tried some more permutations, like changing "scsi()" to "multi()".
Nothing works.

AND THIS WAS WHAT THE RECOVERY CONSOLE "BOOTCFG" CAME UP WITH!

Total confusion.

Am I screwed out of getting my e:/WINNT windows 2000 install from working
because it was originally it's own C:, or something?

Thanks in advance.

 

[Andy]

I tried it, and it works.

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows 2000
Professional" /fastdetect

The operating system that is booted becomes the C: drive, while the
other one is E:, with the CD drive being D:.

Ok, I have a brand new Dell 8300 with windows XP pro installed on the
primaryIDE/master.

This is what the boot.ini originally looked like on the primary/master:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=
"Microsoft Windows XP Professional" /fastdetect

(last line is broken up just for this post)

Now I have my old Windows 2000 pro HD that I've put on the
primaryIDE/slave position on the IDE cable. My system regards it as E:.
All seems well enough and normal.

But I cannot seem to modify boot.ini to find it.

On my old win2000 disk, when it was the only disk in the win2000 system, its
boot.ini OS entry was as follows:

multi(0)disk(0)rdisk(0)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

So I figured that the entry that I needed to place now in my new system,
where the XP installation is the primary/master, and my old 2000
installation is the primary/slave (and E, would be this:

multi(0)disk(0)rdisk(1)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

But it doesn't work.

My understanding was that rdisk() indicated the disk on the particular
controller. No? I've tried a few permutations without success.

I've even tried assuming that the primary/slave would be the 3rd disk in the
lineup:

multi(0)disk(0)rdisk(2)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

---------> NOW GET THIS BIT OF HORSE@#$%........

When I boot off the installation CD and then issue a:

bootcfg /rebuild

...which isn't a bootcfg option unless you're in the XP recovery console,
it's supposed to search through all drives looking for operating systems
and then make appropriate mods to boot.ini

So I booted from the CD, and tried that. It searched through both drives,
found
both the OS's

C:\Windows (my new winXP)
E:\WINNT (my old Win2k)

BUT THEN DECIDED TO ADD THE FOLLOWING LINE:

scsi(0)disk(1)rdisk(0)partition(1)\WINNT=
"Microsoft Windows 2000 Professional" /fastdetect

WTF??????????????????????????

This is /not/ what disk() is supposed to mean, as near as I can tell. And
WHY did it chose "scsi()" and not "multi()" like it should (both are IDE)!

I tried some more permutations, like changing "scsi()" to "multi()".
Nothing works.

AND THIS WAS WHAT THE RECOVERY CONSOLE "BOOTCFG" CAME UP WITH!

Total confusion.

Am I screwed out of getting my e:/WINNT windows 2000 install from working
because it was originally it's own C:, or something?

Thanks in advance.