N
News Reader
Hi,
A week or two ago I ran Windows Update. I hadn't updated drivers in a while
so when it offered me a new NVIDIA driver, I installed it. The driver
version is now at 4.5.2.3 and dated as 7/28/2003. It also installed some
desktop display manager thing that runs in the system tray.
The problem is that now my power management isn't working. I have my screen
saver set to activate after 15 min. and I have the display set to go into
power saving mode after 30 min. and this was working fine before I updated
the driver. Now, it doesn't happen at all. The screen saver goes on, but the
display doesn't go into power saving mode.
Once or twice I went into the power management control panel, changed the
timeout to something else, hit "apply," changed it back to 30 min. and hit
"apply" again and I think that made it work temporarily, but after I
rebooted it didn't work anymore.
Has anyone else had this problem? Any suggested fix aside from resetting
this after each reboot? I suppose as a worst-case option I could run some
quick registry script on startup to change this value if that would help.
Thanks
A week or two ago I ran Windows Update. I hadn't updated drivers in a while
so when it offered me a new NVIDIA driver, I installed it. The driver
version is now at 4.5.2.3 and dated as 7/28/2003. It also installed some
desktop display manager thing that runs in the system tray.
The problem is that now my power management isn't working. I have my screen
saver set to activate after 15 min. and I have the display set to go into
power saving mode after 30 min. and this was working fine before I updated
the driver. Now, it doesn't happen at all. The screen saver goes on, but the
display doesn't go into power saving mode.
Once or twice I went into the power management control panel, changed the
timeout to something else, hit "apply," changed it back to 30 min. and hit
"apply" again and I think that made it work temporarily, but after I
rebooted it didn't work anymore.
Has anyone else had this problem? Any suggested fix aside from resetting
this after each reboot? I suppose as a worst-case option I could run some
quick registry script on startup to change this value if that would help.
Thanks