BMS Updater Note! [copying of config files]
-
Yes. You can copy paste everything in the config folder in order not to loose your settings, but the Falcon_BMS.cfg has to be checked with the new stock installed one of course…and dont copy paste the Setup.ver.
Dont die, you are young :mrgreen:
-
Well in fact, you should NOT copy everything in the config folder if you want to backup your settings. Besides the already mentioned “Setup.ver” file, there are other files in there as well which should be handled purely by the installer.
But let’s do it the other way round and list the files that you CAN backup:
<callsign>.* –- your personal settings, logbook etc.
<whatever>.key — any custom keyfiles that you use
axismapping.dat — the joystick mapping file
joystick.cal — the joystick calibration data
phonebkn.ini — your comms phonebook
windowconfig.dat — external window configuration
The following files MIGHT be copied, but it’s actually better NOT to copy them, so that you get the latest versions:
dx9display.dsp — the display config
ews_def.ini — the defaul ECM settings
falcon bms.cfg — the BMS config file
mfd_def.ini — the default MFD pages setup
Files which are NOT listed here should NOT be copied under any circumstances. And yes, it might be a good idea to separate the files a bit better in the future. ;)</whatever></callsign>
-
Wonder if this backup could be part of the update process as an option?
-
But let’s do it the other way round and list the files that you CAN backup:
This would make a great sticky as the question comes up quite often.
-
+1
-
-
.key should not be copied because new commands might exist in updates and you would miss them
-
How about if the user/config would be reorganized so that only really configurable (and copyable) files would be in one directory, and the known version dependent or irrelevant files would be in a sister-dir?
-
.key should not be copied because new commands might exist in updates and you would miss them
<whatever>.key –- any custom keyfiles that you use</whatever>
How about if the user/config would be reorganized so that only really configurable (and copyable) files would be in one directory, and the known version dependent or irrelevant files would be in a sister-dir?
And yes, it might be a good idea to separate the files a bit better in the future.
-
.key should not be copied because new commands might exist in updates and you would miss them
I would like to know which new commands might exits since U1 because I always use the same key file (I’m sure that most BMS users do the same).
If there are no new commands, I’ll appreciate if in the future versions that info will be listed in changelog so people be aware. -
Hi A.S. and Dunc, personally i stick to logbook, phonebook and keyfile ive modded to copy into the new install. Copying config files is ok if your machine and OS drivers havent changed, but knowing how Micro… love to play with stuff I personally would say it isnt advisable.
By the way Dunc, if your interested done a test of BMS on Windows X this week and although its in beta it works fine. Only bugs in it are pitch roll and yaw trims lock on full for some reason. Mayb cured when the final version goes on the shelves.
-
Weird.
I have been copying and pasting my config folder since U1. In fact since F4 in 1998.
What bad stuff should I be looking for. I am experiencing no problems that I know of…… or perhaps I have and did not know it was from this practice..key should not be copied because new commands might exist in updates and you would miss them
I would for sure take the chance and copy and paste my callsign.key file. It took days to build and I would not redo it from scratch every time BMS got patched. In that custom situation it would be easier to will deal with the conflicts as they arise. If one was using Duncs key file, as is, then I would not bother to copy it.
-
But let’s do it the other way round and list the files that you CAN backup:
<whatever>.key –- any custom keyfiles that you use</whatever>
Already stated that custom key files are ok to copy
-
I wonder if I have a related issue, though I did not copy or backup config.
I “enlisted” with the 1-6 Installer. I can’t get 7 to install. I’ve downloaded it more then one. I see it listed in the correct file(with the multipart base and through update 6) but the Updater just doesn’t list it in the “downloaded” column -
Look at my hotlist I have a base + u1-u7 package ready and waiting.
-
Definitely get the 1-7 installer from Arty’s hot list.
You’ll never be MP compatible if you’re on 6
-
Thanks, D, and Arty, I’m glad you posted as there are LOTS things on your Hotlist I will be investigating.
You mention the Base + 1-7 in your post. That one is preferable to the “Full” one listed right by it? Also, do you have to do a full uninstall of Base Plus 1-6?
Thanks for the help! -
Thanks, D, and Arty, I’m glad you posted as there are LOTS things on your Hotlist I will be investigating.
You mention the Base + 1-7 in your post. That one is preferable to the “Full” one listed right by it? Also, do you have to do a full uninstall of Base Plus 1-6?
Thanks for the help!no you don’t have to uninstall it works. It actually overwrites the files so you will be ok. I personally tested it with base u1-6 and with a fubared one by one installed u1-7 to install on top of it and it worked like a charm. I even tested it on a from my package install but the files got corrupted by time and usage and it worked just fine.
Have in mind those are if u actually know the tips and tricks of Falcon in case u don’t than better uninstall and install from the package I provided.
-
no you don’t have to uninstall it works. It actually overwrites the files so you will be ok. I personally tested it with base u1-6 and with a fubared one by one installed u1-7 to install on top of it and it worked like a charm. I even tested it on a from my package install but the files got corrupted by time and usage and it worked just fine.
Have in mind those are if u actually know the tips and tricks of Falcon in case u don’t than better uninstall and install from the package I provided.
Thanks, Arty. I definately don’t know all the tricks so I will probably uninstall, with some trepidation. I had a lot of trouble with my initial setup, controller-wise, and don’t want a repeat!