• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

A quick question

A

aaroncohn

Junior Member
I have my own theory on the subject, but I'd like to know for a fact why some programs require the user to reboot his/her machine. Can the same process be achieved by simply logging out and then back into Windows? I use XP pro. Thanks!
 
Not a quick question as you might think. A couple possibiltities is that new DLL files are being installed, Registry needs modified, a number of possibilities.

Maybe you are installing software which updates windows to accept the program....

What exactly are you trying to do?
 
I'm simply trying to understand why a system reboot is required after certain changes are made. That's all. Also, why would adding new DLLs require a reboot? Programs call functions from them just as easily without rebooting. I know, because I am a programmer and have added several DLLs without rebooting.
 
Like freakyguy said, it depends. If program installed a new service that service won't be started until the system is rebooted. Other times programes add themselves to the "runonce" registry key, so that they can do some initialization next time computer is restarted. Also, things like device drivers are loaded way before the user logs in and therefore won't take effect until full restart.

On the other hand, "restart" option sometimes is added by programmers to the installshield script just "to be on the safe side". If thats the case it can be safely ingored, even without loggin in/out.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top