I know you wanted to hear, “Oh! It’s a great computer. It’s superfast and a dream come true.” Well, I can’t quite say that this time. I seemed to have run into problems this weekend with the whole process. Let me explain.
On Thursday night, I had all my parts together and ready for assembly. I decided to start putting everything together. By the end of the night, all that was left was installing the cables.
Friday, I put the wires in and got ready to install Windows. At this time, I realized I needed to also install a floppy drive. Without it, you can’t setup your raid drives because the floppy drive is the only means of getting your drivers into windows during installation.
I had a floppy drive and one disk, but it was inside of my presently working computer. So, out it came and into the new computer. This is when the trouble began.
First, I couldn’t get the new computer to read the data on the floppy disk without error. After fiddling around with it for a while, I found out (by trial and error) that it was the flat cable that was bad. With the cable replaced, I was on my way to installing Windows on the new PC.
However, next I needed to turn the old computer back on. Doing so displayed an error that the hal.dll driver was missing or corrupt. Uh Oh. This Windows driver contains information about your hardware and tells the computer what to setup during boot. Looking around online (via a laptop), I notice that there are many other people out there that have experienced this same problem. The solution was to replace the hal.dll file and recreate the boot.ini file. Just like about 70% of the others out there, this didn’t work for me. Goodbye working computer.
It was at that time that I made it a mission to complete the new machine and make that my primary computer. The old machine was dead to me. The data? Well, that could be retrieved by setting up the hard drives in the new machine later (yeah, that did work).
Back to the new machine because my troubles were not over. Everything was going well until it was time to setup my four monitors. I was previously working with two PCIe GeForce 6800 cards to power my four monitors. Who would have thought there would be a problem with the newer and greater 8800 card series.
Turning the computer on with four monitors resulted in Windows being unable to boot.
Turning the computer on with three monitors resulted in the NVidia driver crashing at boot.
Two monitors worked fine. Why?
For 1.5 days I was convinced it was a power issue. I figured I couldn’t get enough juice to the cards. Amazingly, these new cards require 30amps of power to run. Trust me, that’s a ton of power. But, after visiting forums and calling BFG (the card manufacturer) I realized that this wasn’t the problem. The problem is most likely the drivers from NVidia. I found two forum posts referring to the hope the NVidia would support multiple monitors in the near future. Damn!
So, newer doesn’t always mean better. It’s a lesson I already new and don’t like being reminded.