Registered Member
|
On my Win 10 PC I've put my KMM .kmy file in a Veracrypt encrypted container file, which I mount as drive k. KMM (Version 5.1.0-d60b0fa1e, installed a couple of years ago) happily opens the .kmy file.
I've now installed KMM (kmymoney5-mingw64-5.0.6-8.1-setup.exe from https://download.kde.org/stable/kmymoney/5.0.6/win64/) on a second PC (also Win 10 Pro), and copied the Veracrypt container file across to the second PC. On the second PC, I can open the container file and mount it as drive k: with VC perfectly ok, but when I start KMM, it fails to open and hangs, just displaying the splash screen. I’ve made a Windows batch file, and I call KMM with this line:
The following three error messages appear in the command prompt window:
If I simply start up KMM without any parameters, KMM starts perfectly ok to the Home screen, but if I then choose File/Open, navigate to drive k:, and select my .kmy file, I get a dialog box pop up with the message:
I've tried copying the container file again from old to the second PC in case it got corrupted - it still works on the old PC, but still fails on the second PC. What am I doing wrong? I’m presumably missing some vital component(s)? Has the .kmy file format changed from v5.0.6 to v5.1.0? Why are version numbers seemingly going backwards? I'm mystified. Can anybody help, please? Regards John |
Registered Member
|
Ah! Solved it. I don't understand why I managed to download KMM vVersion 5.1.0-d60b0fa1e a couple of years ago, but kmymoney5-mingw64-5.0.6-8.1-setup a couple of days ago. The version numbers seem to be going backwards. I uninstalled 5.0.6 and reinstalled 5.1.0. KMM now works properly.
Sorry to bother you. John |
Registered users: Bing [Bot], daret, Google [Bot], Sogou [Bot]