HPT366 ATA66 in XP
This is a discussion about HPT366 ATA66 in XP in the Windows Hardware category; Well here we go again. My BE6 and HPT366 are acting up again this time on Windows XP. I just downloaded XP RC2 (though I still didn't get my RC1 CD yet ). I installed it without a hitch since my boot drive(s) are one the regular ATA33 controller on the motherboard.
Well here we go again. My BE6 and HPT366 are acting up again this time on Windows XP. I just downloaded XP RC2 (though I still didn't get my RC1 CD yet ). I installed it without a hitch since my boot drive(s) are one the regular ATA33 controller on the motherboard. Here is a quick rundown of my drives
Primary ATA33
Master: Hard drive
Slave: Hard drive
Secondary ATA33
Master: CD-Rom
Slave: CD-RW
Primary ATA66
Master:Hard drive
Slave: none
Secondary ATA66
Master: DVD-Rom
Slave: none
Adaptec SCSI
Zip drive
OK with that being said, Windows boots fine and such and it sees all drives except for my hard drive on the ATA66 primary master (though it shows the DVD-Rom on the secondary master). To elaborate more on the problem, the drive is actually seen by windows in the device manager and it is shown as a SCSI device. The only problem is that I cannot access it. I got it to work under windows 2000 before but the fix I used for 2k isn't working for XP. Anyone else experience this? Until I build a new computer I can't live with this problem. I know I should get with the times and just get one or two big hard drives but instead I am saving up to build a new one...after I get XP full.
Primary ATA33
Master: Hard drive
Slave: Hard drive
Secondary ATA33
Master: CD-Rom
Slave: CD-RW
Primary ATA66
Master:Hard drive
Slave: none
Secondary ATA66
Master: DVD-Rom
Slave: none
Adaptec SCSI
Zip drive
OK with that being said, Windows boots fine and such and it sees all drives except for my hard drive on the ATA66 primary master (though it shows the DVD-Rom on the secondary master). To elaborate more on the problem, the drive is actually seen by windows in the device manager and it is shown as a SCSI device. The only problem is that I cannot access it. I got it to work under windows 2000 before but the fix I used for 2k isn't working for XP. Anyone else experience this? Until I build a new computer I can't live with this problem. I know I should get with the times and just get one or two big hard drives but instead I am saving up to build a new one...after I get XP full.
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Aug 3
Aug 10
0
3 minutes
Responses to this topic
i had same problem with the same abit mb. i installed a promise contoller card and attached my hard drives to the primary and secondary on the promise controller i didnt use the high point ata 66 controller on the motherboard. my cd rom`s are on the mb ata 33 controller. every thing works fine. maybe high point will get compatible drivers for xp by october
man get rid of that mobo.. its baaaaad.. the be6 is by far one of the worst mb's i've ever worked with. replaced alot with blown caps for no aparent reason and many hard drives eaten. got one in the shop right now be6-ii that has eaten 3 hard drives. 2 on the hpt366 and one on the u33 controller.. also the bios sux if you use scsi cards, its hard to get it to boot right with some scsi cards because of the hpt controller, try updatin to the latest bios may help
i9
i9
today i went into device mgr the mass storage controller was still
yellow flagged i uninstalled it in both instances where it was flagged and ran the add new hardware wizard it detected the controller and i directed it to the a drive where the high point drivers were on a flloppy i received an incompatible error message but i opted to install any way i installed the drivers twice once for the primary and once for the secondary controller after rebooting the system the controller was finally recognized i shut down attached another hard drive to the high point controller and it was recognized when i re started the system my main drives are still on the add on promise pci controller but the motherboard controller now works the drivers were the hp 366 driver file 1.25
yellow flagged i uninstalled it in both instances where it was flagged and ran the add new hardware wizard it detected the controller and i directed it to the a drive where the high point drivers were on a flloppy i received an incompatible error message but i opted to install any way i installed the drivers twice once for the primary and once for the secondary controller after rebooting the system the controller was finally recognized i shut down attached another hard drive to the high point controller and it was recognized when i re started the system my main drives are still on the add on promise pci controller but the motherboard controller now works the drivers were the hp 366 driver file 1.25
