You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just logging this for the sake of it kinda, but also means I can keep a log of version numbers and their issues for reference.
v80s: Loses Watch folder on restarts, even if not launched on boot, added, run, closed, reopened, watch folder gone again.
I'm running Qiqqa in a virtualmachine Windows10 which seems to work fine, with the library location on my linux (host) drive which is made available to the VM as a mapped network drive, always in the same place (Y:/). The mapped drive location seems to be available immediately on startup, but just in case I disabled running Qiqqa at startup but that changed nothing.
Versions and key issues
v83: crashes all the time with object error. does textify & OCR properly (quite well? not perfectly? never finishes?) though.
v82: white pages. textify & OCR issues.
v80s: Loses Watch folder on restarts, even if not launched on boot, added, run, closed, reopened, watch folder gone again. textify & OCR work perfectly. Everything else works.
Cheers, hope you're well!
The text was updated successfully, but these errors were encountered:
SimonDedman
changed the title
Watch folder lost ever (Qiqqa) restart, v80
Watch folder lost every (Qiqqa) restart, v80
Jun 1, 2023
Edit: thought: it says I have read-only access to the library which AFAIK isn't an issue since the database is separate? Notwithstanding I should have write access to the library since I can make write edits on things in that mapped drive within windows explorer etc.
sorry, already brought this up in this megathread, though my setup has changed since the original nightmares, and I'm now running win10 in a virtualmachine, with the watch folder being in a permanently mapped drive (Y:/Galway/Papers). Do you think the inability to save watch folders has anything to do with my only having read-only access to the library?
I suppose this could be a solved problem, but I'm using v80 due to worse issues with v82 & 83:
v83: crashes all the time with object error. does textify & OCR properly though.
v82: white pages. textify & OCR takes forever/fails.
v80: Loses Watch folder on restarts, even if not launched on boot, added, run, closed, reopened, watch folder gone again
Hi Ger,
Just logging this for the sake of it kinda, but also means I can keep a log of version numbers and their issues for reference.
v80s: Loses Watch folder on restarts, even if not launched on boot, added, run, closed, reopened, watch folder gone again.
I'm running Qiqqa in a virtualmachine Windows10 which seems to work fine, with the library location on my linux (host) drive which is made available to the VM as a mapped network drive, always in the same place (Y:/). The mapped drive location seems to be available immediately on startup, but just in case I disabled running Qiqqa at startup but that changed nothing.
Versions and key issues
v83: crashes all the time with object error. does textify & OCR properly (quite well? not perfectly? never finishes?) though.
v82: white pages. textify & OCR issues.
v80s: Loses Watch folder on restarts, even if not launched on boot, added, run, closed, reopened, watch folder gone again. textify & OCR work perfectly. Everything else works.
Cheers, hope you're well!
The text was updated successfully, but these errors were encountered: