Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
Thanks Tony, As you're probably aware, modifying the path on NT/2k/XP/2k3 should be done by setting the value of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\PATH However, you can avoid a reboot by sending a WM_SETTINGCHANGE notification, e.g. SendMessageTimeout(HWND_BROADCAST, WM_SETTINGCHANGE, 0, (LPARAM)"Environment", SMTO_ABORTIFHUNG, 5000, &retval); More elaborate applications will make use of this notification to update themselves and don't even need to be restarted (unfortunately, cmd.exe is not one of them). As for LSASRV.DLL, I used handle from www.sysinternals.com to check on it and it's not in use when cvsnt isn't running so a reboot shouldn't be required to replace it on most systems (just stop the cvsnt services before copying the files during upgrades). As for MSI rebooting for no reason, that's entirely possible as I don't use it but it certainly isn't acceptable behaviour to force a reboot just-in-case. If you want to discuss this further or need extra clarification or even a helping hand, let me know and I'll contact you via e-mail. Cheers, Rob "Tony Hoyle" <tony.hoyle at march-hare.com> wrote in message news:dnupkh$mur$1 at paris.nodomain.org... > Robin McLeod wrote: >> Can somebody please clarify why exactly a reboot is required after >> installing on NT4/2k/XP/2k3? The wiki claims that this is a path issue >> but that would only apply to 9x/Me. >> > Those all have paths too (modification of the system path would require a > reboot - cvsnt used to do that a year or so ago), but that's not the > primary issue. The main one is the installation of the LSA helper DLL > that allows pserver & sserver to work correctly. > > Also, MSI likes rebooting, and will do it at the slightest provocation. > > Tony