Project

General

Profile

Actions

Bug #3817

open

Windows installer deletes existing CHIRP version

Added by Brian Koontz almost 8 years ago. Updated almost 8 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
07/13/2016
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
(All models)
Platform:
Windows
Debug Log:
I read the instructions above:

Description

Not understanding the utility of wiping out an existing CHIRP installation. The installer not only wiped it out, but hung up on the COPYING file. (Yes, I had a backup, but still, I'm not seeing the necessity of doing this.) Daily version 20160713.


Related issues

Related to Bug #3309: Update wiped out all config filesNew02/10/2016

Actions
Actions #1

Updated by Jim Unroe almost 8 years ago

  • Status changed from New to Feedback

This has worked fine for my for over 4 years. You should not store you data files in the program folder. Create a CHIRP folder in you Documents folder and store them there.

Jim KC9HI

Actions #2

Updated by Brian Koontz almost 8 years ago

Yes I'm aware of that. At the least, stage the new installation first if it can't reliably install over an existing version (which it apparently can't ) or move the old installation out of the way. At the least, docs should state that the old installation will be wiped out, with no guarantees that an update will install properly.

Actions

Also available in: Atom PDF