AMD Pushes R600 Back To May. If you were waiting for Direct3D 10 compliant hardware from AMD (formerly ATI) you will have to wait even longer. AMD pushed the launch of R600 yet once more.. And cuz it's so important to run Fear at 232 fps instead of 186....

of memory without >> dropping the clock speed too, though some of the review sites claim to have >> made that work by setting memory timings manually. There's also another >> issue here with the 1/2T timing spec, where 2T waits an extra clock cycle >> from...

it works It costs significantly more than the GTX, and offers minimal performance increase. If you can wait, like you are thinking "I would maybe like to have something a little better maybe", but I can live without it right now, then wait. Hardware always...

100000ea) The device driver is spinning in an infinite loop, most likely waiting for hardware to become idle. This usually indicates problem with the hardware itself or with the device driver programming the hardware incorrectly. If the kernel debugger...

NO point in multiple processors. - Sanity is purely based on point-of-view. I wans't that impressed either.... M PS still waiting for your hardware?? :-) one of the first UK T-Bird users.... I would agree with that. The almighty John Carmack...

driver is spinning in an infinite loop, most likely waiting for hardware to become idle. This usually indicates problem with the hardware itself, or with the device driver programming the hardware incorrectly. In many cases this is the result of a bad...

of systems and driver version we'll never really know the most accurate judgement of performance. Unless you've been waiting on a new card to come out because your is dead then I'd suggest waiting at least a month after these cards come out to pick one up....

ea) The device driver is spinning in an infinite loop, most likely waiting for hardware to become idle. This usually indicates problem with the hardware itself or with the device driver programming the hardware incorrectly. If the kernel debugger is connected...

for the HDD to react. Maybe the same kind of problem... something in Windows is moving too quickly for some piece of hardware to react, and Window's doesn't have any coding to tell it to wait for that hardware. Or, maybe it has issues with the multiplier....

on the other drive hopefully I will be able to give it access to the raid drive though. I was planning on getting an additional raid card a little bit down the road, but that’s not in today’s forecast. Still waiting on the hardware, I will post an update...