Hi,
On Sunday 10 July 2016 00:57:51 Kob S wrote:
> Running C:\gnupg2.1.13\gpg --expert --full-gen-key
>
...
> I suspect that gnuPG is looking at the same \AppData\Roaming\gnupg
> directory that is being used by gpg4win. If that is the case, is there a
> way to force gnuPG to use a different
>To avoid that you should specify --homedir c:\testhome or something on the
>commandline to 2.1 calls. Then it will use that as a different homedir.
>e.g.: gpg --homedir c:\testhome --expert --full-gen-key
This works now like a charm.
Thanks,
Rimma
Hello,
I am using gpg4win V. 2.3.2 on a WIN7 machine, but I want to test the gnuPG
2.1.13 on the same machine, using the CLI, without interfering with the
existing gpg4win installation.
I downloaded and expanded the gnuPG 2.1.13 Windows CLI archive into a new
directory, and made sure to fully
