This is a general description of the most frequently asked questions about the IDE/EIDE Interface. This information is meant only to address basic troubleshooting of IDE/EIDE compatibility issues, and is not meant to be an in-depth discussion of all possible error issues. Our purpose is to aid you in solving basic IDE/EIDE difficulties that may arise.
- IDE/EIDE Definitions
- Compatibility Issues
11.Why is the 20th hole plugged on the Ribbon Connector?
It is a means of preventing the cable from being installed (plugged in) upside down. Users that inadvertently plug a cable in backwards can cause damage to both the hard drive and the motherboards interface. If your system does not have the corresponding missing pin, you may remove this plug by “teasing it out” with a straight pin.
12. Does the IDE interface cable influence data integrity, signal noise issues and drive recognition?
The answer is Yes! The ATA standard specifies that an IDE Interface cable should be no longer than 18 inches. The standard cable used today conforms to the ATA specifications. However, 40 pin interface cables do not always filter out noise when used with the Ultra DMA 33, 66, 100 and even 133 hard drives of today. Another option for reduction of cable noise would be to use an 40-pin 80-wire interface cable. These cables provide better grounding to maximize signal integrity.
13. Will adding an EIDE Interface increase disk performance?
Although most, if not all computers manufactured today have the fastest interface available, the answer really depends on the hard disk drive. Unless you’re working with legacy equipment, a new interface may not give you a performance increase. As an example, upgrading an ISA controller to a PCI controller would be the biggest improvement a user could make.
14. Why is the hard disk drive NOT as fast as advertised?
Advertised transfer rates are based on the fastest speed at which the drive can send data across the ribbon cable from the drive buffer, with the transfer stopping temporarily every time the buffer re-fills. This process continues until a command is complete. Data transfer rates will differ between system configurations, as a drive is not the single component that decides transfer rates. The one thing that designers have control of is the speed at which data transmits across the data ribbon cable from the drive’s buffer, but not how your other components interact with the drive.
15. Why is it that an old IDE drive may not work with a New IDE drive?
The reason is the fact that many hard drive manufacturers were already making and selling drives before the IDE standard was clearly defined. While this is now, for the most part, relegated to very old IDE drives that have problems functioning in dual-drive configurations. This scenario was more prevalent when the hard disk drives are from different manufacturers, however, in some cases, two drives may not function together at all. Even today though, in rare circumstances even new drives will not work together.
16. Why is my new IDE drive not recognized as a slave or a master?
Configuring IDE drives can be simple, as is the case with most single-drive installations, or troublesome, especially when mixing drives from different manufacturers on a single cable. Most IDE drives must be configured in one of the following ways:
- Single-drive (master)
- Master in a dual-drive system
- Slave in a dual-drive system
Because each IDE drive has its own controller, one drive must be jumped as a master and the other as the slave. There are no functional differences between the two, except that the drive that’s specified as the slave will assert the DASP (Drive Active/Slave Present) signal after a system reset to inform the master that a slave drive is present in the system. Daisy-chained hard disk drives that do not have their jumpers set correctly will not function. You should contact the disk drive manufacturer if you are unsure of proper jumper settings.
17. Two hard disk drives will not function even after verifying jumper settings. What could be wrong?
There may be a compatibility problem between the two drives. Use the following steps to verify the function of each drive:
- Test each drive by itself, making sure that each drive has been jumpered correctly. If both drives work by themselves, you may conclude that there is a compatibility problem.
- Try “swapping” (switching) the drive’s position, what was the master will be changed to a slave and the slave will become the master.
- Most motherboards have two IDE bus connectors. Place one drive on each IDE bus and test the system.
18. Why does an IDE CD-ROM and Tape Backup not work when attached to the Interface?
On occasion, attaching an IDE CD-ROM or tape backup drive to a bus that supports an IDE drive, can slow down and even compromise the drive’s data integrity. Although this is extremely rare today, make sure that your systems motherboard has an Enhanced IDE interface that is ATAPI compliant. If it is not, you can purchase and add-in card that has this interface, and they usually come with a secondary IDE interface built on the same card.
19. Even after switching roles, my hard drives still will not work. What else can I do?
First, see questions 16 and 17 above. We recommend that you separate the hard drives and connect them to the different interface ports (IDE buses) of the system. If the system does NOT have a Secondary IDE interface, we recommend that you install an EIDE interface card. By doing so, each of your drives would be able to communicate individually with the system. Enhanced EIDE cards also can add BIOS LBA support and enhanced performance for the drives.
20. Why are 80-wire, 40-pin ribbon cables required for certain hard drive configurations?
40-conductor cables support only up to 33MB/sec transfers (and should only be used for up to 16MB/sec or less in our opinion), while 80-conductor cables support up to 100MB/sec. Thus you can always replace a 40-conductor cable with an 80-conductor cable, but not the other way around without seriously hurting transfer speeds, and quite possibly damaging one or more of your systems components.