Coops
11-04-2006, 08:56 AM
If you are using SATA 2 Drives on systems where the SATA controller only supports SATA1 speeds you may see issues where BIOS does not detect drive or XP locks during boot.
This can be resolved by changing or adding a jumper on your SATA 2 drive that will limit the drive to SATA 1 operation.
The problem is caused by the SATA 1 controller arranging with the SATA2 drive to run at SATA1 speeds. This is not always sucessful and thus the problem occurs. By placing the jumper on the drive this limits the drive straight away stopping this issue from arising.
This issue does not affect all SATA1 controllers when used with SATA2 drives, but HDD manufacturers recommend that regardless if your controller works or not you should always apply this jumper to your drive when fitting SATA2 HDD to SATA 1 controllers as good practice and also to make sure that no issue can arise.
This can be resolved by changing or adding a jumper on your SATA 2 drive that will limit the drive to SATA 1 operation.
The problem is caused by the SATA 1 controller arranging with the SATA2 drive to run at SATA1 speeds. This is not always sucessful and thus the problem occurs. By placing the jumper on the drive this limits the drive straight away stopping this issue from arising.
This issue does not affect all SATA1 controllers when used with SATA2 drives, but HDD manufacturers recommend that regardless if your controller works or not you should always apply this jumper to your drive when fitting SATA2 HDD to SATA 1 controllers as good practice and also to make sure that no issue can arise.