Bug #11234
closedInstallation Issue
0%
Description
I downloaded the latest Chirp for Windows, today. I launched the installation like always. I do not accept the defaults, instead I set a custom install path with the following naming scheme. C:\Program Files (x86)\CHIRP-next-2024-03-10
What changed tonight was... While I deleted the default CHIRP install folder, therefore what was left in the install path was C:\Program Files (x86)\ I accidentally pressed the ENTER key on my keyboard. But, instead of installing CHIRP into Program Files (x86) it started deleting all the existing files and folders as part of its install process. As quickly as I noticed this I cancelled the install via the Task Manager. And then proceeded to purchase a File Recovery Utility to recover 1,000's of missing files.
I realize that I triggered the installation, but I would have never imagined that the installation would start deleting in mass.
Is this by design or oversite?
Updated by Dan Smith 8 months ago
Yeah, if you give the installer a destination path that exists, it deletes that destination before re-creating and installing to it. It does that to make sure that there isn't anything left-over from a previous install, assuming you're installing over the previous. Even if you point it somewhere else, it needs to clear that location so that there aren't conflicting files that are pre-existing with what needs to be installed.
AFAIK, any installer would do the same thing and indeed, CHIRP just uses a standard installer tool to do its work. This has been how the tool we use to install has behaved as long as I can remember. Since it will let you install wherever you tell it, I'm not sure there's any way it can realistically do anything other than what it's doing now.
Updated by Ryan Stillnet 8 months ago
Dan Smith wrote in #note-1:
Yeah, if you give the installer a destination path that exists, it deletes that destination before re-creating and installing to it. It does that to make sure that there isn't anything left-over from a previous install, assuming you're installing over the previous. Even if you point it somewhere else, it needs to clear that location so that there aren't conflicting files that are pre-existing with what needs to be installed.
AFAIK, any installer would do the same thing and indeed, CHIRP just uses a standard installer tool to do its work. This has been how the tool we use to install has behaved as long as I can remember. Since it will let you install wherever you tell it, I'm not sure there's any way it can realistically do anything other than what it's doing now.
Dan, what installer are you using? I'm willing to take a look and see if there is an option to make it behave differently.
Do you need a privileged account to use the program on Windows? I'm guessing maybe, due to the driver access. If not, then one alternative would be to install without requiring the UAC prompt. Then the installer would not have access to the Program Files directory even if the user tried to use that.
Dan Smith wrote in #note-1:
Yeah, if you give the installer a destination path that exists, it deletes that destination before re-creating and installing to it. It does that to make sure that there isn't anything left-over from a previous install, assuming you're installing over the previous. Even if you point it somewhere else, it needs to clear that location so that there aren't conflicting files that are pre-existing with what needs to be installed.
AFAIK, any installer would do the same thing and indeed, CHIRP just uses a standard installer tool to do its work. This has been how the tool we use to install has behaved as long as I can remember. Since it will let you install wherever you tell it, I'm not sure there's any way it can realistically do anything other than what it's doing now.
Updated by Dan Smith 8 months ago
- Status changed from New to Closed
So, I've already made a change here. I look for the uninstaller in the destination directory and if it's there, I run it in silent mode. I like that in some ways and don't in others, but I'm going to try it and see if it ends up causing other troubles or not. If the user chooses to install to an existing directory with other stuff, we won't clear it, which is unfortunate. Also if the uninstaller fails for any reason then we could have issues of course. If there ends up being fallout from this then I'll have to switch back.
Also if you had installed to program files and then ran the uninstaller, it would end up nuking the whole thing anyway, so this isn't even a total fix.
I'm not really super excited about making other substantial changes to the installer if I can help it. 16 years of clearing the destination and this is the first such issue I've heard of, which I think means we are not being excessively irresponsible here :)
I'll mark this as closed as the latest build does the uninstaller thing now and hope that at least resolves the issue you ran into.
Updated by Jim Unroe 8 months ago
If you want to have multiple versions of CHIRP available on a Windows computer at the same time, my recommendation is to just grab the win64.zip version. You simply unZIP it anywhere convenient. No installation necessary. Just right-click the 'chirpwx.exe' and choose 'Create shortcut' to create a shortcut that you can copy/move to anywhere you want and rename it to suit your needs.
I add different versions all the time for testing. When it is no longer needed, I remove it without affecting any of my other versions.
Updated by Jeff Widgren 8 months ago
Jim Unroe wrote in #note-4:
If you want to have multiple versions of CHIRP available on a Windows computer at the same time, my recommendation is to just grab the win64.zip version. You simply unZIP it anywhere convenient. No installation necessary. Just right-click the 'chirpwx.exe' and choose 'Create shortcut' to create a shortcut that you can copy/move to anywhere you want and rename it to suit your needs.
I add different versions all the time for testing. When it is no longer needed, I remove it without affecting any of my other versions.
I really like this idea and will start using your suggestion.
Thanks
Updated by Jeff Widgren 8 months ago
Jim Unroe wrote in #note-4:
If you want to have multiple versions of CHIRP available on a Windows computer at the same time, my recommendation is to just grab the win64.zip version. You simply unZIP it anywhere convenient. No installation necessary. Just right-click the 'chirpwx.exe' and choose 'Create shortcut' to create a shortcut that you can copy/move to anywhere you want and rename it to suit your needs.
I add different versions all the time for testing. When it is no longer needed, I remove it without affecting any of my other versions.
Guys,
I have come to depend highly on Chirp for all my radios, and certainly appreciate all the work that you put forth into this project.
I realize that my method of install is an edge-case, and I don't expect mountains to be moved due to my experience.
Keep up the great work.
Jeff Widgren
(913) 908-8485