-
-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
companion as a portable install in Windows #5650
Comments
That's a good workaround for our current condition I was looking to avoid multiple installs and have have the multiple instances self contained |
Might need to be a little more specific as to use case. As individual minor
version installs... i.e. 2.8.x, 2.9.x are effectively self contained, as
they don't even share Companion settings. You probably just can't, for
instance copy the install folder to a flash drive and in doing so copy the
program AND settings in one neat bundle. Could probably do something using
the PortableApps launcher packager though.
…On Wed, 6 Nov 2024, 7:48 am alfredborges, ***@***.***> wrote:
That's a good workaround for our current condition
I was looking to avoid multiple installs and have have the multiple
instances self contained
—
Reply to this email directly, view it on GitHub
<#5650 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJ66KLR4RLI7X5MCMW5DLTZ7E4J5AVCNFSM6AAAAABRG3DQPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJYGIYTGMBQGQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Not clear as to your point I try to have a folder for each firmware revision that I've installed on a radio |
My point was/is that you merely have to install them to separate folders, and since they each use their own major and minor version number when saving settings in the registry (i.e. 2.9, 2.10) they are effectively isolated from one another.
Or, it is possible to wrap stuff using the PortableApps.com launcher to make an app AND settings self-contained... (within reason - some apps will still need some external dependencies installed). i.e. if you trust some random stranger on the internet... 😇 ... below is a self-extracting package for the Win64 EdgeTX Companion 2.10.5, created using the PortableApps.com launcher and installer toolkits... First time you run the app, it will create a Data folder in that same folder, and keep a private copy of the registry settings it loads into memory, and removes from memory every time you run that app. Configuration for the launcher is in the App\AppInfo\AppInfo.ini and App\AppInfo\Launcher\CompanionPortable.ini files. Would only need a couple of minor tweaks (basically just the version numbers changed) so that the launcher was correct for the different version of Companion being bundled. The zip file is the same content as the self extractor, just not an executable, if you prefer to check things out first ;) Self-extracting package - http://files.portabledev.xyz/f/0564eb9b0b964442b969/ |
Is there an existing issue for this feature request?
Is your feature request related to a problem?
Different firmware versions require different companion versions to manage in Windows. So in Windows you can have two or more versions of companion installed on every PC you use to manage edgetx radios
Describe the solution you'd like
It would be great to have the option of a "portable" install , so you could manage several firmware versions without a full install. This appears to be the behavior in the Linux version
Describe alternatives you've considered
1-Run the Linux version
2- Go ahead and install multiple versions of companion
Additional context
I manage my edge set ups by creating edgetx firmware/radio folders into my gdrive. That way I can manage them on different computers. With a portable install, you could also drop the right windows companion version in the gdrive folder and make it truly portable
The text was updated successfully, but these errors were encountered: