My new notebook has a wide screen display which, over the week away, I'd rather learnt to like. So, bearing in mind that I spend a lot of time staring at a monitor screen I thought I'd get a new wider one. So I did.
The new monitor has a fantastic, jaw dropping display of amazing quality. Which is just as well, because otherwise I might have chucked it through the window by now. It is a 22 inch HP job, with an HDMI input as well as VGA and a lovely glossy finish. However, it and Vista just don't get on.
I know exactly how this should work. I know because I've read the White Paper "Transient Multimon Manager (TMM) Ver. 1.1" by Yu-Kuan Lin Program Manager, Mobile PC Business Unit. This is well written, comprehensive and has some nice scenarios that explain just what should happen. Essentially, the whole thing has been designed so that you set a monitor up once, Vista remembers that setup and then replicates it each time you plug that monitor in again.
This does not happen.
What happens is that you set it up once, and next time you plug it in the system does what the heck it likes, with a range of implausible and hard to select display options. Should you be stupid enough to let the screen saver kick in it then does something else. And if you are such an idiot as to put the machine to sleep you can look forward to no screen, a black screen with a cursor, a screen that you can't do anything with because the window is on the other screen or the blue screen of death when you come back depending on the whim of the system.
I'm not sure who to blame here. The monitor has the habit of reporting itself to Vista as one of a number of devices. The HP monitor control program refuses to believe that an HP monitor is plugged in. The Nvidia display driver doesn't even let me change options and Vista seems quite happy that nothing is wrong.
As for me, the picture is so good that I'm just about prepared to live with it for now. But I've lost a couple of hours trying to find out why something which should just be plug and play is nothing of the sort.
'tis a driver thing. I've managed to track down a set of NVidia drivers that makes the monitor mostly work.