Alex Fetters 6 discussion posts
|
I am migrating between PCs and trying to pull my settings over. I exported my CF settings on PC A and tried restoring them on PC B. I get an error message:
Followed by: It looks like a similar error was reported here: https://www.clipboardfusion.com/Discussions/View/get-error-every-time-cf-is-run/?ID=d53a23d1-2137-4e06-8c88-67a07463baae It looks like it should have been resolved, but I'm not sure. I'm running 5.4.1. I've attached the settings I'd like to restore. • Attachment [protected]: ClipboardFusion_PC_A.reg [14,794 bytes]
Sep 27, 2018
• #1
|
|
It's looking for the database in C:\Users\fettersa\AppData\Local\ClipboardFusion. If that path doesn't exist any more, that would cause the error to be shown.
If you edit the path in line 67 of the .reg file (use Notepad), or just delete that whole line, it should restore correctly. Sep 27, 2018
• #2
|
Alex Fetters 6 discussion posts
|
I removed the line, tried to restore, and it failed in the same manner. I then put the line back, confirmed that the path indicated by DatabaseLocation exists and tried again: same result.
Sep 27, 2018
• #3
|
|
I've just tested by removing the entire database location line from the backup and it restored without errors. Did you still get an error with that line removed? Or are some settings just not restored?
Sep 27, 2018
• #4
|
Alex Fetters 6 discussion posts
|
With the line removed I still get the error message:
It looks like maybe some of the settings restored as I noticed the "Options > Start with Windows" became checked. I am missing my Hotkey settings though, so I'm in an indeterminate state right now. • Attachment [protected]: ClipboardFusion_PC_A_db_removed.reg [14,644 bytes]
Sep 27, 2018
• #5
|
|
Ok, it looks like for some reason the restore process doesn't work for the hotkeys. Can you try this instead?
Oct 2, 2018
• #6
|
Alex Fetters 6 discussion posts
|
That worked great! Thanks for your help.
Just curious if this is considered a bug and will be fixed in future releases? Oct 2, 2018
• #7
|
|
Definitely! It's already on our list, thanks for confirming that the workaround did the trick
![]() Oct 2, 2018
• #8
|
Was this helpful? ![]() ![]() | |