Win2k/ Hpt366(Abit BE6) trouble
This is a discussion about Win2k/ Hpt366(Abit BE6) trouble in the Windows Hardware category; I have many IDE & SCSI devices so as an intro I will make a list (All HDDs are FAT32) This is a long problem so please bear with me: ATA33 (onboard ATA33 controller) Primary Master/Slave = Drive C/Drive D Secondary Master/Slave = CD-Rom/CD-RW HPT366(onboard UDMA66 Controller) Primary Master/Slave = Drive E/none Sec ...
I have many IDE & SCSI devices so as an intro I will make a list (All HDDs are FAT32) This is a long problem so please bear with me:
ATA33 (onboard ATA33 controller)
Primary Master/Slave = Drive C/Drive D
Secondary Master/Slave = CD-Rom/CD-RW
HPT366(onboard UDMA66 Controller)
Primary Master/Slave = Drive E/none
Secondary Master/Slave = DVD/none
SCSI
Zip100
The above are my drive configurations. Note that they are connected in such a matter because of physical location (eg I can't connect Drive E to DVD because of where they are located in my tower).
Now the specs
Abit BE6
everything else not important. No overclocking. Only overclocked hardware is video card.
And finally the problem:
I am ready to make the final switch to Windows 2000 but there is this major problem I have that is keeping me from doing it. Win2k won't "see" any hard drives connected to my UDMA66 controller. It detects and assigns a drive letter to my DVD but not my hard drive(s) on that controller. Whatever drive I put, Windows tells me that it is unreadable. I am using the latest drivers for the controller from Abit. Another odd thing is that the HDD is tagged as a SCSI device. I suspect that it could be the controller but I could be wrong.
What I tried:
*running the useless troubleshooting wizard - no luck
*using the built in drivers - no luck (crashes on boot)
*using updated drivers - no luck (DVD works HDD doesn't)
*switching the cables of the DVD and HDD around - no luck
*using different HDDs - no luck (same problem)
*using drive under Windows ME - works but hate WinME
*moving drive to other 2k computer - works as a primary slave.
If you are this far then I thank you for bearing with me and taking the time to read this. (More thanks are in order to whoever finds a fix). At least respond so I know this is actually being read.
ATA33 (onboard ATA33 controller)
Primary Master/Slave = Drive C/Drive D
Secondary Master/Slave = CD-Rom/CD-RW
HPT366(onboard UDMA66 Controller)
Primary Master/Slave = Drive E/none
Secondary Master/Slave = DVD/none
SCSI
Zip100
The above are my drive configurations. Note that they are connected in such a matter because of physical location (eg I can't connect Drive E to DVD because of where they are located in my tower).
Now the specs
Abit BE6
everything else not important. No overclocking. Only overclocked hardware is video card.
And finally the problem:
I am ready to make the final switch to Windows 2000 but there is this major problem I have that is keeping me from doing it. Win2k won't "see" any hard drives connected to my UDMA66 controller. It detects and assigns a drive letter to my DVD but not my hard drive(s) on that controller. Whatever drive I put, Windows tells me that it is unreadable. I am using the latest drivers for the controller from Abit. Another odd thing is that the HDD is tagged as a SCSI device. I suspect that it could be the controller but I could be wrong.
What I tried:
*running the useless troubleshooting wizard - no luck
*using the built in drivers - no luck (crashes on boot)
*using updated drivers - no luck (DVD works HDD doesn't)
*switching the cables of the DVD and HDD around - no luck
*using different HDDs - no luck (same problem)
*using drive under Windows ME - works but hate WinME
*moving drive to other 2k computer - works as a primary slave.
If you are this far then I thank you for bearing with me and taking the time to read this. (More thanks are in order to whoever finds a fix). At least respond so I know this is actually being read.
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
May 19
May 20
0
4 minutes
Responses to this topic
Did you install Win2k when you had all of this? I know Win2k puts drives in the order they are put in, so that could be screwing you up.
The drives on the HPT366 controller will be detected as a SCSI device, I cant really explain why, but any extra controllers besides the ones with the chipset on the motherboard are considered SCSI wheter they are or not.
There is the chance that the HPT366 has gone bad, but Im not totally sure that's it. Im thinking its the drivers. My dad has that motherboard and has never had a problem with it. I picked one up in a used bin and it works fine.
Another thing: got the latest BIOS for the BE6? The latest BIOS file is the BE6_TH, FYI
The drives on the HPT366 controller will be detected as a SCSI device, I cant really explain why, but any extra controllers besides the ones with the chipset on the motherboard are considered SCSI wheter they are or not.
There is the chance that the HPT366 has gone bad, but Im not totally sure that's it. Im thinking its the drivers. My dad has that motherboard and has never had a problem with it. I picked one up in a used bin and it works fine.
Another thing: got the latest BIOS for the BE6? The latest BIOS file is the BE6_TH, FYI
OP
Yes I did have all the hardware before. It all runs fine in Windows ME but I hate WinME. I am dual booting right now until I get a bigger drive or fix this problem. I have the latest BIOS TH which also includes the new BIOS for the HPT366. I downloaded the new BETA drivers for the HPT366 from the Abit FTP and now it works but not in UDMA mode. I guess it is a driver issue. I am working with Abit and High-Point to get this fixed.
I was having some probs with my BE6 (latest bios and everything) and it seems that 4x CD-ROM I had in there was fouling things up. You may want to try a different DVD or CD-ROM drive if possible.
Did you hit F6 during the install procedure?
