G
Guest
Any plans about reducing the number or reboot requirements? Because every
time I install a driver Windows Vista needs to reboot.
time I install a driver Windows Vista needs to reboot.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
J
John Boy
BillD said:Any plans about reducing the number or reboot requirements? Because every
time I install a driver Windows Vista needs to reboot.
This is not new in Vista. The computer has to
reboot after a driver installation so the driver
can be loaded. I realize there are some drivers
that will function with out a reboot, but it
depends on how it interacts with the kernel.
S
Stooovie
I don't think so...Vista (my installation of anything after 5270) doesn't
need to reboot after river installation, not even after graphic card driver
installation. Drivers load on the fly, at least for most of my devices.
need to reboot after river installation, not even after graphic card driver
installation. Drivers load on the fly, at least for most of my devices.
C
Colin Barnhorst
Yes. I was wondering what BillD and John Boy are seeing that I'm not. I
don't see a lot of reboots either. A lot of the drivers must be loading in
user mode.
don't see a lot of reboots either. A lot of the drivers must be loading in
user mode.
C
CH
I suspect this is in the category that your milage may vary, because I
haven't in several builds seen any reboot requirements for drivers and I
haven't seen any situations that are imposing reboots in other areas.
I know that the feature "Restart Manager" refers to restart to a program
that may be faultering and while it is far from perfect, its a very good
concept and it will get much better in time.
The idea for it and it's companion "Resource Exhuastion Detection and
Recovery" tries to monitor memory commit levels for stability.
I'm not sure which drivers might require a restart in concert with which
hardware, but have always harbored the impulse that if I install anything
and it is not working, a restart might help it engage or that a restart may
help period.
CH
haven't in several builds seen any reboot requirements for drivers and I
haven't seen any situations that are imposing reboots in other areas.
I know that the feature "Restart Manager" refers to restart to a program
that may be faultering and while it is far from perfect, its a very good
concept and it will get much better in time.
The idea for it and it's companion "Resource Exhuastion Detection and
Recovery" tries to monitor memory commit levels for stability.
I'm not sure which drivers might require a restart in concert with which
hardware, but have always harbored the impulse that if I install anything
and it is not working, a restart might help it engage or that a restart may
help period.
CH
G
Guest
CH said:I suspect this is in the category that your milage may vary, because I
haven't in several builds seen any reboot requirements for drivers and I
haven't seen any situations that are imposing reboots in other areas.
The sound blaster Live 5.1 drivers delivered by automatic updates, require
to reboot the system (I have the request to reboot). But It's possible that
this reboot request is a bug, because the sound after the driver installation
is activated (before driver installation Windows Vista is mute but after
installation completion I hear the Windows sounds).
So it's a bug?