Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I am using the latest commercial version of Qiqqa on my laptop ...How can I install v82 on my new laptop and transfer a copy of my PDF and work to the new one? #361

Open
emanelbanna opened this issue Oct 7, 2021 · 4 comments
Labels
📖documentation Improvements or additions to documentation 🤔question Further information is requested or this is a support question

Comments

@emanelbanna
Copy link

No description provided.

@GerHobbelt GerHobbelt changed the title I am using the latest commercial version of Qiqaa on my laptop ...How can I install v82 on my new laptop and transfer a copy of my PDF and work to the new one? I am using the latest commercial version of Qiqqa on my laptop ...How can I install v82 on my new laptop and transfer a copy of my PDF and work to the new one? Oct 10, 2021
@GerHobbelt
Copy link
Collaborator

Ok, need to ask before I can answer this one:

You have two machines, one already running Qiqqa, with your libraries on board, and you intend to use Qiqqa on a second machine, correct?

(I assume the answer is YES but I'ld better check to preclude misunderstanding.)

Second question: do you intend to use Qiqqa on both machines or do you intend to move from the 'old one' to the 'new one'. In other words: do you intend to work on two machines at the same time or will you switch machines and keep working on a single machine only (as far as Qiqqa is concerned)?

This is relevant because you'll need to set up some type of share/sync mechanism in the former case, while the latter could be accomplished by copying your Qiqqa Base directory contents to the new machine.

Let me know which of these scenarios you are looking for so that I can provide you with a suitable process to achieve your goals. 👍

@GerHobbelt GerHobbelt added 📖documentation Improvements or additions to documentation 🤔question Further information is requested or this is a support question labels Oct 10, 2021
@emanelbanna
Copy link
Author

Hi,
Thanks for your reply
Yes the first question is right. I have two machines one already running Qiqqa v79s with my libraries (I synced them last time from one week just before shut down of the site) and a new machine, and I intend to use Qiqqa new version v82 on both machines ( v79 has some troubles as sniffer stop working ) and restore my library and work on the new one
So,
first, how I safely transfer from v79 to v 82 on the old machine with my work and libraries moved safely.
Second, how I use v82 on the new machine with my work and libraries on it.
Thanks in advance

@GerHobbelt
Copy link
Collaborator

To answer the first part (upgrading v79 to v82) the short answer is they are binary data compatible so you can install v82 over the existing v79 installation and access your libraries on the local machine as Qiqqa will auto-discover your libraries.

Please read the comment at #358 (comment) -- if you feel a little adventurous, you can skip step 1 in there (creating a backup) but I would personally take the time to create a copy of all the content of that Qiqqa Base Directory: it's a relatively cheap safety precaution as it will take time (computer busy copying files), but then you can go and do something else (unattended copy).

I'll address the second part in a next comment (how to sync OSS Qiqqa V8x installs on multiple computers) as it's still a bit convoluted and I'm running out of time right now (RL stuff 😉 )

@emanelbanna
Copy link
Author

Thanks a lot. It's really appreciated.
Plz don't forget to answer the second question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📖documentation Improvements or additions to documentation 🤔question Further information is requested or this is a support question
Projects
None yet
Development

No branches or pull requests

2 participants