|
|
|
#842 - GeCube x1950Pro Video Card |
|
|
|
Written by Zach Jeffers
|
|
Wednesday, 04 July 2007 |
|
Page 6 of 7
Comparisons:
As always, I like to have a comparison of the products I review. The GeCube x1950Pro video card has a pretty long body to it and I wanted to show just how long. I actually did not have any newer cards that were comparable to match it to. Both the ATI x1600Pro and the nVidia 7600GS were three quarters the size of the x1950Pro. The closest I could come to matching the size of this GeCube card was an old nVidia 4800 AGP! Now that’s taking us back..!
  
Installation was a breeze as is with most new video cards. I downloaded the newest AMD Catalyst Control Center and drivers to my desktop. I then proceeded to uninstall my current video card and drivers; completely removing any trace of the previous card. In this case I was migrating away from the Leadtek nVidia based 7600GS. Keeping the old nVidia software around could cause conflicts and is best removed before installation. If you are migrating from an (for example) x1300 through x1800, the Catalyst drivers should be able to pickup the new video card without problems, but being up to date on the most current video drivers usually helps.
For testing of the GeCube RADEON X1950Pro 256MB GDDR3, HDCP Edition video card, we used the following hardware:
Enclosure: CM Stacker (STC-T01) (Noctua NF-S12 fans intake/exhaust)
Power Supply: Ultra
X3 1000watt
Processor: AMD 3800+ X2 (Socket AM2)
Motherboard: ECS
KA3 MVP
Memory: Crucial
Ballistix 2gig (2 x 1gig) DDR2 PC2-6400
Video: GECUBE Radeon X1950 PRO 256MB DDR3 PCIe x16 HDCP Edition
Storage: Seagate 7200.10 320 GB SATA2
Optical: Plextor PX-740UF PATA
Results:
Over clocking was pretty much non existent on this video card. The famous ATI Tool over clocking utility actually does not support this card and the ATI CCC Over clocking wizard would only allow a ten and twenty Mhz jump on the GPU and memory respectively. This card is obviously not for those trying to break the over clocking record books. With testing at these settings, FPS gains were minimal if even noticeable, thus the reason we chose to leave them out of the results graph.
|
|