Well, I've really written about "Symbolic links (if necessary)" string in my previous post, as petermad said. This option creates hardlinks and junctions when possible and symbolic links otherwise (e.g. hardlink can't be made on a different volume), and there are no cases where junctions/hardlinks are possible but symbolic links don't, therefore it has "(if necessary)".
But there are cases when relative symbolic links are not possible but absolute ones do, so "Relative symbolic links (if possible)" option has "(if possible)".
MVV wrote: 2020-01-03, 14:30 UTC
Thank you, Happy New Year!
And thanks for the translation. However I have a question: you have changed "if necessary" to "if possible" for symlink creation, and now your option has a bit different meaning. It is always possible to create a symlink (in case of NTFS target of course), but it is not always possible to create a hardlink, so "if possible" looks incorrect here. Please correct it.
2Fla$her
To my knowledge, no TC plugin or utility is digitally signed. In fact, why would/should they be signed? It just costs a lot of money and has very little to no benefit. Sure, UAC dialogs get a different appearance and anti-virus software seems to favor signed programs - especially ones with an expensive extended validation (EV) certificate. But apart from that, there's not much else.
Furthermore, Windows allows the execution of unsigned software (MS would be VERY fast to change their decision if that wasn't the case), so I'm wondering how exactly the report about the missing signature looks like, and if you changed some system setting that would require applications to be signed (I'm not sure there is such setting).
Regards
Dalai
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64