![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
plonqWhat should have been a simple chore turned into a whole evening of frustration. All I wanted to do was swap out the stupid P.O.S. IBM drive in my computer with a much more reliable Western Digital drive. While I was in there I decided to do some long-planned rewiring. I admit that the first blunder was of my own doing.
I pulled out all of the drives (two hard drives, a CDRW and a DVD) and set their jumpers for Cable Select. I blew the dust out of the system, grabbed 4-UDMA100 cables and wired them up as follows: 80G Seagate to IDE 1, 13.7G Western Digital to IDE 2, CDRW to IDE 3 and DVD to IDE 4. I powered back up, jumped into the BIOS and enabled the RAID controllers (IDE 3 and 4). On reboot the BIOS cycled through all four drives, clearly seeing and identifying each one.
Everything's groovy!
Windows did The Funky Chicken when it came up, doing it's whole "OMGWTF teh n3w w2r3z!!!" bit while it detected the changes I'd made to the hardware configuration. After many requesters and thrashing of the hard drive, it announced that it had found some generic RAID device that it couldn't identify, and some kind of "mass storage device" that it could make neither heads nor tails of. I checked in the "My Computer" folder to confirm that it was talking about my CD and DVD drives. Bugger. It must have lost the proper drivers for the RAID when I upgraded to SP2.
I went to the ABIT site and downloaded the latest Highpoint and VIA drivers for my motherboard. Windows swallowed down the first driver without a complaint, but when I tried to install the second one it was all like "That driver is so yesterday. You're not going to try and make me use it, are you?" And I'm all like, "Whatever bitch, just take it and shut up." And it's all like, "Whatever, but don't blame me if I stop working." And I'm all like, "Whatever. You always say that."
This time it was serious.
I rebooted, and it came back up into a BSOD. Grrr. I guess I should have listened to it when it complained about the IDE driver. Windows does not like it when you mess with IDE drivers. Anyone who has ever taken a boot drive formatted in one machine and dropped it into another will know about that. Fortunately I'd created a bootable XP install disk with SP2 slipstreamed into it just a couple of days prior. I jumped into the BIOS and changed around the boot order so that the first device it would try would be teh RAID device. The machine calmly went through listing all of my drives and devices on boot up, then skipped right past teh RAID device and booted me back into a BSOD. OMGWTFBBQ?! I tightened the thumb screws a bit and told it, "Attention BIOS, as of right now there is no other bootable device other than teh RAID device."
The machine rebooted. It detected all of my mass storage devices, meditated on the futility of existence for awhile, and then prompted me for a boot disk. Suddenly the distant words of wisdom from a co-worker came floating back to me from across the ages. "... and remember not to plug your DVD or CD drives into the RAID controller, not that I think you'd be dumb enough to try that." D'oh! Shitshitshitshit! That's right, the hard drives are supposed to go into IDE 3 and 4, and the other devices go into 1 and 2. Sheepishly I juggled the cables around, reset the boot order in BIOS and rebooted. The computer pondered on the great mysteries for awhile, announced that it had found a whole scad of mass storage devices plugged into my system, and then said that it NTLoader was missing, or that it needed a boot disk, or something lame like that. Ah well, missing NTLoader was something that I could deal with.
I juggled the boot order again, plugged in the new, slipstreamed install CD and rebooted. It gronked and ground and loaded up all of its install stuff. I had my finger poised over the R key to do a repair, when the Windows installer said, "OMG, like you don't even have a hard drive. How am I supposed to, like, install if you don't have a hard drive?" Bugger! It appears that Windows no longer recognizes my RAID controller. I don't know if this is a Windows thing, or a hardware problem on my machine. A friend who has the same motherboard is running off his RAID controller, so I'm thinking the problem is likely localized to my machine. Gah. I'm not too surprised if it's a hardware problem. My Centronics port has been hooped for awhile now too. Time for an upgrade, methinks.
I eventually found a combination that worked and did a repair install, though it screwed up my sound drivers and rendered my system mute. I downloaded the new audio and video drivers again, and by the end of this evening I should at least have my machine back up and running at the same level as it was before I started this whole messy process.
I pulled out all of the drives (two hard drives, a CDRW and a DVD) and set their jumpers for Cable Select. I blew the dust out of the system, grabbed 4-UDMA100 cables and wired them up as follows: 80G Seagate to IDE 1, 13.7G Western Digital to IDE 2, CDRW to IDE 3 and DVD to IDE 4. I powered back up, jumped into the BIOS and enabled the RAID controllers (IDE 3 and 4). On reboot the BIOS cycled through all four drives, clearly seeing and identifying each one.
Everything's groovy!
Windows did The Funky Chicken when it came up, doing it's whole "OMGWTF teh n3w w2r3z!!!" bit while it detected the changes I'd made to the hardware configuration. After many requesters and thrashing of the hard drive, it announced that it had found some generic RAID device that it couldn't identify, and some kind of "mass storage device" that it could make neither heads nor tails of. I checked in the "My Computer" folder to confirm that it was talking about my CD and DVD drives. Bugger. It must have lost the proper drivers for the RAID when I upgraded to SP2.
I went to the ABIT site and downloaded the latest Highpoint and VIA drivers for my motherboard. Windows swallowed down the first driver without a complaint, but when I tried to install the second one it was all like "That driver is so yesterday. You're not going to try and make me use it, are you?" And I'm all like, "Whatever bitch, just take it and shut up." And it's all like, "Whatever, but don't blame me if I stop working." And I'm all like, "Whatever. You always say that."
This time it was serious.
I rebooted, and it came back up into a BSOD. Grrr. I guess I should have listened to it when it complained about the IDE driver. Windows does not like it when you mess with IDE drivers. Anyone who has ever taken a boot drive formatted in one machine and dropped it into another will know about that. Fortunately I'd created a bootable XP install disk with SP2 slipstreamed into it just a couple of days prior. I jumped into the BIOS and changed around the boot order so that the first device it would try would be teh RAID device. The machine calmly went through listing all of my drives and devices on boot up, then skipped right past teh RAID device and booted me back into a BSOD. OMGWTFBBQ?! I tightened the thumb screws a bit and told it, "Attention BIOS, as of right now there is no other bootable device other than teh RAID device."
The machine rebooted. It detected all of my mass storage devices, meditated on the futility of existence for awhile, and then prompted me for a boot disk. Suddenly the distant words of wisdom from a co-worker came floating back to me from across the ages. "... and remember not to plug your DVD or CD drives into the RAID controller, not that I think you'd be dumb enough to try that." D'oh! Shitshitshitshit! That's right, the hard drives are supposed to go into IDE 3 and 4, and the other devices go into 1 and 2. Sheepishly I juggled the cables around, reset the boot order in BIOS and rebooted. The computer pondered on the great mysteries for awhile, announced that it had found a whole scad of mass storage devices plugged into my system, and then said that it NTLoader was missing, or that it needed a boot disk, or something lame like that. Ah well, missing NTLoader was something that I could deal with.
I juggled the boot order again, plugged in the new, slipstreamed install CD and rebooted. It gronked and ground and loaded up all of its install stuff. I had my finger poised over the R key to do a repair, when the Windows installer said, "OMG, like you don't even have a hard drive. How am I supposed to, like, install if you don't have a hard drive?" Bugger! It appears that Windows no longer recognizes my RAID controller. I don't know if this is a Windows thing, or a hardware problem on my machine. A friend who has the same motherboard is running off his RAID controller, so I'm thinking the problem is likely localized to my machine. Gah. I'm not too surprised if it's a hardware problem. My Centronics port has been hooped for awhile now too. Time for an upgrade, methinks.
I eventually found a combination that worked and did a repair install, though it screwed up my sound drivers and rendered my system mute. I downloaded the new audio and video drivers again, and by the end of this evening I should at least have my machine back up and running at the same level as it was before I started this whole messy process.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2004-08-17 11:06 am (UTC)I had difficulty getting the RAID controller on an Abit motherboard
to function a few weeks ago. Seems when i used the MB to check out
a 60 gig drive, it would boot to it while connected to the RAID controller.
BUT When setting up Win 2000 on a 10 gig drive, it can't see the drive while
connected to the RAID controller...sheesh..
no subject
Date: 2004-08-17 11:28 am (UTC)I've been nursing this machine along since early 2000, so I guess I'm due for an upgrade sometime soon. I'm watching the prices. Oh yes. Soon a fastnewsexy machine will be mine. Well, before Christmas anyway.
no subject
Date: 2004-08-17 11:57 am (UTC)*hugs*
The secret word is AAAAARRRRRRRRRRRGG!!
Date: 2004-08-17 05:43 pm (UTC)Install This drive is not formated would you like tio format now?? Heck NO read the bloody DVD....
FEH FEH I say Try another SAME {Woof uses many many colorful bad words}.. "Reinstall drivers read instructions nada Call eldest in Seattle *HALP* Fiddle with registry bad words DEEP fiddle with registry. Dave" Try it again...... DRAT Have you tried another DVD??? YES DA***T same rssults "So why not try another?" {Woof loads Ranma1/2}
DAYMMNN i got pictures.. What the????..
Bottom line was 2 unreadible DVDs in a row {Very imaginitive usage of bad words}
And the original *bad* player wasn't.
Well I wanted that burner anyway, and it runs Perfictly on USB2.
Ain't tecnology grand??
T.
Re: The secret word is AAAAARRRRRRRRRRRGG!!
Date: 2004-08-17 08:24 pm (UTC)