CurtC
December 6, 2000, 4:34am
21
Uniball wrote:
There’s a large number of reasons for the reboot, depending on the program. The most common one are registry issues, activation of new DLLs, memory usage and, above all, inicialization of new versions of the AUTOEXEC.BAT and CONFIG.SYS.
Win2k is back to using autoexec.bat and config.sys files? WinNT doesn’t have them, and 2k is just the new version of NT, so I am very surprised to learn that they’ve brought them back.
jrishaw
December 6, 2000, 6:57am
22
*Originally posted by astro *
In order to work properly, complex installed software programs need to re-initialize with the new drivers and various other software components in place and integrated into the system registery. The system needs to reboot for the changes to the registery etc to become active and for the program components to be recognized and load correctly.
Not once in my 10 years administering UNIX systems have I had to “reboot” after installing a program or package.
Maybe Microsoft should have done it the right way to begin with, eh.
