//flex table opened by JP

Click to See Complete Forum and Search --> : ABIT BE6 and HPT366 windows 2000 drivers


eclypse
01-17-2000, 07:20 AM
I have an ABIT BE6 motherboard and I cannot get my ATA66 controller to work with my Windows 2000 server (Beta 3 CDROM) am I missing something? I installed Windows 2000 Server on the ATA33 Controller then installed the ATA66 HPT366 drivers from Highpoint-tech.com's website version 1.22 for Windows 2000 both controllers installed fine and there were no errors. I then migrated both my Western Digital ATA66 drives over in the exact same configuration and booted up. I get my menu screen to select Windows 2000 server or Microsoft Windows (Win98 SE) it begins to boot, then I get the black screen with the periods running across the top (loading hal I think) the it just locks up and my HDD led stays lit?? WTF I say http://www.sysopt.com/forum/smile.gif If I select Win98 it boots fine on the controllers as usual, I cannot even select safe mode in W2K. Any clues?
Oh yeah here is my system info in case you need it for reference.
----------------My system--------------------
Inwin IW-Q500 full tower with 300watt power
ABIT BE6 MB Bios upgraded to version (PL)
On board HPT366 controller with updated bios
from MB bios upgrade.
P3 600 (100FSB)
384MB Mitsubishi PC100 ECC SDRAM (3x128)
Creative Labs Anihilator PRO 32MB DDR GeForce (Using NT4.0 Detonator 3.68)
Diamond MX300 Sound (MSw2k aureal vortex 2 drivers)
2 Kingston KNE110 TX Fast Ethernet 10/100 cards using Kingstons latest Beta W2K drivers
Tekram Ultra Scsi Adapter 390F/U Using the Symbios drivers built into W2K
Toshiba 6x32 DVD (IDE)
Smart And Freindly 8x20 CD-ROCKET CDR 8020 (SCSI 2)
Western Digital 10.2 GB ATA66 (Caviar)
Westerm Digital 8.4 GB ATA66 (Caviar)
Windows98 SE
Windows 2000 Server Beta 3



[This message has been edited by eclypse (edited 01-17-2000).]

tlwhite76
01-18-2000, 11:33 AM
Could that be why it's a beta version? If it works fine in Win98, I don't think there is anything wrong with your board. You sure know how to pack the hardware in that box of yours.

eclypse
01-19-2000, 12:08 AM
I know that the OS is a beta, and so are the drivers are too, I was just looking for anyone who may have done it successfully. I did finally get it working, it took about 8 different beta versions of the HPT366 drivers to find the one that worked and alowed me to boot from the ATA66 controller. All the drivers allowedt he controller to be used, but not booted from it would hang. I find that the OS itself is very stable so far and have no problems with the ATA drives at all. http://www.sysopt.com/forum/smile.gif Oh yeah I like my hardware http://www.sysopt.com/forum/smile.gif Can't get enough of that goodness. Funny thing though most of my leftovers from upgrading is still top shelf stuff too not quite old enough to consider outdated hehe. Here is the system I replaced with this one a few months back.

Supermicro 750 full tower+300watt
Tyan Thunder 100 Dual with 2 SL2W8 P2 300Mhz @504Mhz
256MB Toshiba PC100 SDRAM
Matrox G400 32MB AGP (not dual out)
2 WD 20.4 ATA66 HDD
Fasttrak ATA66 Raid card running raid 0 (striped 40GB drive)
3Com 10/100 fast ethernet
Yamaha 4x6 CDR SCSI 2 on Adaptec controllers on the MB
Soundblasrer Live PCI audio
Samsung Syncmaster 900p 19" monitor

This was one of my best and most stable PC's
not bragging i kinda miss that machine http://www.sysopt.com/forum/smile.gif
Eclypse

Mntsnow
01-19-2000, 12:21 AM
Well it looks like you found your answer in that you need to find different drivers and Bios for the ata66 controller. I went thru the same headache's getting my BP6 to use the ata66 to boot from in win2k but finally got it to work with the answer I got at www.bp6.com (http://www.bp6.com)

Mntsnow

eclypse
01-19-2000, 12:29 AM
I got those drivers amongst others, ultimately it was an NT4.0 driver that worked not a beta w2k http://www.sysopt.com/forum/smile.gif

Take care dude.

Eclypse