Administrative installation adds inappropriate registry entries

[Richard Haselgrove]

Running the installer with the '/a' (administrative installation) switch should not make changes to the local sysem registry.

Testing with both v6.4.5 and v6.6.10, I found that both INSTALLDIR and DATADIR were set to point to the network server image directory - this would break any running BOINC v6 on the workstation used for network upload. Fortunately I was running BOINC v5.

However, the administrative installer does not read back either registry key for subsequent installations - it defaults to the root of the first available mapped network drive.

An administrative installation should either make no local registry changes at all, or maintain and use its own ADMININSTALLDIR key.

Also, the final screen (attached) on the test machine (Windows XP SP3, workgroup) is contradictory - if the installation was successful (as it appears to have been), why am I being directed to run a repair tool from add/remove programs?

[Richard Haselgrove]

Admin setup - final screenshot

[Nicolas]

"InstallShield? wizard" is an implementation detail, internal and technical information the user doesn't care about. "BOINC installation" finished, not "InstallShield? wizard".

[romw]

Punting setup bugs to 6.10.

[Richard Haselgrove]

Following an enquiry about admin setups at SETI, I tested the v6.2.19 installer: yes, it modifies the local registry too. Just warning people in case they decide not to wait until v6.10.x before trying their next admin setup.

[Christian Beer]

Is this fixed in 6.10? Please reopen when not.

[Richard Haselgrove]

Tested both 6.10.58 and 6.11.7 under Windows XP. Problem remains as originally described. Reopening ticket.

[romw]

Setup bugs are being punted to a future release. This work item should be completed with the new open source installer.

[Richard Haselgrove]

Behaviour remains the same in v7.0.64