Last post on this issue.
* I cleaned ap again, and installed version 2.5.3 into a wsjtx253
folder, then version 2.5.4 into a wsjtx254 folder
* That worked, apart from some initial "stale lock file" complaints
that went away on retry. The Start Menu entry for 2.5.3 started
that version and the entry for 2.5.4 started that one
* The 2.5.4 entry was missing the Start Menu entries for uninstaller,
documentation and website, but the latter two appeared on their own
when I uninstalled 2.5.3 from Settings>Apps and Features
* The uninstaller for 2.5.4 nevertheless worked when I did so from
Settings>Apps and Features
Maybe something like that is all that's necessary to clear this one up -
the installer to suggest a different default folder for each version?
Alan G0TLK
On 31/12/2022 13:46, Alan Groups via wsjt-devel wrote:
Following a system clean-up I've looked a bit further into the weird
menu and other entries I found on my system and found the same effects
arising on version upgrade, so it's a repeatable issue:
*The Uninstaller*
* Following a system clean of WSJT-X, installation of v 2.5.4 and
after a reboot I uninstalled WSJT-X 2.5.4 using the uninstal link
under the Start button - it runs uninstal.exe
* WSJT-X went from the Start menu, the W10 apps list, Control
Panel>Programs & Features, and the registry
* The uninstaller therefore seems to be doing it's job, if run.
*Version upgrade*
I then installed version 2.5.3 and rebooted, followed by an upgrade to
version 2.5.4 by simply running the latter installer. This gave me:
* Start Menu - one entry labelled 2.5.3 that actually runs 2.5.4
* Registry - two entries, for each of 2.5.3 and 2.5.4
* Control Panel>Programs & Features - two entries in the list, one
for 2.5.3 and one for 2.5.4, both uninstalling only 2.5.4
* Settings>Apps & Features - same as Control Panel
The system entries are therefore incorrect, leading to user confusion
and for all I know potential W10 system issues as well.
*Diagnosis*
I don't believe the installer is running the working uninstal.exe nor
is it cleaning up system entries from the previous version, when a new
version is installed over the top of an existing version
*Suggested solutions*
* Advise users to run the uninstaller first, before version
upgrading; or
* Incorporate minimum necessary system entry clean-up into the
installer script; or
* If an ability to run multiple versions on one machine is required
then amend the installer script so that it handles the system
entries to have each version remaining entirely separate
Hope that helps!
Alan G0TLK
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
