Had to install a new master HD to replace a failed HD on my BE6-II (HPT366). The new HD is a IBM 60GXP(ATA100) installed as a Master on my primary HPT366 controller. I also have another IBM 34GXP(ATA66) HD installed as slave on the same cable with the 60GXP HD, (cables are correct and I am not using cable select - jumps on HD's correct also). The PC will boot and I can login to Win98, but the machine will lockup right after login. I can boot to windows safe mode without problems, so I suspect a driver conflict/problem. I used IBM's Hard Drive Utility to set the 60GPX to ATA66 mode, but the lockup still occurs. The interesting thing is that if I separate the two hard drives - 60GPX on the primary and 34GPX on the secondary the PC will launch Win98 without problems and things work good. My original setup was two ATA66 drives on the primary controller and never had any problems (they did not need to be separated) and now the ATA100 and ATA66 will not coexist on the same cable, strange. I upgraded my BE6-II BIOS to get the latest beta HPT366 drivers (v1.28) to see if that would help, but no luck.
Any BE6-II(HPT366) owners out there experience the same problem, I know the HPT366 controller had a problem with IBM DTLA ATA100 drives and highpoint updated their drivers and BIOS which had me try the Abit beta BIOS for my BE6-II to get the same drivers (v1.28). This just pisses me off that two IBM drives will not coexist on the same cable:| and just want to find out if this is a known problem. I had sent an e-mail to IBM's tech support and they suspect a driver problem too. Abit has yet to reply - suspect they never will.
Any BE6-II(HPT366) owners out there experience the same problem, I know the HPT366 controller had a problem with IBM DTLA ATA100 drives and highpoint updated their drivers and BIOS which had me try the Abit beta BIOS for my BE6-II to get the same drivers (v1.28). This just pisses me off that two IBM drives will not coexist on the same cable:| and just want to find out if this is a known problem. I had sent an e-mail to IBM's tech support and they suspect a driver problem too. Abit has yet to reply - suspect they never will.
Facebook
Twitter