Why second HD is Disk 0?

[Tod]

I've got Win XP (home) on this computer.
My OS is on an 80GB HD set as master on the primary motherboard controller.
I've also got a 200GB storage drive running off an add-on controller.
(DVD & burner on motherboard secondary controller)
In Win XP, disk management the 200GB is listed as Disk 0
and the 80GB as Disk 1
I would like to change the 80GB to Disk 0.
Ideas please?

 

[T. Waters]

Tod, please learn the difference between multiposting (what you did) and
cross-posting (what you should have done). Now you are going to collect
responses in several separate newsgroups.

 

[Steve N.]

I've got Win XP (home) on this computer.
My OS is on an 80GB HD set as master on the primary motherboard controller.
I've also got a 200GB storage drive running off an add-on controller.
(DVD & burner on motherboard secondary controller)
In Win XP, disk management the 200GB is listed as Disk 0
and the 80GB as Disk 1
I would like to change the 80GB to Disk 0.
Ideas please?

This is a motherboard/BIOS/add-on card issue, not really a Windows
issue. Windows can only report what it sees from the hardware in this
case. Why the BIOS has elected to enumerate the add-on controller drive
as it did is a question for the Motherboard manufacturer and the add-on
controller manufacturer but I would start by looking in BIOS for any
settings that might effect which IDE controller the system sees first.

Steve

 

[Guest]

The xp hard drive is connected to 2nd plug connector on the board,
the 200mb is on 1st,switch the two connections.

 

[Winux P]

Hi Tod,

Is the add-on controller a Silicon Graphics (Sil) card? If so, and you can't
set the boot disk order from the BIOS you **may** have to put both your
disks in the Sil Card and your ROM drives in the mother board. Then from the
Sil card assign the disk orders, making sure your system disk is assigned 0.
If your add-on controller is a Promise Technology one make sure your 80GB is
in IDE slot 0 (in which case your 200GB can be anywhere that will take it).
Look in device manager to see what kind of add-on you have.

Hope this helps.

Regards,
Winux P.

| I've got Win XP (home) on this computer.
| My OS is on an 80GB HD set as master on the primary motherboard
controller.
| I've also got a 200GB storage drive running off an add-on controller.
| (DVD & burner on motherboard secondary controller)
| In Win XP, disk management the 200GB is listed as Disk 0
| and the 80GB as Disk 1
| I would like to change the 80GB to Disk 0.
| Ideas please?
|
|
|

 

[Winux P]

Addition: "...If your add-on controller is a Promise Technology one make
sure your 80GB is
in IDE slot 0..." IDE slot 0 on your mother board that is.

|
| Hi Tod,
|
| Is the add-on controller a Silicon Graphics (Sil) card? If so, and you
can't
| set the boot disk order from the BIOS you **may** have to put both your
| disks in the Sil Card and your ROM drives in the mother board. Then from
the
| Sil card assign the disk orders, making sure your system disk is assigned
0.
| If your add-on controller is a Promise Technology one make sure your 80GB
is
| in IDE slot 0 (in which case your 200GB can be anywhere that will take
it).
| Look in device manager to see what kind of add-on you have.
|
| Hope this helps.
|
| Regards,
| Winux P.
|
| || I've got Win XP (home) on this computer.
|| My OS is on an 80GB HD set as master on the primary motherboard
| controller.
|| I've also got a 200GB storage drive running off an add-on controller.
|| (DVD & burner on motherboard secondary controller)
|| In Win XP, disk management the 200GB is listed as Disk 0
|| and the 80GB as Disk 1
|| I would like to change the 80GB to Disk 0.
|| Ideas please?
||
||
||
|
|

 

[Kelly]

Cross posting in no better.

--
In memory of our dear friend, MVP Alex Nichol: http://www.dts-l.org/

All the Best,
Kelly (MS-MVP)

Troubleshooting Windows XP
http://www.kellys-korner-xp.com

 

[Tod]

It is the Sil 680 ATA133 PCI controller.

 

[ByTor]

Hi Tod,

Is the add-on controller a Silicon Graphics (Sil) card? If so, and you can't
set the boot disk order from the BIOS you **may** have to put both your
disks in the Sil Card and your ROM drives in the mother board. Then from the
Sil card assign the disk orders, making sure your system disk is assigned 0.
If your add-on controller is a Promise Technology one make sure your 80GB is
in IDE slot 0 (in which case your 200GB can be anywhere that will take it).
Look in device manager to see what kind of add-on you have.

Hope this helps.

Regards,
Winux P.

.................... ;0)

 

[Winux P]

G'Day ByTor

Think I've had a case of Dejavu....;~P

Hi Tod,

You can try this out if you please, you may, I'm not sure myself may have to
rebuild WinXP in some way (I did in my case).

Place both hard disks into the Sil 0680, 80GB in slot 0 and 200GB into slot
1. Put your ROMs into the mother board. If you can get away with not having
any slave drives do so. If you don't have any slaves, boot up into your BIOS
and set none to slave drives to make boot up abit quicker. When the Sil 0680
searches for disks press F3 and from the controller configuration utility
make sure or set the 80GB to the first disk. You may need to do a
re-install, that should do it.

Hope it all works out for you.

Regards,
Winux P.




| In article <[email protected]>, (e-mail address removed),
| Winux P says...
|
| >
| > Hi Tod,
| >
| > Is the add-on controller a Silicon Graphics (Sil) card? If so, and you
can't
| > set the boot disk order from the BIOS you **may** have to put both your
| > disks in the Sil Card and your ROM drives in the mother board. Then from
the
| > Sil card assign the disk orders, making sure your system disk is
assigned 0.
| > If your add-on controller is a Promise Technology one make sure your
80GB is
| > in IDE slot 0 (in which case your 200GB can be anywhere that will take
it).
| > Look in device manager to see what kind of add-on you have.
| >
| > Hope this helps.
| >
| > Regards,
| > Winux P.
|
| ................... ;0)
|

 

[ByTor]

When the Sil 0680 searches for disks press F3 and from the controller
configuration utility make sure or set the 80GB to the first disk.

I've been meaning to ask you something about this F3 business......I've
never needed or tried to access the BIOS on the card, I take it that
access to it is **only** allowed when HD's are attached to it??

I'm asking because I can't access the BIOS on the card....I'm assuming
it's because there are no HD's on it and after it detects all my Roms it
states the BIOS is disabled............Which I understand as the BIOS is
not needed for ROMS and I don't use it for **main** booting.......Oh
well it's no biggie I was curious though if you were able to access it
with no drives attached when you had your *scenario* a bit
back............

 

[Winux P]

Hi ByTor,

Funny enough I've never tried to access the Card BIOS either until I changed
the configuration we spoke about before. Even though the proposed system
disk was in slot 0 and the proposed data disk in slot 1, the card kept
insisting the larger data disk be disk 0 hence the C: drive. Then I started
pressing F3 on boot ups and was able to assign what I wanted to be disk 0
and so on. That's all the functionality the card bios gave me. Previously
when I had ROMs in there it didn't occur to me to press F3.... I don't know.

Regards,
Winux P.

: In article <[email protected]>, (e-mail address removed),
: Winux P says...
:
: > When the Sil 0680 searches for disks press F3 and from the controller
: > configuration utility make sure or set the 80GB to the first disk.
:
: I've been meaning to ask you something about this F3 business......I've
: never needed or tried to access the BIOS on the card, I take it that
: access to it is **only** allowed when HD's are attached to it??
:
: I'm asking because I can't access the BIOS on the card....I'm assuming
: it's because there are no HD's on it and after it detects all my Roms it
: states the BIOS is disabled............Which I understand as the BIOS is
: not needed for ROMS and I don't use it for **main** booting.......Oh
: well it's no biggie I was curious though if you were able to access it
: with no drives attached when you had your *scenario* a bit
: back............
:

 

[ByTor]

Hi ByTor,

Funny enough I've never tried to access the Card BIOS either until I changed
the configuration we spoke about before. Even though the proposed system
disk was in slot 0 and the proposed data disk in slot 1, the card kept
insisting the larger data disk be disk 0 hence the C: drive. Then I started
pressing F3 on boot ups and was able to assign what I wanted to be disk 0
and so on. That's all the functionality the card bios gave me. Previously
when I had ROMs in there it didn't occur to me to press F3.... I don't know.

Regards,
Winux P.

Thanks..........I was just curious. I mean the card was meant to take
over because at the time the assumption was made that people would buy
larger drives that the MB's did not support, hence they made it easier
for the card to taker over assignment thinking people wouldn't keep
their old drives.....Helluva an assumption.........Oh well, I'll never
buy a Sil again though.....Well maybe, I mean they work **great** with
the ROMS though....better than the promises.

Thanks buddy........ ;0)