Archived from groups: microsoft.public.windowsxp.hardware (More info?)
I've come upon a paradoxical situation. Looking for ideas.
Win XP Pro SP1 system. Dell Dimension XPS series desktop
with a Promise Technologies DMA Ultra/100 (plain or TX2)
controller card. System drive configuration
(MB=motherboard, C=controller card):
MB IDE primary: no drives
MB IDE secondary: CD-RW (master), Zip 250 (slave)
C IDE primary: hard disk drive with WinXP Pro
C IDE secondary: no drives
When system boots, BIOS seems to scan motherboard first
and then controller card. It assigns Zip 250 as "disk 0"
as seen in Computer Management. Hard drive is "disk 1".
(If I disconnect the Zip 250 drive, the hard drive becomes
disk 0. If I reconnect the Zip 250, then the Zip drive
again becomes disk 0.)
Partition Commander software package requires that the
boot drive be disk 0. It cannot work with the boot drive
as another disk according to V-com tech support.
So, I am looking for a way to get the hard drive
recognized as disk 0.
I could stop using the HDD Controller card and connect the
hard drive to the MB primary port. Undesirable due to
higher performance from the controller card.
It seems that if I connect the Zip 250 drive to the
controller's secondary IDE channel it will get scanned
after the hard drive and the hard drive would be drive 0.
I have previously had difficulty when connecting an
internal CD-RW drive to the controller card. I've been
told previously in this forum that I should not connect
ATAPI CD-RW drives to the controller - that they should
connect to the MB IDE ports.
Question: Anyone see problems if I try connecting the
internal ATAPI Zip 250 drive to the Promise controller
card?
Thanks.
I've come upon a paradoxical situation. Looking for ideas.
Win XP Pro SP1 system. Dell Dimension XPS series desktop
with a Promise Technologies DMA Ultra/100 (plain or TX2)
controller card. System drive configuration
(MB=motherboard, C=controller card):
MB IDE primary: no drives
MB IDE secondary: CD-RW (master), Zip 250 (slave)
C IDE primary: hard disk drive with WinXP Pro
C IDE secondary: no drives
When system boots, BIOS seems to scan motherboard first
and then controller card. It assigns Zip 250 as "disk 0"
as seen in Computer Management. Hard drive is "disk 1".
(If I disconnect the Zip 250 drive, the hard drive becomes
disk 0. If I reconnect the Zip 250, then the Zip drive
again becomes disk 0.)
Partition Commander software package requires that the
boot drive be disk 0. It cannot work with the boot drive
as another disk according to V-com tech support.
So, I am looking for a way to get the hard drive
recognized as disk 0.
I could stop using the HDD Controller card and connect the
hard drive to the MB primary port. Undesirable due to
higher performance from the controller card.
It seems that if I connect the Zip 250 drive to the
controller's secondary IDE channel it will get scanned
after the hard drive and the hard drive would be drive 0.
I have previously had difficulty when connecting an
internal CD-RW drive to the controller card. I've been
told previously in this forum that I should not connect
ATAPI CD-RW drives to the controller - that they should
connect to the MB IDE ports.
Question: Anyone see problems if I try connecting the
internal ATAPI Zip 250 drive to the Promise controller
card?
Thanks.