SATA Drive - Setting boot priority

I have two SATA drives installed in Asus A7N8X Deluxe mobo and no RAID
is set up. There are OSs(WXPs) installed in Disk0 and Disk1.

My problem is that I can not let an OS in Disk1 boot even if I set boot
priority of Disk1 above Disk0. When I installed the OS in Disk1 I
temporarily replaced Disk0 with Disk1, and after OS installation
completed I restored the original condition being that Disk0 connected
to the channel #1 and Disk1 to the channel #2.

I am wondering if I should have just disconnected Disk0 and then
installed OS in Disk1 while leaving Disk1 connected to the channel #2.

Could anyone shed light on the above?

Kaz Honjo

Hello

If your going to boot rom 2 OS here is somethign to look at

http://support.microsoft.com/default...;en-us;Q217210


Alvin


Honjo wrote:

I have two SATA drives installed in Asus A7N8X Deluxe mobo and no RAID
is set up. There are OSs(WXPs) installed in Disk0 and Disk1.

My problem is that I can not let an OS in Disk1 boot even if I set boot
priority of Disk1 above Disk0. When I installed the OS in Disk1 I
temporarily replaced Disk0 with Disk1, and after OS installation
completed I restored the original condition being that Disk0 connected
to the channel #1 and Disk1 to the channel #2.

I am wondering if I should have just disconnected Disk0 and then
installed OS in Disk1 while leaving Disk1 connected to the channel #2.

Could anyone shed light on the above?

Kaz Honjo

Alvin,

Thanks for your response. I am aware of this KB article but this is not the
way I want to do multi-boot. Thank you anyway for your trying to help me.

Kaz

Alvin A Brown wrote:

Hello

If your going to boot rom 2 OS here is somethign to look at

http://support.microsoft.com/default...;en-us;Q217210

Alvin

Honjo wrote:

I have two SATA drives installed in Asus A7N8X Deluxe mobo and no RAID
is set up. There are OSs(WXPs) installed in Disk0 and Disk1.

My problem is that I can not let an OS in Disk1 boot even if I set boot
priority of Disk1 above Disk0. When I installed the OS in Disk1 I
temporarily replaced Disk0 with Disk1, and after OS installation
completed I restored the original condition being that Disk0 connected
to the channel #1 and Disk1 to the channel #2.

I am wondering if I should have just disconnected Disk0 and then
installed OS in Disk1 while leaving Disk1 connected to the channel #2.

Could anyone shed light on the above?

Kaz Honjo

Hi Kaz

It's a little difficult to follow but if I'm decoding correctly.... you had
an XP installation on Disk0 on Channel #1 and then you installed XP on Disk1
also when connected to Channel #1...
That might be the source of the problem... it may be that both installations
are 'pointing' to Channel #1... as you seem to have indicated in your final
summing up.

There may be an easier solution than this, which another poster could
supply, but you could try a repair install.... booting from the XP CD with
both SATA drives connected (or maybe with just Disk 1 connected to
Channel#2) and selecting the installation on Disk 1 for repair.

You'd need to re-install SP1 and any XP updates afterwards though. As I
said there may be an quicker solution but that may be worth a try.
(Hopefully it's not another issue with the controller ;o) )

hope that helps
Pete
----------------
"Honjo" wrote in message
...
I have two SATA drives installed in Asus A7N8X Deluxe mobo and no RAID
is set up. There are OSs(WXPs) installed in Disk0 and Disk1.

My problem is that I can not let an OS in Disk1 boot even if I set boot
priority of Disk1 above Disk0. When I installed the OS in Disk1 I
temporarily replaced Disk0 with Disk1, and after OS installation
completed I restored the original condition being that Disk0 connected
to the channel #1 and Disk1 to the channel #2.

I am wondering if I should have just disconnected Disk0 and then
installed OS in Disk1 while leaving Disk1 connected to the channel #2.

Could anyone shed light on the above?

Kaz Honjo

Hello Kaz,

Thanks for using Microsoft News Group! Thanks for Alvin and Pete's posts.

To install Windows XP on your Disk 1, I suggest you do not replace Disk 0
with Disk 1. Just connect Disk 0 to channel #1, and connect Disk 1 to
channel #2. Boot with the XP CD and install XP on the Disk 1. During the
installation, you will be prompted to choose drive to install. Make sure to
choose Disk 1. You won't be able to pull disk 0 and if it fails, then XP on
disk 1 will not boot (without a repair).

If you don't want to multi-boot like above, I suggest you switch boot
devices in BIOS. Still connect Disk 0 to channel #1, and connect Disk 1 to
channel #2. After you switch boot devices in BIOS to the disk 1, then you
can install the second XP on the disk 1.

Have a great week!

Pearson Peng,
Microsoft Online Support
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Pete

You decoded it correctly. So you agree to my reasoning why WXP in Disk1 does
not boot. If repair installation is done as you suggested I think the drive
name of WXP in Disk1 becomes something other than C: because C: would be taken
by the WXP in Disk0. I would think that if a repair installation of WXP is
carried out while Disk0 is temporarily disconnected, then C: will be assigned to
the WXP drive in Disk1 being connected to the channel #2. I am particular about
a drive name of operating system and want it to be C:.

Well if there is any other solution simpler than the above I will try the above.
I am still learning how IDE drives works since I previously used only SCSI
drives.

Kaz

Pete Baker wrote:

Hi Kaz

It's a little difficult to follow but if I'm decoding correctly.... you had
an XP installation on Disk0 on Channel #1 and then you installed XP on Disk1
also when connected to Channel #1...
That might be the source of the problem... it may be that both installations
are 'pointing' to Channel #1... as you seem to have indicated in your final
summing up.

There may be an easier solution than this, which another poster could
supply, but you could try a repair install.... booting from the XP CD with
both SATA drives connected (or maybe with just Disk 1 connected to
Channel#2) and selecting the installation on Disk 1 for repair.

You'd need to re-install SP1 and any XP updates afterwards though. As I
said there may be an quicker solution but that may be worth a try.
(Hopefully it's not another issue with the controller ;o) )

hope that helps
Pete
----------------
"Honjo" wrote in message
...
I have two SATA drives installed in Asus A7N8X Deluxe mobo and no RAID
is set up. There are OSs(WXPs) installed in Disk0 and Disk1.

My problem is that I can not let an OS in Disk1 boot even if I set boot
priority of Disk1 above Disk0. When I installed the OS in Disk1 I
temporarily replaced Disk0 with Disk1, and after OS installation
completed I restored the original condition being that Disk0 connected
to the channel #1 and Disk1 to the channel #2.

I am wondering if I should have just disconnected Disk0 and then
installed OS in Disk1 while leaving Disk1 connected to the channel #2.

Could anyone shed light on the above?

Kaz Honjo

Hi Kaz

The problem has almost certainly occurred because you switched channels and
removed Disk 0.

I'm not sure that my suggested solution will help though. I had envisaged
that you wanted a dual-boot with one XP on 'C:' and another on 'D:' (I
should point out here that my experience with dual-boot is somewhat limited)

Someone else has suggested on this thread that you switch the Boot device
order in BIOS before a new installation on the second HD. If you did this
then the repair option, or even better a new install, you should get your
desired result. Then to boot to either installation you would switch, in
BIOS, to the appropriate device. I think that would be a better choice than
disconnecting drives before repair. I certainly think it's worth trying.
I'm not sure how the 2 instances of XP will interact with the other drive
though.

hope some of that helps
Pete
----------------




"Honjo" wrote in message
...
Hi Pete

You decoded it correctly. So you agree to my reasoning why WXP in Disk1
does
not boot. If repair installation is done as you suggested I think the
drive
name of WXP in Disk1 becomes something other than C: because C: would be
taken
by the WXP in Disk0. I would think that if a repair installation of WXP is
carried out while Disk0 is temporarily disconnected, then C: will be
assigned to
the WXP drive in Disk1 being connected to the channel #2. I am particular
about
a drive name of operating system and want it to be C:.

Well if there is any other solution simpler than the above I will try the
above.
I am still learning how IDE drives works since I previously used only SCSI
drives.

Kaz

Pete Baker wrote:

Hi Kaz

It's a little difficult to follow but if I'm decoding correctly.... you
had
an XP installation on Disk0 on Channel #1 and then you installed XP on
Disk1
also when connected to Channel #1...
That might be the source of the problem... it may be that both
installations
are 'pointing' to Channel #1... as you seem to have indicated in your
final
summing up.

There may be an easier solution than this, which another poster could
supply, but you could try a repair install.... booting from the XP CD
with
both SATA drives connected (or maybe with just Disk 1 connected to
Channel#2) and selecting the installation on Disk 1 for repair.

You'd need to re-install SP1 and any XP updates afterwards though. As I
said there may be an quicker solution but that may be worth a try.
(Hopefully it's not another issue with the controller ;o) )

hope that helps
Pete
----------------
"Honjo" wrote in message
...
I have two SATA drives installed in Asus A7N8X Deluxe mobo and no RAID
is set up. There are OSs(WXPs) installed in Disk0 and Disk1.

My problem is that I can not let an OS in Disk1 boot even if I set
boot
priority of Disk1 above Disk0. When I installed the OS in Disk1 I
temporarily replaced Disk0 with Disk1, and after OS installation
completed I restored the original condition being that Disk0 connected
to the channel #1 and Disk1 to the channel #2.

I am wondering if I should have just disconnected Disk0 and then
installed OS in Disk1 while leaving Disk1 connected to the channel #2.

Could anyone shed light on the above?

Kaz Honjo

Hello Pearson,

I would think the drive name will become non-C: if WXP is installed in either
way. As a matter of fact your second suggestion is one of those I tried and
noticed the drive name was not going to be C: so I aborted installation.

Kaz Honjo

Pearson Peng wrote:

Hello Kaz,

Thanks for using Microsoft News Group! Thanks for Alvin and Pete's posts.

To install Windows XP on your Disk 1, I suggest you do not replace Disk 0
with Disk 1. Just connect Disk 0 to channel #1, and connect Disk 1 to
channel #2. Boot with the XP CD and install XP on the Disk 1. During the
installation, you will be prompted to choose drive to install. Make sure to
choose Disk 1. You won't be able to pull disk 0 and if it fails, then XP on
disk 1 will not boot (without a repair).

If you don't want to multi-boot like above, I suggest you switch boot
devices in BIOS. Still connect Disk 0 to channel #1, and connect Disk 1 to
channel #2. After you switch boot devices in BIOS to the disk 1, then you
can install the second XP on the disk 1.

Have a great week!

Pearson Peng,
Microsoft Online Support
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Pete

The point is I want OS drive name be always C:. If I accept whatever the drive
name assigned to, then I would not have the present problem. I would not think
other poster's suggestion does not solve non-C: drive problem.

Kaz

Pete Baker wrote:

Hi Kaz

The problem has almost certainly occurred because you switched channels and
removed Disk 0.

I'm not sure that my suggested solution will help though. I had envisaged
that you wanted a dual-boot with one XP on 'C:' and another on 'D:' (I
should point out here that my experience with dual-boot is somewhat limited)

Someone else has suggested on this thread that you switch the Boot device
order in BIOS before a new installation on the second HD. If you did this
then the repair option, or even better a new install, you should get your
desired result. Then to boot to either installation you would switch, in
BIOS, to the appropriate device. I think that would be a better choice than
disconnecting drives before repair. I certainly think it's worth trying.
I'm not sure how the 2 instances of XP will interact with the other drive
though.

hope some of that helps
Pete
----------------

"Honjo" wrote in message
...
Hi Pete

You decoded it correctly. So you agree to my reasoning why WXP in Disk1
does
not boot. If repair installation is done as you suggested I think the
drive
name of WXP in Disk1 becomes something other than C: because C: would be
taken
by the WXP in Disk0. I would think that if a repair installation of WXP is
carried out while Disk0 is temporarily disconnected, then C: will be
assigned to
the WXP drive in Disk1 being connected to the channel #2. I am particular
about
a drive name of operating system and want it to be C:.

Well if there is any other solution simpler than the above I will try the
above.
I am still learning how IDE drives works since I previously used only SCSI
drives.

Kaz

Pete Baker wrote:

Hi Kaz

It's a little difficult to follow but if I'm decoding correctly.... you
had
an XP installation on Disk0 on Channel #1 and then you installed XP on
Disk1
also when connected to Channel #1...
That might be the source of the problem... it may be that both
installations
are 'pointing' to Channel #1... as you seem to have indicated in your
final
summing up.

There may be an easier solution than this, which another poster could
supply, but you could try a repair install.... booting from the XP CD
with
both SATA drives connected (or maybe with just Disk 1 connected to
Channel#2) and selecting the installation on Disk 1 for repair.

You'd need to re-install SP1 and any XP updates afterwards though. As I
said there may be an quicker solution but that may be worth a try.
(Hopefully it's not another issue with the controller ;o) )

hope that helps
Pete
----------------
"Honjo" wrote in message
...
I have two SATA drives installed in Asus A7N8X Deluxe mobo and no RAID
is set up. There are OSs(WXPs) installed in Disk0 and Disk1.

My problem is that I can not let an OS in Disk1 boot even if I set
boot
priority of Disk1 above Disk0. When I installed the OS in Disk1 I
temporarily replaced Disk0 with Disk1, and after OS installation
completed I restored the original condition being that Disk0 connected
to the channel #1 and Disk1 to the channel #2.

I am wondering if I should have just disconnected Disk0 and then
installed OS in Disk1 while leaving Disk1 connected to the channel #2.

Could anyone shed light on the above?

Kaz Honjo

If you always want drive letter to be C: , I think you first have to install
XP on channel1:disk0, remove disk0 and install XP on channel2:disk1 .
Thus I suppose it wouldn't see any disk before it in the drive chain (and so
_maybe_ get letter C....
(remember DOS and w9x?, 1st disk/primary patition=C, 2nd disk/prim.part.=D:,
1st disk/ext.part/log.drive_x=E: F: etc..., 2nd
drive/ext.part/log.drive=...... )

I can't try, haven't got a modern enough computer with SATA drives.....


--
Most of my answers are learned on ms.public.xxx.xxx
Helsinki, Finland (remove spam_)




"Honjo" kirjoitti viestissä
...
Hi Pete

The point is I want OS drive name be always C:. If I accept whatever the
drive
name assigned to, then I would not have the present problem. I would not
think
other poster's suggestion does not solve non-C: drive problem.

Kaz

Pete Baker wrote:

Hi Kaz

The problem has almost certainly occurred because you switched channels
and
removed Disk 0.

I'm not sure that my suggested solution will help though. I had
envisaged
that you wanted a dual-boot with one XP on 'C:' and another on 'D:'
(I
should point out here that my experience with dual-boot is somewhat
limited)

Someone else has suggested on this thread that you switch the Boot
device
order in BIOS before a new installation on the second HD. If you did
this
then the repair option, or even better a new install, you should get
your
desired result. Then to boot to either installation you would switch,
in
BIOS, to the appropriate device. I think that would be a better choice
than
disconnecting drives before repair. I certainly think it's worth
trying.
I'm not sure how the 2 instances of XP will interact with the other
drive
though.

hope some of that helps
Pete
----------------

"Honjo" wrote in message
...
Hi Pete

You decoded it correctly. So you agree to my reasoning why WXP in
Disk1
does
not boot. If repair installation is done as you suggested I think the
drive
name of WXP in Disk1 becomes something other than C: because C: would
be
taken
by the WXP in Disk0. I would think that if a repair installation of
WXP is
carried out while Disk0 is temporarily disconnected, then C: will be
assigned to
the WXP drive in Disk1 being connected to the channel #2. I am
particular
about
a drive name of operating system and want it to be C:.

Well if there is any other solution simpler than the above I will try
the
above.
I am still learning how IDE drives works since I previously used only
SCSI
drives.

Kaz

Pete Baker wrote:

Hi Kaz

It's a little difficult to follow but if I'm decoding correctly....
you
had
an XP installation on Disk0 on Channel #1 and then you installed XP
on
Disk1
also when connected to Channel #1...
That might be the source of the problem... it may be that both
installations
are 'pointing' to Channel #1... as you seem to have indicated in
your
final
summing up.

There may be an easier solution than this, which another poster
could
supply, but you could try a repair install.... booting from the XP
CD
with
both SATA drives connected (or maybe with just Disk 1 connected to
Channel#2) and selecting the installation on Disk 1 for repair.

You'd need to re-install SP1 and any XP updates afterwards though.
As I
said there may be an quicker solution but that may be worth a try.
(Hopefully it's not another issue with the controller ;o) )

hope that helps
Pete
----------------
"Honjo" wrote in message
...
I have two SATA drives installed in Asus A7N8X Deluxe mobo and no
RAID
is set up. There are OSs(WXPs) installed in Disk0 and Disk1.

My problem is that I can not let an OS in Disk1 boot even if I set
boot
priority of Disk1 above Disk0. When I installed the OS in Disk1 I
temporarily replaced Disk0 with Disk1, and after OS installation
completed I restored the original condition being that Disk0
connected
to the channel #1 and Disk1 to the channel #2.

I am wondering if I should have just disconnected Disk0 and then
installed OS in Disk1 while leaving Disk1 connected to the channel
#2.

Could anyone shed light on the above?

Kaz Honjo

Hi Thomas

That is essentially how I installed WXP as I described in my original post and
an assigned drive name became C:. Before installing WXP I connected Disk1 to the
channel #1 or where Disk0 was connected. I once thought this is the cause of my
present problem but it does not seem to bo so because the WXP installed in Disk1
boots fine even it is connected to the channel #2 if Disk0 is disconnected.

Kaz Honjo

Thomas Wendell wrote:

If you always want drive letter to be C: , I think you first have to install
XP on channel1:disk0, remove disk0 and install XP on channel2:disk1 .
Thus I suppose it wouldn't see any disk before it in the drive chain (and so
_maybe_ get letter C....
(remember DOS and w9x?, 1st disk/primary patition=C, 2nd disk/prim.part.=D:,
1st disk/ext.part/log.drive_x=E: F: etc..., 2nd
drive/ext.part/log.drive=...... )

I can't try, haven't got a modern enough computer with SATA drives.....

--
Most of my answers are learned on ms.public.xxx.xxx
Helsinki, Finland (remove spam_)

"Honjo" kirjoitti viestissä


...
Hi Pete

The point is I want OS drive name be always C:. If I accept whatever the
drive
name assigned to, then I would not have the present problem. I would not
think
other poster's suggestion does not solve non-C: drive problem.

Kaz

Pete Baker wrote:

Hi Kaz

The problem has almost certainly occurred because you switched channels
and
removed Disk 0.

I'm not sure that my suggested solution will help though. I had
envisaged
that you wanted a dual-boot with one XP on 'C:' and another on 'D:'
(I
should point out here that my experience with dual-boot is somewhat
limited)

Someone else has suggested on this thread that you switch the Boot
device
order in BIOS before a new installation on the second HD. If you did
this
then the repair option, or even better a new install, you should get
your
desired result. Then to boot to either installation you would switch,
in
BIOS, to the appropriate device. I think that would be a better choice
than
disconnecting drives before repair. I certainly think it's worth
trying.
I'm not sure how the 2 instances of XP will interact with the other
drive
though.

hope some of that helps
Pete
----------------

"Honjo" wrote in message
...
Hi Pete

You decoded it correctly. So you agree to my reasoning why WXP in
Disk1
does
not boot. If repair installation is done as you suggested I think the
drive
name of WXP in Disk1 becomes something other than C: because C: would
be
taken
by the WXP in Disk0. I would think that if a repair installation of
WXP is
carried out while Disk0 is temporarily disconnected, then C: will be
assigned to
the WXP drive in Disk1 being connected to the channel #2. I am
particular
about
a drive name of operating system and want it to be C:.

Well if there is any other solution simpler than the above I will try
the
above.
I am still learning how IDE drives works since I previously used only
SCSI
drives.

Kaz

Pete Baker wrote:

Hi Kaz

It's a little difficult to follow but if I'm decoding correctly....
you
had
an XP installation on Disk0 on Channel #1 and then you installed XP
on
Disk1
also when connected to Channel #1...
That might be the source of the problem... it may be that both
installations
are 'pointing' to Channel #1... as you seem to have indicated in
your
final
summing up.

There may be an easier solution than this, which another poster
could
supply, but you could try a repair install.... booting from the XP
CD
with
both SATA drives connected (or maybe with just Disk 1 connected to
Channel#2) and selecting the installation on Disk 1 for repair.

You'd need to re-install SP1 and any XP updates afterwards though.
As I
said there may be an quicker solution but that may be worth a try.
(Hopefully it's not another issue with the controller ;o) )

hope that helps
Pete
----------------
"Honjo" wrote in message
...
I have two SATA drives installed in Asus A7N8X Deluxe mobo and no
RAID
is set up. There are OSs(WXPs) installed in Disk0 and Disk1.

My problem is that I can not let an OS in Disk1 boot even if I set
boot
priority of Disk1 above Disk0. When I installed the OS in Disk1 I
temporarily replaced Disk0 with Disk1, and after OS installation
completed I restored the original condition being that Disk0
connected
to the channel #1 and Disk1 to the channel #2.

I am wondering if I should have just disconnected Disk0 and then
installed OS in Disk1 while leaving Disk1 connected to the channel
#2.

Could anyone shed light on the above?

Kaz Honjo

Hi Pete and everyone:

This is an update of the problem situation: I just unplugged Disk0 and started
the computer then WXP in Disk1 booted fine. This appears to mean WXP has been
installed normally in Disk1. Another word if boot priority is set higher for Disk1
than Disk0 then WXP installed in Disk1 should boot. Well, is this SATA controller
issue again? I noticed a newer version driver up at SiI website recently. Maybe I
should bug Asus again.

Kaz Honjo

Honjo wrote:

Hi Pete

The point is I want OS drive name be always C:. If I accept whatever the drive
name assigned to, then I would not have the present problem. I would not think
other poster's suggestion does not solve non-C: drive problem.

Kaz

Pete Baker wrote:

Hi Kaz

The problem has almost certainly occurred because you switched channels and
removed Disk 0.

I'm not sure that my suggested solution will help though. I had envisaged
that you wanted a dual-boot with one XP on 'C:' and another on 'D:' (I
should point out here that my experience with dual-boot is somewhat limited)

Someone else has suggested on this thread that you switch the Boot device
order in BIOS before a new installation on the second HD. If you did this
then the repair option, or even better a new install, you should get your
desired result. Then to boot to either installation you would switch, in
BIOS, to the appropriate device. I think that would be a better choice than
disconnecting drives before repair. I certainly think it's worth trying.
I'm not sure how the 2 instances of XP will interact with the other drive
though.

hope some of that helps
Pete
----------------

"Honjo" wrote in message
...
Hi Pete

You decoded it correctly. So you agree to my reasoning why WXP in Disk1
does
not boot. If repair installation is done as you suggested I think the
drive
name of WXP in Disk1 becomes something other than C: because C: would be
taken
by the WXP in Disk0. I would think that if a repair installation of WXP is
carried out while Disk0 is temporarily disconnected, then C: will be
assigned to
the WXP drive in Disk1 being connected to the channel #2. I am particular
about
a drive name of operating system and want it to be C:.

Well if there is any other solution simpler than the above I will try the
above.
I am still learning how IDE drives works since I previously used only SCSI
drives.

Kaz

Pete Baker wrote:

Hi Kaz

It's a little difficult to follow but if I'm decoding correctly.... you
had
an XP installation on Disk0 on Channel #1 and then you installed XP on
Disk1
also when connected to Channel #1...
That might be the source of the problem... it may be that both
installations
are 'pointing' to Channel #1... as you seem to have indicated in your
final
summing up.

There may be an easier solution than this, which another poster could
supply, but you could try a repair install.... booting from the XP CD
with
both SATA drives connected (or maybe with just Disk 1 connected to
Channel#2) and selecting the installation on Disk 1 for repair.

You'd need to re-install SP1 and any XP updates afterwards though. As I
said there may be an quicker solution but that may be worth a try.
(Hopefully it's not another issue with the controller ;o) )

hope that helps
Pete
----------------
"Honjo" wrote in message
...
I have two SATA drives installed in Asus A7N8X Deluxe mobo and no RAID
is set up. There are OSs(WXPs) installed in Disk0 and Disk1.

My problem is that I can not let an OS in Disk1 boot even if I set
boot
priority of Disk1 above Disk0. When I installed the OS in Disk1 I
temporarily replaced Disk0 with Disk1, and after OS installation
completed I restored the original condition being that Disk0 connected
to the channel #1 and Disk1 to the channel #2.

I am wondering if I should have just disconnected Disk0 and then
installed OS in Disk1 while leaving Disk1 connected to the channel #2.

Could anyone shed light on the above?

Kaz Honjo

I have 3 operating systems on my computer. No matter which one I boot into,
it is seen as drive C:.

I use a 3rd party boot manager program to do this. You may want to look into
the same.

"Honjo" wrote in message
...
I have two SATA drives installed in Asus A7N8X Deluxe mobo and no RAID
is set up. There are OSs(WXPs) installed in Disk0 and Disk1.

My problem is that I can not let an OS in Disk1 boot even if I set boot
priority of Disk1 above Disk0. When I installed the OS in Disk1 I
temporarily replaced Disk0 with Disk1, and after OS installation
completed I restored the original condition being that Disk0 connected
to the channel #1 and Disk1 to the channel #2.

I am wondering if I should have just disconnected Disk0 and then
installed OS in Disk1 while leaving Disk1 connected to the channel #2.

Could anyone shed light on the above?

Kaz Honjo

Hi Kaz

I don't believe it is a SATA controller issue. As 'Crusty' has suggested
elsewhere on this thread, you might get a better and more stable result from
a third party boot manager.

Pete
------------
"Honjo" wrote in message
...
Hi Pete and everyone:

This is an update of the problem situation: I just unplugged Disk0 and
started
the computer then WXP in Disk1 booted fine. This appears to mean WXP has
been
installed normally in Disk1. Another word if boot priority is set higher
for Disk1
than Disk0 then WXP installed in Disk1 should boot. Well, is this SATA
controller
issue again? I noticed a newer version driver up at SiI website recently.
Maybe I
should bug Asus again.

Kaz Honjo

Honjo wrote:

Hi Pete

The point is I want OS drive name be always C:. If I accept whatever the
drive
name assigned to, then I would not have the present problem. I would not
think
other poster's suggestion does not solve non-C: drive problem.

Kaz

Pete Baker wrote:

Hi Kaz

The problem has almost certainly occurred because you switched
channels and
removed Disk 0.

I'm not sure that my suggested solution will help though. I had
envisaged
that you wanted a dual-boot with one XP on 'C:' and another on 'D:'
(I
should point out here that my experience with dual-boot is somewhat
limited)

Someone else has suggested on this thread that you switch the Boot
device
order in BIOS before a new installation on the second HD. If you did
this
then the repair option, or even better a new install, you should get
your
desired result. Then to boot to either installation you would switch,
in
BIOS, to the appropriate device. I think that would be a better
choice than
disconnecting drives before repair. I certainly think it's worth
trying.
I'm not sure how the 2 instances of XP will interact with the other
drive
though.

hope some of that helps
Pete
----------------

"Honjo" wrote in message
...
Hi Pete

You decoded it correctly. So you agree to my reasoning why WXP in
Disk1
does
not boot. If repair installation is done as you suggested I think
the
drive
name of WXP in Disk1 becomes something other than C: because C:
would be
taken
by the WXP in Disk0. I would think that if a repair installation of
WXP is
carried out while Disk0 is temporarily disconnected, then C: will be
assigned to
the WXP drive in Disk1 being connected to the channel #2. I am
particular
about
a drive name of operating system and want it to be C:.

Well if there is any other solution simpler than the above I will
try the
above.
I am still learning how IDE drives works since I previously used
only SCSI
drives.

Kaz

Pete Baker wrote:

Hi Kaz

It's a little difficult to follow but if I'm decoding
correctly.... you
had
an XP installation on Disk0 on Channel #1 and then you installed
XP on
Disk1
also when connected to Channel #1...
That might be the source of the problem... it may be that both
installations
are 'pointing' to Channel #1... as you seem to have indicated in
your
final
summing up.

There may be an easier solution than this, which another poster
could
supply, but you could try a repair install.... booting from the XP
CD
with
both SATA drives connected (or maybe with just Disk 1 connected to
Channel#2) and selecting the installation on Disk 1 for repair.

You'd need to re-install SP1 and any XP updates afterwards though.
As I
said there may be an quicker solution but that may be worth a try.
(Hopefully it's not another issue with the controller ;o) )

hope that helps
Pete
----------------
"Honjo" wrote in message
...
I have two SATA drives installed in Asus A7N8X Deluxe mobo and
no RAID
is set up. There are OSs(WXPs) installed in Disk0 and Disk1.

My problem is that I can not let an OS in Disk1 boot even if I
set
boot
priority of Disk1 above Disk0. When I installed the OS in Disk1
I
temporarily replaced Disk0 with Disk1, and after OS installation
completed I restored the original condition being that Disk0
connected
to the channel #1 and Disk1 to the channel #2.

I am wondering if I should have just disconnected Disk0 and then
installed OS in Disk1 while leaving Disk1 connected to the
channel #2.

Could anyone shed light on the above?

Kaz Honjo

Hi Pete

I am aware of third party boot managers but I do not want to use those softwares
if at all possible. I have been multi-booting 6 OSs installed in three physical
drives without using any such boot manager software. This is with SCSI HD
system and I am atempting to realize something similar to it.

I have installed three OSs in Disk0 and they works as I wanted. Then I attempted
to install forth OS in Disk1 and encountered difficulty. I think I managed to
install it ok but the present problem is how to switch OS accross two physical
drives.

The problem symptom as stated in my original post indicates that boot priority
setting of HD within HDs is not effective. Is it because the HDs are SATA and
it is effective only for conventional IDE HDs? Is this by design or bug? Anyone
know the answer?

Kaz Honjo

Pete Baker wrote:

Hi Kaz

I don't believe it is a SATA controller issue. As 'Crusty' has suggested
elsewhere on this thread, you might get a better and more stable result from
a third party boot manager.

Pete
------------
"Honjo" wrote in message
...
Hi Pete and everyone:

This is an update of the problem situation: I just unplugged Disk0 and
started
the computer then WXP in Disk1 booted fine. This appears to mean WXP has
been
installed normally in Disk1. Another word if boot priority is set higher
for Disk1
than Disk0 then WXP installed in Disk1 should boot. Well, is this SATA
controller
issue again? I noticed a newer version driver up at SiI website recently.
Maybe I
should bug Asus again.

Kaz Honjo

Honjo wrote:

Hi Pete

The point is I want OS drive name be always C:. If I accept whatever the
drive
name assigned to, then I would not have the present problem. I would not
think
other poster's suggestion does not solve non-C: drive problem.

Kaz

Pete Baker wrote:

Hi Kaz

The problem has almost certainly occurred because you switched
channels and
removed Disk 0.

I'm not sure that my suggested solution will help though. I had
envisaged
that you wanted a dual-boot with one XP on 'C:' and another on 'D:'
(I
should point out here that my experience with dual-boot is somewhat
limited)

Someone else has suggested on this thread that you switch the Boot
device
order in BIOS before a new installation on the second HD. If you did
this
then the repair option, or even better a new install, you should get
your
desired result. Then to boot to either installation you would switch,
in
BIOS, to the appropriate device. I think that would be a better
choice than
disconnecting drives before repair. I certainly think it's worth
trying.
I'm not sure how the 2 instances of XP will interact with the other
drive
though.

hope some of that helps
Pete
----------------

"Honjo" wrote in message
...
Hi Pete

You decoded it correctly. So you agree to my reasoning why WXP in
Disk1
does
not boot. If repair installation is done as you suggested I think
the
drive
name of WXP in Disk1 becomes something other than C: because C:
would be
taken
by the WXP in Disk0. I would think that if a repair installation of
WXP is
carried out while Disk0 is temporarily disconnected, then C: will be
assigned to
the WXP drive in Disk1 being connected to the channel #2. I am
particular
about
a drive name of operating system and want it to be C:.

Well if there is any other solution simpler than the above I will
try the
above.
I am still learning how IDE drives works since I previously used
only SCSI
drives.

Kaz

Pete Baker wrote:

Hi Kaz

It's a little difficult to follow but if I'm decoding
correctly.... you
had
an XP installation on Disk0 on Channel #1 and then you installed
XP on
Disk1
also when connected to Channel #1...
That might be the source of the problem... it may be that both
installations
are 'pointing' to Channel #1... as you seem to have indicated in
your
final
summing up.

There may be an easier solution than this, which another poster
could
supply, but you could try a repair install.... booting from the XP
CD
with
both SATA drives connected (or maybe with just Disk 1 connected to
Channel#2) and selecting the installation on Disk 1 for repair.

You'd need to re-install SP1 and any XP updates afterwards though.
As I
said there may be an quicker solution but that may be worth a try.
(Hopefully it's not another issue with the controller ;o) )

hope that helps
Pete
----------------
"Honjo" wrote in message
...
I have two SATA drives installed in Asus A7N8X Deluxe mobo and
no RAID
is set up. There are OSs(WXPs) installed in Disk0 and Disk1.

My problem is that I can not let an OS in Disk1 boot even if I
set
boot
priority of Disk1 above Disk0. When I installed the OS in Disk1
I
temporarily replaced Disk0 with Disk1, and after OS installation
completed I restored the original condition being that Disk0
connected
to the channel #1 and Disk1 to the channel #2.

I am wondering if I should have just disconnected Disk0 and then
installed OS in Disk1 while leaving Disk1 connected to the
channel #2.

Could anyone shed light on the above?

Kaz Honjo