!!!

[Goosemaster]

Sup peeps


Well I have a complicated question for you.

I am making a comp for a friend with win2k, and it isn't cooperating.


So what do you guys think about this system?

Abit KT7A-Raid
1.33Thunderbird
512MB pc133 Ram cas 3
9.1GB Seagate Cheetah 10K ultra2lvd
60 GB IDE Western Digital
Advansys SCSI CARD (ultra ultra2lvd>>>ASC3550/ASB38500<<<
16x/48x Toshiba DVD
16/10/40a Plextor Burner
Zip 100(Just in case)
Gainward Geforce2 MX400 32MB 4ns(the best mx 2 card)w/ tv out
Sound blaster live value
Cables etc.
Antec 1030 SOHO File server case
Floppy
Windows 2000 Misc keyboard etc

Now first, of all, i can't get the WD drive to react at all. Sometimes it is registered in the bios;most the time it isn't.

Now then, I tried to do a direct install using the scsi drive. Unfortunately Advansys decided to move off of the planet, so only NT drivers are available. I know I kniw, but what else is there?
Anyways, i try the floppy and win2k installation recognizes the driver and proceeds, then it gives me the messsage that no drive was found. I am so stuck. I even attempted to install win2k with the WD (60GB) but that didn't work. On the boot after the install, the screen would stay black when the disks were about to boot up. anyone got any tips?
I've been working for a bout 3days and i can't figure it out
ANd where the hell is advansys !!!
is my mobo messed up? my drive checks out ok?






I appreciate your pitty and your assistance in my moment of grieving

 

[TheTeacher]

What kind of power supply are you using? Bad IDE cables? Using latest BIOS? Is IDE drive plugged into RAID controller or IDE? IRQ conflict maybe? Try moving some cards around. Is system overclocked? Are memory timings right, as in is it set for cas3 and not cas2? Just trying to shed some light on the situation. I'll do what I can to help as I have had that board before. I did have problems with the HDDs not being recognized all the time. It had to do with overclocking on that one. It was becuase of my memory.
Mike

*EDIT*
You did Fdsik and format the drives right?

 

[jamesbond007]

I've noticed the same problem with some WDs I've used to build some computers for customers. What I've done to solve the problem is to set the drives to Cable Select and let the BIOS select it. The IBMs, Fujitsus, Seagates, etc don't have this problem, but only the WDs.

Give that a try.