SATA & IDE in same computer

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

Guest

Can I install an internal SATA HDD as my system drive and then install an
internal IDE as a slave? Will windows recognize both and operate properly?
It would be done on an ASUS P4P800 MoBo...

Comments?
 
Mike C said:
Can I install an internal SATA HDD as my system drive and then install an
internal IDE as a slave? Will windows recognize both and operate
properly?
It would be done on an ASUS P4P800 MoBo...

Comments?

Yes, you can. If it is a clean install, you may need to specify the SATA
drive as your C: logical drive in the partition dialog of the windows setup.
I have several machines, all but one running Asus motherboards, with IDE and
SATA drives installed.

carl
 
"Slave" denotes the SECOND drive on an IDE header, normally attached to
the middle connector on the IDE cable.
 
Mike C said:
Can I install an internal SATA HDD as my system drive and then install an
internal IDE as a slave? Will windows recognize both and operate
properly?
It would be done on an ASUS P4P800 MoBo...

Comments?


Gerry Cornell said:
Mike / Carl

Set the jumpers for the Sata drive as master and
the jumpers on the IDE drive as slave.
http://www.mysuperpc.com/hdu/jumper_pins.shtml
--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England


Bob I said:
"Slave" denotes the SECOND drive on an IDE header, normally attached to
the middle connector on the IDE cable.


Mike:
As carl has indicated there is no problem installing a SATA and PATA HD in
the same machine. The SATA drive will be connected to one of the
motherboard's SATA connectors and the PATA HD will be connected to one of
the motherboard's IDE connectors.

(Gerry: There is no Master/Slave positions with respect to SATA hard drives)

I assume from your query that the SATA HD will be your boot drive containing
the XP OS and the PATA drive will be a secondary HD for storage or whatever.
Under those circumstances you can connect the PATA drive to either of the
motherboard's Primary or Secondary IDE channels. Since it is not a boot
drive you can connect it as either Master or Slave on either IDE channel.
Again, I'm assuming in all this that you are *not* planning on also
installing the OS on the PATA HD in order to have a multi-boot
configuration. If that *is* your plan, then that would change the
configuration I've indicated.

(Bob: With respect to the OP's PATA drive it is unnecessary that it be
connected as a Slave. Again we're assuming that it will be a non-bootable
drive)

The system should boot to your SATA drive without further ado.
Anna
 
Anna

I dug out my Manual and it confirms what you say.

--

Regards.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Bob I said:
"Slave" denotes the SECOND drive on an IDE header,
normally attached to the middle connector on the IDE cable.


A "Slave" drive is a drive marked "Slave" by a jumper (or
by its position on the IDE cable in the case of Cable Select).
The designation is merely for the IDE channel controller to
differentiate that drive from the other drive on the same
cable/channel, i.e. the "Master". It does NOT imply which
hard drive controls booting. Some BIOSes make the Master
the DEFAULT head of the hard drive boot order, but the user
can manually instruct the BIOS to put any other hard drive at
the head of the hard drive boot order. Beyond that, Master/
Slave has no meaning to the Master Boot Record, the Boot
Sector, the loader, the drivers, or the operating system.

To be explicit, the Slave hard drive can contain the boot files,
i.e. bootini, ntldr, and ntdetect.com, and it can also contain the
operating system that is loaded. There is nothing "secondary"
about the Slave hard drive. The two drives on the same IDE
cable/channel could just as well have been called "#" and "@".

*TimDaniels*
 
That is still not true. A sole hard drive in the computer
can be a Slave hard drive. Re-jumper the Master hard
drive as a Slave and try it.

A hard drive jumpered as Slave can also be put
at the end of the cable while a hard drive jumpered
as Master is at the mid-point. Try it.

Again, "Master" and "Slave" designations are only to
differentiate two hard drives for the IDE channel controller.
Except for the DEFAULT hard drive boot order in the
BIOS (which may be changed by the user) they have no
further meaning.

*TimDaniels*
 
Yes, but it's possible to get this very wrong, so read on. Problems
arise at two levels; BIOS/CMOS setup, and the OS.

The best thing is to remove all drives that could cause ambiguity at
the time the OS is installed:
- have only S-ATA, IDE or SCSI HDs present at install time
- remove all removeable disks, USB devices and card readers

If you don't do this, there is a risk that the installation process
will assign C: to a drive or device other than the boot HD.

There's generally no ambiguity when you attach HDs of the same type,
e.g. multiple IDE HDs, multiple SCSI HDs or multiple S-ATA HDs.

There's also no ambiguity when the first of these HDs has only one
primary partition on it; all other primary partitions should be hidden
by spoofing the partition type byte to something XP doesn't
understand, and most boot managers will provide that facility.

Where things go wrong is where you mix drives of different types.
Optical (CD, DVD) and classic diskette drives are OK at install time,
it's a mix of newer busses such as USB, Firewire, S-ATA and
non-standard removable disk drives such as Zip etc. that can cause
problems. This is because there may be variance between:
- which device BIOS sees as the "boot device" (boot order)
- which order these are enumerated by BIOS
- which order these are enumerated by OS PnP

Generally, the OS has no idea about which drive is the boot device.
Instead, it enumerates devices via PnP, and PnP generally starts with
the equipment list that is passed to it by BIOS.

BIOS may not see USB, Firewire or devices attached via add-on
controllers at all, unless these are set as "legacy devices". For
example, a USB flash drive would normally be expected to be ignored by
BIOS and thus not passed to the OS in the equipment list, but if the
drive is present at boot time and Legacy USB is enabled in CMOS setup,
the flash drive may be passed as part of the list.
As carl has indicated there is no problem installing a SATA and PATA HD in
the same machine.

False. BIOS may handle S-ATA in different ways, in terms of how these
co-exist with IDE, and YMMV on how this is set.

At the one extreme, BIOS may handle S-ATA as additional to IDE, so
that you can use all the S-ATA connectors and all the IDE connectors
at the same time. The downside of this is that the S-ATA are unlikely
to be seen by any OS that doesn't "know" S-ATA.

At the other extreme is to operate S-ATA in "legacy mode" where
logically they are treated as IDE. The mapping is usually...

S-ATA 0 = IDE Primary Master
S-ATA 1 = IDE Primary Slave
S-ATA 2 = IDE Secondary Master
S-ATA 3 = IDE Secondary Slave

....and that obviously means you can't have an S-ATA 0 and an IDE
Primary Master installed at the same time. Less obviously, the
relationship between IDE channels and S-ATA is usualy such that the
presence of anything on an IDE channel knocks out both of the S-ATA
that correspond to that channel. So for instance, this won't work...

S-ATA 0 = boot HD
IDE Primary Slave = second HD
IDE Secondary Master = DVD writer

....because the presence of the HD on the Primary IDE clashes with
S-ATA 0, even though the IDE HD is "Slave" to S-ATA 0. When it's said
that S-ATA has no concept of Master / Slave, this extends to the
inability to co-exist with such IDE overlaying the same "space".

Instead, try...

S-ATA 0 = boot HD
IDE Secondary Master = second HD
IDE Secondary Slave = DVD writer

....or...

S-ATA 0 = boot HD
IDE Secondary Master = DVD writer
IDE Secondary Slave = second HD

....but because BIOS and/or OS PnP may enumerate all IDE before all
S-ATA irrespective of what boots first, I would remove the IDE hard
drive completely until after installing Windows. Then I'd use Admin
Tools, Storage blah blah blah to map the optical drive to a higher
letter, then add the IDE and set those volumes in between the others.

The point about Admin Tools, Storage blah blah blah is that this
CANNOT change the letter of the boot drive later. It can fudge
eveything else, but you HAVE to get the boot drive to fall naturally
on the letter you want at installation time.

There may be other S-ATA vs. IDE modes, such as completely disabling
IDE or S-ATA, and the S-ATA may be "natural" or set up as various RAID
combinations of drives (typically RAID 0 or RAID 1).
(Gerry: There is no Master/Slave positions with respect to SATA hard drives)

True.

IDE Master / Slave relationships can be defined in two ways:

1) Explicitly

Set one device to Master, set other device on same channel to Slave.
There may be additional jumper settings to distinguish between "Sole
Device", "Master with Slave Present" and "Master with
Non-ATAPI-Compliant Slave Present" - it varies with drives.

2) Cable Select

Set both devices on the same channel as Cable Select, rather than
Master or Slave. The device connected to the end of the shared IDE
data cable will be Master, and the one in the middle will be Slave.

Caveats:

Don't mix Cable Select and Master / Slave jumpers on same channel

If using 80-pin data cables, Master must be at the end and Slave must
be in the middle, even if using explicit jumpers. This is a
requirement for best signal propagation integrity. Any modern HD
(specifically, anything that uses UDMA-66 or better) should be used
with 80-pin data cables to clean up the signal quality.

The above mileage has been my experience with Intel-chipset
motherboards; YMMV depending on chipset, BIOS, etc.


---------- ----- ---- --- -- - - - -
Don't pay malware vendors - boycott Sony
 
Bob I, Cquirke, or anybody,

I would appreciate help on a S-ata issue that no one seems to get. I am
a tech and I ALLOWED the techs at the shop where I got my PC to
assemble it.
Here it is:
I have an ASUS A8N-Sli (not deluxe)
Two Maxtor 200gb S-ata HDD's
AMD X2 4200+
4X's 512 Corsair ValueSelect (mistake I know)

Problem is sort of a mystery. I have read the thread about Master/Slave
(it's all master with S-ata, IMHO) and I have a question you might
understand better than I since Hardware is my soft side.
To be brief, The Nvidia Raid controller that is built in the MoBo seems
to show a Healthy Raid 0 of 200gb
In the BIOS the drive config is as follows:
1-4 master/Slave IDE
1-4 S-ata
ALL enabled
No HDD's are recognized. It's as if I had no drives installed.
From what I understood, the BIOS should automatically detect the S-ata
drives (so says ASUS)
I think that maybe the techs just didn't configure the BIOS correctly
or set it up in the correct order. I am surprized that it boots. When I
go into the BIOS, I would expect to see my drives and not to see all
drives/channels enabled.
I am thinking about tearing it all down and starting over, but this
will be my first Raid setup with these specs. I don't want to mess it
up.
Also, the 4gb of RAM is set to 333MhZ and I want it at 400., that's why
I got DDR400 in the first place...
I know the MoBo will default to 333 from factory for stability with
some memory modules. The problem is that it's set to 333, all following
config is Auto and trying to change it to 400 doesn't seem to change
anyhthing once inide Windows and is benchmarked.
Please give advice if this makes any sense and what I ca do about the
mem settings which won't change if it is put to 400 and Auto. It just
says 400 with all other variables the same and seems to still be
running at 333.
I can be more specific if anyone will kindly post, just running off to
fix someone else's PC while I am a little stumped by mine.
P.S. I would like a dual boot system but don't see how that is possible
with Raid 0 (assuming no third party software is involved)

Thank you,
Range Rover 11
 
RangeRover 11 said:
Bob I, Cquirke, or anybody,

I would appreciate help on a S-ata issue that no one seems to get. I am
a tech and I ALLOWED the techs at the shop where I got my PC to
assemble it.
Here it is:
I have an ASUS A8N-Sli (not deluxe)
Two Maxtor 200gb S-ata HDD's
AMD X2 4200+
4X's 512 Corsair ValueSelect (mistake I know)

Problem is sort of a mystery. I have read the thread about Master/Slave
(it's all master with S-ata, IMHO) and I have a question you might
understand better than I since Hardware is my soft side.
To be brief, The Nvidia Raid controller that is built in the MoBo seems
to show a Healthy Raid 0 of 200gb
In the BIOS the drive config is as follows:
1-4 master/Slave IDE
1-4 S-ata
ALL enabled
No HDD's are recognized. It's as if I had no drives installed.
drives (so says ASUS)
I think that maybe the techs just didn't configure the BIOS correctly
or set it up in the correct order. I am surprized that it boots. When I
go into the BIOS, I would expect to see my drives and not to see all
drives/channels enabled.
I am thinking about tearing it all down and starting over, but this
will be my first Raid setup with these specs. I don't want to mess it
up.
Also, the 4gb of RAM is set to 333MhZ and I want it at 400., that's why
I got DDR400 in the first place...
I know the MoBo will default to 333 from factory for stability with
some memory modules. The problem is that it's set to 333, all following
config is Auto and trying to change it to 400 doesn't seem to change
anyhthing once inide Windows and is benchmarked.
Please give advice if this makes any sense and what I ca do about the
mem settings which won't change if it is put to 400 and Auto. It just
says 400 with all other variables the same and seems to still be
running at 333.
I can be more specific if anyone will kindly post, just running off to
fix someone else's PC while I am a little stumped by mine.
P.S. I would like a dual boot system but don't see how that is possible
with Raid 0 (assuming no third party software is involved)

Thank you,
Range Rover 11

If you have two 200GB drives, your RAID-0 size should be 400GB. If what
your saying is not a typo, and you have two 200GB drives appearing as 200GB,
then you do have a problem and should tear down the array and start over.

Of course, you will lose all data on both drives.

You should have set no jumper settings on either drive or at least configure
each for Master. Hook each one up to it's respective SATA controller (0 and
1), then use CTRL-S (or whatever it is) when prompted during POST to enter
the RAID Configuration. Manually configure your RAID-0 and set the
block-size to 16K unless you'll be doing more file-streaming than any other
type of usage. Oh yeah, you'll need to have your RAID drivers on a floppy
diskette.

When you boot to the Windows XP installation CD, hit F6 when prompted to add
additional drivers. Insert your floppy and select your RAID drivers. At
the Windows XP Setup Partition dialog, manually set the partition to be
logical drive C. I've had several attempt to default to F: even though the
only other drive was a DVD-RW drive.

I don't know what has happened at Asus and their newer boards, but I am
having trouble getting my Patriot Dual-Channel DDR400 memory to run at
400Mhz. I've never had any trouble with this in their older boards, but
their newer ones that suppot the 775 CPU socket seem to want to run it at
333Mhz. The only way around this that I know of is to use a different make
motherboard.

carl
 
You have RAID 1 or Mirroring installed. IF you set the RAID BIOS to show
the drives you will then see them on boot up. IF you weren't using RAID
controller then they would show up like you are expecting to see.
 
On 26 Jan 2006 05:52:05 -0800, "RangeRover 11"
Bob I, Cquirke, or anybody,
Hi!

I would appreciate help on a S-ata issue that no one seems to get. I am
a tech and I ALLOWED the techs at the shop where I got my PC to
assemble it.
I have an ASUS A8N-Sli (not deluxe)
Two Maxtor 200gb S-ata HDD's
AMD X2 4200+
4X's 512 Corsair ValueSelect (mistake I know)

Why a mistake?
The Nvidia Raid controller that is built in the MoBo seems
to show a Healthy Raid 0 of 200gb
In the BIOS the drive config is as follows:
1-4 master/Slave IDE
1-4 S-ata
ALL enabled
No HDD's are recognized. It's as if I had no drives installed.

OK, I guess that's because from the BIOS's perspective of looking
through the chipset, there are no HDs present - that's assuming the
nVidia RAID is a separate chipset added by Asus.

Google(A8N-Sli) ... oooh, studly! <swoon>

http://www.gamepc.com/labs/view_content.asp?id=a8nsli&page=1&cookie_test=1

http://www.pcper.com/article.php?aid=98&type=expert

<paste>
nForce4 Storage:
- 4 x SATA 3Gb/s
- 2 x UltraDMA 133/100/66/33
- NVRAID : RAID0, RAID1, RAID 0+1 and JBOD span cross SATA and PATA
Silicon Image 3114R RAID controller:
- 4 x Serial ATA with RAID0, 1, 0+1, 5 (RAID 5 software patch
available, no WHQL)
</paste>

Not clear whether the RAID is part of nVidia or is an add-on (e.g.
Silicon Image) that BIOS doesn't "see".

http://www.hardwareanalysis.com/content/topic/38623/

<paste>
Harddisks

Any Serial-Ata harddisk would do fine, we’re pretty fond of Hitachi
ourselves and have used up to two 250GB 7K250 discs in RAID and that
performed admirably. Make sure these are connected to the NForce 4
chipset RAID controller though. More on that later, in the section
about setting your drives up properly.
</paste>

Nit-picks on that article:
- why automatic preference for Pro over Home?
- need to warn on said:
From what I understood, the BIOS should automatically detect the S-ata
drives (so says ASUS)
I think that maybe the techs just didn't configure the BIOS correctly
or set it up in the correct order. I am surprized that it boots. When I
go into the BIOS, I would expect to see my drives and not to see all
drives/channels enabled.

If it boots, then I'd worry less about what BIOS sees. If you do a
diskette of CD boot, can you see the physical HDs?

Often RAID is implimented as an add-on, often with its own BIOS
management (e.g. "press ^&$%* to configure RAID" on POST, etc. which
leads off to this separate BIOS or BIOS extension). If this is the
case, it may be appropriate not to see the HDs in BIOS; in fact, it
may mean trouble if they are visible in both.
I am thinking about tearing it down and starting over, but I
don't want to mess it up.

Yep. If it works, I wouldn't... what I might do is google for forums
and FAQs on these issues.
Also, the 4gb of RAM is set to 333MhZ and I want it at 400., that's why
I got DDR400 in the first place...

That's odd. Check the rest of the timings to ensure there isn't
overclocking in da house (as that often relies on lamering other
settings to get it to "work"), and what the CPU's capabilities are.
Test overnight (if not over-weekend) in MemTest86 after changes,
before allowing Windows to boot.
I know the MoBo will default to 333 from factory for stability with
some memory modules. The problem is that it's set to 333, all following
config is Auto and trying to change it to 400 doesn't seem to change
anyhthing once inide Windows and is benchmarked.

I'd check those DIMMs. I'm surprised such a modern chipset is still
using old DDR, I'd have thought it would be DD2 (faster, cheaper, more
future esp. for higher capacities) by now... DDR2 goes naturally with
PCI Express, though there was a few months when DDR2 was so costly
that there was a demand for PCI Express + DDR.
Please give advice if this makes any sense and what I ca do about the
mem settings which won't change if it is put to 400 and Auto. It just
says 400 with all other variables the same and seems to still be
running at 333.

Use SIMMtester's SPD reader to query the DIMMs, i.e. to see whether
they really are DDR400 as I'd expect them to be. Check out other
settings, in case something like forcing faster CAS timings etc. is
causing a downshift to keep things working.
I can be more specific if anyone will kindly post, just running off to
fix someone else's PC while I am a little stumped by mine.

You may want to take this to the hardware forums - it's not an OS
issue per se, and there are sharper hardware minds over there.
P.S. I would like a dual boot system but don't see how that is possible
with Raid 0 (assuming no third party software is involved)

That's another battle :-/


---------- ----- ---- --- -- - - - -
Don't pay malware vendors - boycott Sony
 
Back
Top