Additional hard drive takes disk 0 position

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

I have 2 boxes. 1 was using 2-200 gb hard drives as c and d. I built a new
system where I now have a 1-60 GB drive as my xp system drive. I removed the
200's from my other box and placed them in the new one. Although the drives
are jumpered properly(the bios sees them in the correct order) WinXP boots
with one of the additional 200's as drive 0; 60 is drive 1 and the other 200
is drive 2. I have already booted from the Western Digital Diagnostics floppy
and performed the Full 'write zero's to the drive' procedure on both 200's.
It still however boots with the 1st 200 in drive 0 position.

Why is this happening? How do I get the 60 gb to show as drive 0 and the
demote the 200 to the drive 1 position?

Thanks,

Chris
 
You say the drives are jumpered correctly, yet you don't say exactly "how"
they are jumpered - or connected to the IDE channels. Obviously, something
is "incorrect"!!

Without proper information it is difficult to make a diagnosis.

How are they jumpered?

Which IDE channel is each connected to?

Are you using cable select or setting the drives as master/slave.

Give us enough information to work with.

--

Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
 
Sorry.

60GB Prim IDE master
1st 200GB Prim IDE slave

DVDR Sec IDE Master
2nd 200GB Sec IDE Slave

I say they are jumpered properly because the BIOS IDE configuration shows
them in the EXACT order as listed above. But when widows boots the 60 GB
becomes the Drive 1 and the 1st 200 becomes drive 0.

--
Windows XP
Cable Router
Broadband ISP


Richard Urban said:
You say the drives are jumpered correctly, yet you don't say exactly "how"
they are jumpered - or connected to the IDE channels. Obviously, something
is "incorrect"!!

Without proper information it is difficult to make a diagnosis.

How are they jumpered?

Which IDE channel is each connected to?

Are you using cable select or setting the drives as master/slave.

Give us enough information to work with.

--

Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
Click to expand...
 
Are all the drives connected to on-board IDE channels, or are some connected
to an add-in IDE expander card? If so, this will cause some drive position
anomalies.

Also, on my main computer, as soon as I install the Asus M/B IDE drivers -
the drive positions change, as opposed to the drivers supplied with Windows
XP. This does NOT prevent the operating system from functioning in any way
at all. The different drivers just look at the connected drives from a
different viewpoint.


--

Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

Chris Austin said:
Sorry.

60GB Prim IDE master
1st 200GB Prim IDE slave

DVDR Sec IDE Master
2nd 200GB Sec IDE Slave

I say they are jumpered properly because the BIOS IDE configuration shows
them in the EXACT order as listed above. But when widows boots the 60 GB
becomes the Drive 1 and the 1st 200 becomes drive 0.
Click to expand...
 
Thanks Richard.

They are attached to the 2 IDE channels, prim and sec, on the motherboard. I
am using the default windows ide drivers. So drivers is not the cause.

And I know it does not affect windows, but I am a perfectionist. And seeing
it this way drives me crazy! Why would windows just make up its own mind
instead of using the using proper config that the bios shows?

Is there any way to tell windows that x disk is drive 1 and x disk is drive
0? perhaps through the registry?

Chris
 
I straightened out a computer like yours a couple of years ago. It entailed
putting two new drives in the computer. I then had to install Windows XP
fresh on the new drive. After that, I created the partitions I needed on the
two drives. All partitions and drives were then seen correctly.

End result! It didn't operate any differently than before. I used the two
older drives on other computers, after deleting all partitions and getting
the drives back to "all space unallocated".

--

Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
 
That is exactly how this was installed. The 60GB was already in the system
and I installed windows xp as usual. I used the full 60gb as a System
partition.

Then I took the 2 200's and added them to the configuration. But when I
booted up after installing the 2 200's, one of them took the place of the
60gb as Drive 0. I didn't set it up as drive 0. It booted up that way.That's
why I'm getting so frustrated!

Chris
 
Then I can not believe that your drives are setup, jumpered and connected
(to the onboard IDE channels) as you say. Something is not as you make it
out to be. What have you missed?

--

Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
 
When you move the 2 200GB hard drives, where they already formatted and did
one of already have a booting version of XP on it?
 
Chris Austin said:
Sorry.

60GB Prim IDE master
1st 200GB Prim IDE slave

DVDR Sec IDE Master
2nd 200GB Sec IDE Slave

I say they are jumpered properly because the BIOS IDE configuration shows
them in the EXACT order as listed above. But when widows boots the 60 GB
becomes the Drive 1 and the 1st 200 becomes drive 0.
Click to expand...
Chris, please doublecheck your 1st 200 gig. Make sure it is not still
jumpered as master or cable-select. ( IIRC I have seen a system change its
reading from single master as drive 1 to, after adding hd's, the
multiple-drive master now becoming drive 0.) Nevermind the validity of my
"IIRC-bit"; just assume you are starting from scratch and this is a brand
new task. Remove the 60-gig and 1st 200-gig; jumper the 60-gig as master
"with slave attached", and the 200-gig as slave to the 60g. HTH and that
it brings it to your expectations. I, too, am angered when something merely
has a non-consequential flaw. s
 
Back
Top