Build: 5/21/99 SeaMonkey build 1. Use jars, http://jimbob/jars/a_winreg_createkey_setrootkey.jar http://jimbob/jars/a_winreg_setvaluestring.jar http://jimbob/jars/a_winreg_getvalue_setvalue.jar (the first two jars set up the third one) 2. Using the forms: v = winreg.getValue("Software\\WinReg Test Key\\subkey1\\subkey2", "the_name"); winreg.setValue("Software\\WinReg Test Key\\subkey1\\subkey2", "second_name",v); 3. Trigger jar files RESULT: Checking the Windows Registry shows that the value name, "second_name", was not set at "Software\\WinReg Test Key\\subkey1\\subkey2" from HKEY_LOCAL_MACHINE. There is no change. The Install.log shows: --------------------------------------------------------------------------- Acceptance: a_winreg_getvalue_setvalue --------------------------------------------------------------------------- Starting Installation at 05/21/1999 12:24:25 Finished Installation 05/21/1999 12:24:25 The installscipt appears to have executed and finished gracefully. However, it appears that the WinRegValue object was not created since it is not indicated here. Therefore, it makes sense that setValue() would not be successful since it uses the object from getValue(). EXPECTED RESULT: The WinRegValue object is created and indicated from the Install.log. setValue() is then able to create the value name at the specified key, and the Install.log reflects this success as well.

The winreg.getvalue and winreg.setvalue functions are currently not working. I've talked to Dan about the issues involved to getting these functions working properly. He said he's looking into it. Cathleen has suggested that xpinstall offer a winreg.setnumber() and winreg.getnumber(or similar) functions to cover the most widely used cases. I will add those when I get a chance.

I've added Install.SetValueNumber() and Install.GetValueNumber() functions. This should allow the script writer to cover most cases of manipulating the windows registry. I'm resolving this as fixed. Jimmy, when you are done verifying the new functions, please change the resolve status to REMIND, so we don't forget to do something about the Install.SetValue() and Install.GetValue() functions.

Build 6/16/99 Windows The new functions, Install.SetValueNumber() and Install.GetValueNumber(), are working as expected. This bug will be reopened, so Resolution can be set to REMIND per Sean's comment about Install.SetValue() and Install.GetValue().

Bug 10190 will be used to track the status of SetValue and GetValue. GetValueNumber and SetValueNumber work fine. Marking Verified.

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

REMIND is deprecated per bug 35839.

per comments, the scope of this bug is FIXED.