Page 1 of 1

Synchronising settings using 'mklink' command

Posted: 29 May 2023 05:34
by wagojo
Hi everyone

Is it possible to use the 'mklink' command to target/link the entire Calico Pie\Family Historian folder rather than having to create targets/links for every folder of interest e.g. Calico Pie\Family Historian\Autotext, Calico Pie\Family Historian\Plugins, Calico Pie\Family Historian\Source Templates etc?

When I try at this level FH7 will not open. The command line I'm using is: mklink /J "c:\ProgramData\Calico Pie\Family Historian" "C:\Dropbox\!Mackie-Jones Family History\2 DATA FILES\SETTINGS SYNCHRONISATION\Family Historian"...

Any thoughts?

Cheers
Wayne

Re: Synchronising settings using 'mklink' command

Posted: 29 May 2023 05:56
by wagojo
... just a bit more background: I'm wanting to share these settings between two PCs so I can work on either with up to date customisations, e.g. source templates. Interestingly - if I use the 'mklink' command to create a target/link just for the Source Templates folder in ProgramData and open FH none of my customised templates appear. I'm obviously doing something wrong!

Cheers
Wayne

Re: Synchronising settings using 'mklink' command

Posted: 29 May 2023 07:01
by johnmorrisoniom
I have done this, but targeted the entire Calico Pie sub folder in the Program Data Folder

The real Calico Pie folder is on One Drive and can be seen by both other computers that I use (I have 2 licenses)

John

Re: Synchronising settings using 'mklink' command

Posted: 29 May 2023 07:35
by Mark1834
Have you selected "Run as administrator" when opening the command window to create the junctions?

It's personal preference how many folders you link. The top level folder contains a lot of files, so it's a balance between coverage and speed of syncing. A lot of people are still on internet connections that only offer relatively slow uploads, and if that is the case you may find selective linking is more convenient.

Re: Synchronising settings using 'mklink' command

Posted: 30 May 2023 00:29
by wagojo
Hi Mark and John

Thank you for your replies. Everything is working fine now! A combination of 1) not running CMD as administrator, and 2) a typo! :-)

Cheers
Wayne