# File: /users/krowe/www/windows/admin_studio
# Author: K. Scott Rowe
# Time-stamp: <12/30/2004 10:24:25 krowe@rastan.aoc.nrao.edu>


#krowe Oct 13 2004: 
how does one convert HKCU to HKU (.default) when making and MSI package?
a copy of the MSI is kept in c:\windows\installer (its hidden) and when
a new user logs in the msi is executed and settings applied to that user.
This is how the repair process works.

#krowe Nov 23 2004: the addaware program has a sister program called 
addwatch which needs to be configured for each user.  Basicly, addwatch
wants to put a config file in each users Documents and Settings.  To get
around this they told us a way to have addwatch trigger a self-repair.

open the ism file in DEV Studio.
go to Application Data\Files and Folders.  Then in Destination 
computer's folders open AppDataFolder\Lavasoft\Ad-Aware and paste in
the config files (found in c:\documents and settings\mglenden\application data\lavasoft\ad-aware)

next, go to Organization/Components/AllOtherFiles/Registry Data.
Then in Destination computer's folders add a key in HKCU like
Software\Lavasoft and make a blank string value called something like
addwatch-self-repair.  then right-click the new value and select "set key path"

# krowe Mar 04 2004
if you find that a program is "repairing" itself when a new user logs in
and starts it, try doing the following...

  Look in the Windows Application Log and find the corrosponding error 
  with a really long like '{141BEAD3-3708-47D9-95D7-EF21CDA0E076}'
  Then open Developer and open Organization -> Setup Design and look 
  through the components like CreateFolder_Help and check the 
  Component Code for a match.
  These components can be removed from the package by right-clicking
  on the component and selecting Remove from feature.