Test System and Configuration
Hardware
Swipe to scroll horizontally
| Processor: | AMD Athlon X2 TK-53, 1.7 GHz, 800 FSB, 512KB Cache |
| Motherboard: | DELL 0WY383, BIOS: 2.5.2 (07/30/2006) |
| RAM: | Hyundai PC2-5300 @ 266 MHz |
| Row 3 - Cell 0 | 2x512MB, Dual Channel, CAS 4-4-4-12 |
| Hard Drive: | Samsung HD160JJ - P80SD |
| Row 5 - Cell 0 | 160 GB, 7200 RPM, 8 MB Cache, SATA 300 |
| Networking: | NVIDIA nForce onboard Gigabit Ethernet NIC |
| Graphics Cards: | Integrated Radeon Xpress 1150, 256MB RAM (shared) |
| Row 8 - Cell 0 | Sapphire Radeon 2600 XT, 256MB RAM |
| Row 9 - Cell 0 | HIS Radeon 3870, 512MB RAM |
Software
Swipe to scroll horizontally
| OS: | Microsoft Windows Vista (6.0) Business Edition |
| DirectX Version: | 10 |
| Graphics Driver: | Catalyst 7.10 |
The Dell Laptop we tested the ViDock on has an Athlon X2 1.7 GHz processor. This isn’t the most powerful laptop processor by a long shot, so it will provide a decent representation of what the ViDock Pro can do for a typical machine.
It’s important to mention that the driver included in the ViDock installer was the older Catalyst 7.10 driver. Because of this, it’s the driver we used in all of our testing, including the video cards we jury-rigged to work with the ViDock.
First, let’s look at what the ViDock Pro accomplished compared to the integrated chipset in games and 3D production benchmarks.
