Page 2 of 2

Re: porting a database and configuration on other PC

Posted: 03 Mar 2014, 08:50
by ik2egl
hi Terry

I missed to open the database form the file menu (action which permit to have diffent database - you wrote it in the manual ! - ((I wrongly thougth that db path was embedded in the config files !!!)) :lol:

SO

copy the db.sqllite, copy the config files and once run log40 open the *.sqllite where it is located : easy !!
tnx

Re: porting a database and configuration on other PC

Posted: 08 Mar 2014, 17:23
by N5INP
I'm trying to move my entire ham radio ops/setup also to a more powerful computer I have (6 core vs. 2 core). I don't want to do it all in one day, so I'm trying to start with the "hardest" apps first. I read this thread and copied the files shown in the attached pic.
You need to copy:
config.xml
communicatorconfig.xml
all users modified files (files that ends with _user)
log4om_files_pic.jpg
log4om_files_pic.jpg (80.97 KiB) Viewed 6879 times
I copied all those files and put them in the correct places on the new system.

The database looks OK, but most of the settings in the tabs are not carried over such as cat & cluster, QSL & labels, external sources, and others. My station call is OK, but how do I get all the other settings to carry over? Did I miss some files?
Please take note you should revise the whole configuration to check paths
I have no idea what "revise the whole configuration" means in terms of what I need to do on the new machine. Need help with that instruction perhaps?

Re: porting a database and configuration on other PC

Posted: 08 Mar 2014, 22:28
by K7PT
but how do I get all the other settings to carry over? Did I miss some files?
Some settings are currently not saved. :roll:
I have no idea what "revise the whole configuration" means in terms of what I need to do on the new machine. Need help with that instruction perhaps?
You need to check the paths of the LOTW temp file and any the paths in your config settings to make sure they are correct to the new system. ;)

Re: porting a database and configuration on other PC

Posted: 09 Mar 2014, 00:49
by N5INP
OK, that explains it. :? I'm not as dumb as I thought I was this morning. :lol:

Re: porting a database and configuration on other PC

Posted: 10 Mar 2014, 23:18
by N5INP
K7PT wrote:
but how do I get all the other settings to carry over? Did I miss some files?
Some settings are currently not saved. :roll:
Wait a minute ...

If that is so, then how can the program start each time and remember all the settings on the current computer, that are not transferring to the new computer? There must be some files I have missed. :roll:

Re: porting a database and configuration on other PC

Posted: 11 Mar 2014, 00:25
by IW3HMH
When you move the configuration file, Log4OM moves your actual configuration. Well, simple? :) not so simple...

Your current configuration means a lot of informations like PREFERENCES, station settings, clublog passwords, colors, QRZ.COM settings and many other things.
Those preferences are SAVED with Log4OM and moved with the config file (and the other files you're moving out). You will find them on the second pc.

BUT there are a couple of settings that are RELATED TO YOUR SPECIFIC PC, that must be updated in order to make Log4OM working correctly. As example:
COM PORT used for CAT system
Path to log file (eg. c:\mylog\my_log_file.sqlite) that can be different in the other PC
Path to LOTW TQSL.EXE (c:\programs\ARRL\...)
Path to backup folder
Port used by rotator software
IP address of your remote hamlib instance

When you move your config file all those settings are moved with, so you need to fix them.

There are also some "user files" that you can customize. As example, when you change the visualization layout of a specific grid, a something_user.xml file is created in your config folder, and kept between new versions and upgrades. This file should be moved too, with your config file, to restore your views.

So, to move configuration you should:

1) copy config.xml and communicatorconfig.xml
2) check all paths in log4om and communicator to be sure that are still valid in your new PC
3) move all files ending with _user.<something>, that contains your personalized settings (bandplan, band list, mode list, view configurations... almost everything is user configurable and persistable in Log4OM :)
4) move your audio file (for voice parrot function), also stored in the Log4OM settings folder

hope this helps

Re: porting a database and configuration on other PC

Posted: 13 Mar 2014, 15:29
by N5INP
Thanks, I got it done. Mostly by moving the files but some by brute force (pulling up a couple of menus and comparing my old settings on one PC screen with the settings on the other PC screen). :)

All is working now.

Re: porting a database and configuration on other PC

Posted: 13 Mar 2014, 15:30
by G4POP
Now fully documented in the user guide