I suppose it's only natural that, with PCs growing ever more powerful and capable of performing multiple tasks at once, we'd put them to use doing just that. And the more tasks you have going on at once, the more constrained you'll be by the limited desktop area provided by even a screen capable of resolutions as high as 1600x1200. The next logical step is adding a second monitor, or perhaps a third, but what's going to drive those extra monitors? You could go with an AGP card plus an additional PCI card to drive that auxiliary display, but PCI graphics cards aren't easy to find, especially if you want something with good video signal quality. Why not just run two or more displays with a single graphics card?
If you're ready to take the multimonitor plunge, you have a few choices. There's ATI's HydraVision, Matrox's Dual and TripleHead, and NVIDIA's nView. Each multimonitor system juggles hardware compatibility with software features in an attempt to make the most of an multimonitor desktop. Which one is right for you? Let's find out.
Multimonitor setups explored
For some time, Windows has been able to recognize multiple graphics cards in a single system. Years ago, it was quite convenient simply to add a PCI video card in addition to a primary AGP card to support a secondary display. In time, graphics companies caught on to the multimonitor idea and started supporting multiple monitors on a single graphics card. It's a good thing they did, since good PCI graphics cards are so hard to find these daysjust ask anyone with one of Shuttle's non-AGP-equipped cubes.
Windows XP allows multiple-output graphics cards to drive multiple displays to create a single, unified Windows desktop in an expanded workspace. WinXP will also allow a secondary display to mirror the contents of a primary screen. Really, it's up to you how you make the most of a couple of monitors.
That's all there is to multimonitor graphics, at least on the surface. However, there are at least a few compatibility problem areas to keep an eye on, and a lot of feature differentiation between offerings from various companies. I've highlighted some particular areas of concern below.
|Independent monitor settings||XP desktop support||3D acceleration spanning||Virtual desktop limit||Intelligent monitor detection||Application position memory||Application preferences|
Some of the above terms and categories may not be clear for those unfamiliar with multimonitor setups, so I'll go over them one by one. Incidentally, I'll try to keep track of functionality in both Win2K and WinXP through the course of this article, but the various multi-display implemantions vary in quirky ways between Win2K and XP. My primary focus will be Windows XP, since it's the newer OS.
Here, compatibility issues arise with Matrox's TripleHead three-screen configuration, which we'll cover more a little later. Additional incompatibilities also arise with Windows 2000, where only Matrox's DualHead and NVIDIA's nView are capable of adjusting the resolution, refresh rate, and color depth of multiple monitors independently.
If you don't need your taskbar stretching across multiple monitors, or if you want to run independent monitor settings, you'll need to run an extended Windows desktop. Here, only the actual desktop area (not including the taskbar) extends to auxiliary monitors, and Windows sees the configuration as a series of individual displays. With an extended desktop, you can adjust the orientation of auxiliary displays to be above or below your primary display rather than locked down beside it in a widescreen stretched desktop.
|The TR Podcast 171 video is now available via YouTube||2|
|Deal of the week: Radeons, mechanical keyboards, IPS displays, and more||5|
|Windows 10 to support USB 3.1 Type-C's new features||17|
|Apple preps for March 9 'Spring Forward' event||43|
|Thursday Night Shortbread||52|
|TR's February 2015 System Guide||64|
|ISPs to be common carriers under new FCC rules||186|
|These folks won a copy of Homeworld Remastered Collection||52|