Closed Bug 14800 Opened 25 years ago Closed 25 years ago

Version Registry: Absolute path registers into two places

Categories

(Core Graveyard :: Installer: XPInstall Engine, defect, P3)

All
Windows NT
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 12020

People

(Reporter: jimmykenlee, Assigned: cathleennscp)

Details

Build: 9/23/99 SeaMonkey build

1. From http://jimbob/triggers2.html, click drop-down button and select
   f_addsubcomp_regName_absolute.  Click Trigger case button to install.

err = Install.StartInstall("Functional: f_addsubcomp_regName_absolute",
                                       "f_addsubcomp_regName_absolute", vi, 0);
f = Install.GetFolder("Program", "f_addsubcomp_regName_absolute");
err = Install.AddSubcomponent("/"+regName, vi, jarSourcePath, f, jarSourcePath,
true);

RESULT:
The Version registry shows an expected node under /Version Registry.  There also
is a similar node found under Communicator similar to the following:

Subtree Dump of /Version Registry/Netscape/Communicator #19
--------------------------------
f_addsubcomp_regName_absolute
    Version (S)=1.0.1.1

EXPECTED RESULT:
Absolute path registry name installations are not registered under Communicator.

NOTE:
I cannot confirm this bug on a recent build of Linux because of a known
triggering bug.  This problem does not exist on Build 9/16/99.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 12020 ***
checked for duplication with bug# 12020
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall
Engine
Status: RESOLVED → VERIFIED
[bugday] verifying as duplicate. Same registry problem. Looks like shrir had
also verified but maybe bugzilla burped it to resolved on bulk move.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.