Build: 6/16/99 SeaMonkey build 1. User trigger at http://jimbob/trigger2.html 2. Trigger jar, http://jimbob/jars/f_addsubcomp_regname_user.jar 3. "=USER=/" is used as show in the following: f = Install.GetFolder("Temporary", "f_addsubcomp_regName_user"); err = Install.AddSubcomponent("=USER=/"+regName, vi, jarSourcePath, f, "f_addsubcomp_regName_user.txt", true); RESULT: The component is added to c:\Temp\. The Version Registry shows: f_addsubcomp_regName_user RefCount (S)=1 Path (F)=C:\TEMP\f_addsubcomp_regName_user\f_addsubcomp_regName_user.txt Version (S)=1.0.1.1 The Install.log file shows: --------------------------------------------------------------------------- Functional: f_addsubcomp_regName_user --------------------------------------------------------------------------- Starting Installation at 06/22/1999 14:02:42 Item [1/1] Installing: C:\TEMP\f_addsubcomp_regName_user\f_addsubcomp_regName_user.txt Finished Installation 06/22/1999 14:02:42 EXPECTED RESULT: The component is installed and registered to the current user profile. The Install.log shows the correct path to the profile directory. NOTE: With the 6/20/99 Macintosh build, the installscript aborts gracefully. Due to a couple of test blockers, no more detail can be provided at this time.

=USER= and =COMM= say nothing about where the file is installed, they are used in the registry name argument and affect ONLY the registry name. If you want the file to by physically installed into the profile directory then you must use GetFolder("Current User") to do that. =USER= and GetFolder("Current User") should be used together, but since one was a 4.0 feature and the other 4.5 it isn't enforced. However, =USER= is in fact broken so I will leave this bug open for that. But the file itself went into the specified place and that's not part of this bug. Note that =USER= can be used in both StartInstall() and when adding files.

set target milestone to M15, per today's bug meeting.

Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall Engine

this is a low priority feature. bug meeting 3/20

cut feature putting on helpwanted

Taking advantage of new "Future" target milestone.

bug hasn't been touched since forever. is this bug still valid?

Don't need anymore