|I have tried a PCI IDE controller card capable of a UDMA 133 burst speed with several mboards that have older main chipsets that are not capable of that, or not capable of a UDMA 100 burst speed, along with a hard drive that is capable of that , or a hard drive that is capable of a UDMA 100 burst speed.|
As I recall, one of the mboards had a 440xx main chipset, but it was not 440BX (440LX?).
I found that the hard drive cannot run faster, when connected to the PCI controller card, than the max speed the mboard's main chipset supports.
However, I have seen a few posts here where mboards with newer chipsets than I tried the card with are sometimes able to support the full speed of the hard drive in that situation.
The mboard's bios not being able to recognize the full size of a hard drive larger than 128gb (binary; 137gb manufacturer's size) is not a problem.
The PCI controller card will recognize any size of hard drive because it has 48 bit LBA support, so if the mboard's bios can't recognize drives larger than 128gb, or smaller, the whole drive capacity can be recognized and used by the operating system if the drive is connected to the PCI card.
(XP must have SP1 or later updates installed or integrated into it in order for it to recognize drives / partitions larger than 128gb (binary; 137gb manufacturer's size). If you install XP from an XP CD, it must have already have that - if it doesn't, you must make yourself a "slipstreamed" CD that has at least the SP1 updates integrated into the contents of your CD - you might as well integrate SP3 updates if you need to do that - and use that CD to boot the computer with and install Windows.)
In order to boot from a hard drive connected to the PCI controller card, you must be able to select booting from SCSI in the boot order or similar settings in your bios Setup, and have that listed before any hard drive. That's usually there if the bios version is retail - that of the mboard manufacturer - but that's often NOT there if the bios is one for a brand name system.
Brand name system builders almost always did not make the mboard - it was supplied to them by some major mboard manufacturer.
You CAN use a free drive overlay program available from the hard drive manufacturer's web site to support recognizing the full size of the drive that is larger than the mboard's bios can recognize, but I don't recommend that for most people - you have to be very careful how you use bootable disks, otherwise you can easily trash or lose access to the data on the drive. You DO NOT boot the computer with a bootable disk already inserted - you must wait until you see a line while booting (it's put there by the drive overlay program) that pauses the boot and says then is the time you insert one, then insert it.
If you are running XP on this system, the proper 400BX main chipset drivers are probably built into XP.
If they are, your IDE hard drive(s) should show it/they are running in Ultra DMA mode 2 on this mboard in Device Manager, if it/they support a ATA 33 burst speed or greater.
If that's what you see, the main chipset drivers are built into XP and there's nothing wrong with them (they're not corrupted), and there's nothing wrong with the IDE data cable connection to it/them.
(If it's/they're all in PIO mode too, the main chipset drivers can be re-loaded.)
Whether your CD drive runs in PIO mode or a higher mode depends on how old it is. If it's as old as this system, it may not be capable of anything but PIO mode. However, most CD drives are capable of at least Multi-word DMA Mode 2 (which is much slower than Ultra DMA mode 2, = ATA 33).
If you have a problem with the data cable the drive is using, or if the drive is in the process of dying, XP will automatically set the drive to PIO mode after Windows has detected over a certain threshold of data errors for the drive. If Windows continues to detect data errors for that drive after that, a line will be created in the Registry that prevents you from setting that drive to anything but PIO mode - the line can be removed from the Registry, but if the problem that caused the data errors is still there, the line will be created again, right away, or after a short time.
I have a system with XP on it that has an LG 52X CDrom drive and a fairly recent LG DVD combo burner drive (reads and burns both CDs and DVDs).
The LG CDrom drive was running in PIO mode - I chose DMA if available, clicked on OK, then went back in and looked - it's now in Multi-word DMA Mode 2, which is what it should be for that CDrom drive or most CD burner drives.
(That drive hasn't been used much and has no data cable problem - sometimes Windows doesn't initially set the mode of an optical drive correctly. I hadn't checked the mode it was in since I last installed XP. )
If you choose DMA if available, click ok , then go back in and it's still set to PIO mode...
- if the drive is really old, it may only be capable of PIO mode
- if the drive is capable of Multi-word DMA Mode 2 or higher, Windows has made the line in the Registry that prevents that drive from using anything but PIO mode because too many data errors have been detected for it.
That's usually caused by
- there's a problem with the drive's data cable
- or - the drive is malfunctioning - if it's been used a lot, that's much more likely.
It is common to un-intentionally damage IDE data cables, especially while removing them - the 80 wire ones are more likely to be damaged. What usually happens is the cable is ripped at either edge and the wires there are either damaged or severed, often right at a connector or under it's cable clamp there, where it's hard to see - if a wire is severed but it's ends are touching, the connection is intermittent, rather than being reliable.
Another common thing is for the data cable to be separated from the connector contacts a bit after you have removed a cable - there should be no gap between the data cable and the connector - if there is press the cable against the connector to eliminate the gap.
80 wire data cables are also easily damaged at either edge if the cable is sharply creased at a fold in the cable.
Try another data cable if in doubt.
To remove the lines that are forcing the drive to use PIO mode (there is usually more than one) ...
NOTE - be careful - it's recommended you backup your Registry BEFORE you do this.
Start - Run - type regedit, OK, choose Edit - Find - type masteriddatachecksum - delete all the enties found, on the right, that have that - press F3 to search again (there is usually more than one); do the same for slaveiddatachecksum; exit regedit - reboot - your drives should be their max DMA, or the mboard's max DMA if that's less.
Win 2000 and up always opens Regedit where it was in the registry when it was last used.
Make sure the list on the left is set to the top of the list - My Computer, BEFORE you start a search - click on that to highlight it - otherwise you may not be searching the entire Registry.