I've been testing the new ForceWare 91.31 beta drivers for a few days now. One thing that's starting to get really irritating is, for lack of a better description, an SLI nag screen



This comes up on every log on. At no point has this system run in SLI mode, and I can find no way to make it stop. When you click on it, it takes you to NVIDIA's official SLI homepage. Although this is almost certainly a bug in the new control panel, I feel like it's nagging me to buy another card. It may as well say "Warning! You could be running faster graphics. Click here to buy another card.".

Incidentally, the new control panel, which is supposed to be an answer to ATI's Catalyst Control Center, is terrible. Where as ATI’s CCC was much smarter and easier to use than the old Control Panel, with NVIDIA’s new Control Panel one has to navigate through numerous "user friendly" menus to get anywhere. It's no more explanatory than before, so settings will still be ambiguous to anyone who doesn't already understand what they do. I normally embrace changes when everyone else is afraid of them (CCC is an example), but this is one example where I will definitely be making use of the option to the traditional control panel.

Thats what you get for running a SLI compatible board and not actually running it.... You can disable any bubble message from control panel. That specific one is in Display>>>Settings>>>Advanced>>>general tab (maybe)

Interesting theory...you're suggesting that because it's SLI compatible...I should go and buy another card and run SLI?

I have no idea where you're suggesting it's done, but nothing I could find would disable the tray popup (short of disabling all tray popups).

How?

And ugh, tht popup is really annoying, it appears on mine and i dont even hav an SLi mobo!! Grr

Roz

__________________
"If it ain't broken, dont fix it" ;-)

If I've helped you, add to my reputation in the top right (the picture of scales).

I can't remember now how you switch back to classic; an option from the View menu maybe?

Hopefully they'll fix this in the next version. It seems odd that it 91.31 was WHQL certified without any of the driver engineers noticing the bug.