Ticket #5258 (closed: fixed)
Logic of Windows Installer Warnings
Reported by: | Owen Arnold | Owned by: | Owen Arnold |
---|---|---|---|
Priority: | major | Milestone: | Release 2.2 |
Component: | Mantid | Keywords: | |
Cc: | russell.taylor@… | Blocked By: | |
Blocking: | Tester: | Dereck Kachere |
Description
Suggested by Russell Taylor that we should try to distinguish between a firt-time install and what looks to be an install with a previous mantid instance.
We can probably do this by checking to see if the c:\mantidinstall directory exists as well as the existing check for Uninstall.exe.
Change History
comment:2 Changed 8 years ago by Owen Arnold
refs #5258. Better checking for old style install.
Changeset: bfc8e7785a0e4b67bef04b3588db223dd83eaf6e
comment:3 Changed 8 years ago by Owen Arnold
- Status changed from accepted to verify
- Resolution set to fixed
Tester:
Here are some tests to conduct on Windows
1) On a clean machine, Should NOT get a YES/NO message box about old style previous installs.
2) On a machine that has had the new installer-style Mantid already installed (v2.1 and up) should NOT get a YES/NO message box about old style previous installs.
3) On a machine that already has the old style mantid MSI installed (v.2.0 and below) should get a YES/NO message box about old style previous installs.
comment:4 Changed 8 years ago by Dereck Kachere
- Status changed from verify to verifying
- Tester set to Dereck Kachere
comment:5 Changed 8 years ago by Dereck Kachere
- Status changed from verifying to verify
- Tester Dereck Kachere deleted
Fully uninstalled Mantid; the Uninstall.exe is no longer present, nor was the c:\mantidinstall directory itself.
(Clean machine) Mantid v2.1.1430 - Yes/No option NOT there. (Clean machine) Mantid v2.1.1 & v2.1.0- Yes/No option IS THERE.
(Machine with v2.1 and up) Mantid v2.1.0 to v2.1.1430 - Yes/No option NOT there.
(Machine with v2.0 and below) Mantid v1.29.12931 to v1.30.14858 - Yes/No option NOT there but going from v1.29.12931 to v2.0.1 requires removal of previous versions via Control Panel before continuing with the install.
comment:6 Changed 8 years ago by Dereck Kachere
- Status changed from verify to reopened
- Resolution fixed deleted
comment:7 Changed 8 years ago by Owen Arnold
- Status changed from reopened to accepted
I've spoken to Dereck about this. There was a problem with my description. I still think that this is fixed.
comment:8 Changed 8 years ago by Owen Arnold
- Status changed from accepted to verify
- Resolution set to fixed
comment:9 Changed 8 years ago by Dereck Kachere
- Status changed from verify to verifying
- Tester set to Dereck Kachere
comment:10 Changed 8 years ago by Dereck Kachere
- Status changed from verifying to closed
Yes, I misunderstood description; everything is working as it should.
comment:11 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 6104