From: John E. / T. <td...@td...> - 2008-08-07 15:43:52
|
Stephen Lee wrote: > "John E. / TDM" <td...@td...> wrote: > >> Now that you bring it up, I need to amend that to "the only registry >> entry created is for an entry in Windows' Add/Remove Programs". But >> everything else is stored in files -- a manifest of installed components >> and files for each installation is kept in the root of the installation >> directory, and a list of installations is kept in the user's Application >> Data folder. >> > > Err... May I ask why? > > If you want to make the install system-wide, you shouldn't need to > store informatin in the user's Application Data folder. > You misunderstand me. The installer does support both system-wide and per-user installations, and tracks up to two separate lists of installations per program instance -- system-wide installations (IFF the user has system-wide access rights) and current-user installations. The list of system-wide installations is stored in the "All Users" Application Data folder, and lists of current-user installations are stored in the users' specific Application Data folder. On pre-Win2K systems, everything defaults to system-wide. And all of the above happens with the help of NSIS' MultiUser.nsh. > If you want to make the install per-user, then a global Add/Remove > Programs entry is not appropriate. (I don't think there are per-user > entries for this, correct me if I am wrong) > You are wrong, in the case of 2k, XP and Vista. -John E. |