Having just had two days of hell after fitting a new mobo I have a small question to ask. I fitted the mobo and it immediately started freezing etc on installing 98se. I run two h/d's on raid stripping. I found out that one of my h/d's had gone belly up on me. Can the ide connection, mobo or cable have caused the h/d to die or was it simply bad luck. I don't want to use the raid chanels until I know. Any ideas.
i had two HDDs since i installed a asus a7v266, very strange but the first one was a cheap ide cable second is the hard disc and the mobo ain't had anything to do with it *yet* but i'd guess at the most likely candidate of the ide cable or hdd
Well, the first problem was the h/d. It would not hold any info, came back as a disk error on fdisk, but was not making any noice. Simply Computers gave me an exchange straight up. Then I got the mobo running, or limping yesterday. Today it will not enter bios, post or anything. The CPU is fine as well as the rest of the hardware as it is back in my KT7. The Soyo was starting to take one hell of a long time to boot and was getting gradually slower. So onto the phone to chillblast on Monday to get it exchanged. What else can possibly go wrong next. Before you ask I am meticulouse with touching only edges and wearing and earth strap. God I hate computers - until tomorrow.
I had to open my mouth. Ran over a bit of glass on my motorcycle and buggered the front tyre. Took it to the shop and the wheel bairings had gone. 90 quid later and its fixed. Merry Christmas.
Well it goes that way sometimes. I have not given up on the soyo mobo. The potentual is great. Has yours been running ok.
Yep, Mine has been going without any probs at all yet (Touch wood!). I can only hope that when you get your next one all will be OK. It really is a great board when it's up and running!
It's a little Yamaha XJ600N. Smallest bike that I've owned in years, but buzzes along and is great fun to ride. It's black with a belly pan etc. Looks well sweet.
Back to the raid problem: I tried installing Win 98 SE on my latest system which has an AMI RAID controller built on. Since I had previously used a FastTrack RAID as my boot drive I figured that I'd do the same with AMI's. Oops! Found out two re-installs later that not all RAIDs can be used for boot (not a problem with AMI or FastTrack) and that some are very sensitive to what drivers are used. The latter was the problem with the AMI RAID. The install was fine with the first section of 98 SE. Consecutive sections were botched because Windows started using a drvier to control the RAID instead of treating it like any ATA drive. I believe that's your problem. I finally got around it by using another drive on the standard ATA controller. Not the best, but not too bad since now my swap file is on a different IDE Channel than most of the programs I'm loading (off of the RAID.) Reasonable tradeoff, but a pain, nonetheless.
Thanks for the info SonicSilicon, but on this occation it is a h/d. The h/d would not work when it was a single drive on its own and the raid was disabled in the jumpers and bios. These things happen. I don't like the fast track raid as much as the Highpiont however. With the Highpoint you can use a single drive on one of the raid ide connections. But with Promise you have to put a drive on each of the chanels (ide 3&4) if you want to use them as normal ide channels. Jamiesurfes, I called Chillblast today and they are giving me a replacement with no quibbles, but they will not be getting any new boards in until 05/01/02. So some wait still.
