Search results for query: *

I did run some more tests and found the root of the problem. It seems that the NetRAID, Compaq, or Windows 2000 (I suspect the NetRAID), didn't like the drives I had installed. The drive I was using to test with was a 36GB drive. In a RAID5 array of 4 drives, I was swwapping one of the 18's out...

Good guess... it was also one of my first guesses as that's what it seemed to be. I disabled caching and it did the same thing. All is not lost though. I do have a solution and this isn't one that can be fully explained. On a whim, I pulled one of the four disks in the RAID5 array. I then ran...

Gee... I find this a little odd. I had the EXACT same problem and, I too, fixed it with a new motherboard. What the heck? Is there a big time known issue with these boards? The board actually worked fine for years, and then one day, BOOM, I got the CPU 2 error. Weird.

I do know one odd quirk on the 3000 series... I tried installing 768MB of Compaq RAM, in the recommended sequence (and paired of equal size), and it booted and BIOS saw the memory but gave an error stating something to the effect of "The CPU cannot support the amount of RAM you have...

I have a Compaq Proliant 3000 (dual 333Mhz and 512MB RAM; BIOS E39 dated 04/06/1998) with an HP NetRAID SCSI adapter. I currently have 2 x 16MB (32MB) cache on the card, but have tried 1 x 4MB and 2 x 4MB with no changes. I also ensured I was using the newest BIOS on the NetRAID (4.03). Not sure...