Apparently, the Windows installer no longer imports settings.reg to the registry. Only customized installers does. I believe older clients did and I think the installer should. See also Issue 13225.
nsis does not have direct support for importing to the registry from a .REG file. In general, those folks seems not to like those solutions. Instead, there's a hack that converts from .REG to nsis format, see: http://nsis.sourceforge.net/Reg2Nsis_-_convert_registry_info_into_NSIS_commands I like .REG files, though. The difference between program logic and a data format might be subtle, but is real. Since customers needs to edit the registry data in order to create customized clients, it's much easier for them to work with the .REG than with NSIS program code. Besides, it's good if we can change the installer without re-train customers. Additionally, one way of working is to create settings.reg by exporting from the registry. The earlier installer called "regedit /s <file>". I think we should move to reg.exe instead, since it's a real console/command line tool. Included with XP and later.
Fixed in 25571.
Did not work when I tried with build 3671.
(In reply to comment #3) > Did not work when I tried with build 3671. Works, but since we only have a 32 bit client and the Win 7 machine in the lab is 64 bit, the settings (correctly) ends up below Wow6432Node.
Verified on Vista.
From bug 2344, does not work on XP Embedded, since it lacks the reg.exe command.
(In reply to comment #6) > From bug 2344, does not work on XP Embedded, since it lacks the reg.exe > command. Switched to regedit.exe in 26096. Need to re-test on all Windows platforms.
Works fine now. Tested on XP, XPe, Vista, 7.
settings.reg doesn't seem to get uninstalled.
(In reply to comment #9) > settings.reg doesn't seem to get uninstalled. r26149.
Retested on XPe, XP and 7.
