Uninstalling deletes resource files?

Nigel Cunningham
Nigel Cunningham Member Posts: 181 ✭✭
edited November 2024 in English Forum

Hi all.

After having 'fun' this morning with the indexer continually crashing this morning (something about a corrupt database, but it didn't tell me which one), I thought I'd try an uninstall of the beta and reinstall of the latest stable. I got something of a shock when I discovered post-uninstall that the whole installation directory was gone and I needed to redownload 10GB of books. Ouch!

Two requests, as a result:

- If you get a corrupt database, could the log message (sorry, I haven't kept it) say which database is corrupt?

- If you uninstall could it please not delete the resource files?

Thanks very much, Logos, for a great piece of software. I know these are only minor downsides in comparison to the great features that are also there!

Comments

  • Dave Hooton
    Dave Hooton MVP Posts: 36,339

    - If you get a corrupt database, could the log message (sorry, I haven't kept it) say which database is corrupt?

    Not without increasing the volume of logged messages eg. writing to librarycatalog.db, writing to ...., writing to ..., ERROR  <crash trace!>

    The crash trace provides a meaningful sequence to the developers who don't really want us to mess around with the databases.

    - If you uninstall could it please not delete the resource files?

    That's a difficult one as Libronix has conditioned us that way, but it means it cannot be completely removed without deleting about 4 other folders (where are they?). With Logos4 it's also a case of not wanting users to mess around with data! Just remember to backup \Resources before you uninstall.

    Dave
    ===

    Windows 11 & Android 13

  • Nigel Cunningham
    Nigel Cunningham Member Posts: 181 ✭✭

    - If you get a corrupt database, could the log message (sorry, I haven't kept it) say which database is corrupt?

    Not without increasing the volume of logged messages eg. writing to librarycatalog.db, writing to ...., writing to ..., ERROR  <crash trace!>

    The crash trace provides a meaningful sequence to the developers who don't really want us to mess around with the databases.

    No. That's not necessary. Just add it to the error message itself. It doesn't need to be printed if there is no error.

    - If you uninstall could it please not delete the resource files?

    That's a difficult one as Libronix has conditioned us that way, but it means it cannot be completely removed without deleting about 4 other folders (where are they?). With Logos4 it's also a case of not wanting users to mess around with data! Just remember to backup \Resources before you uninstall.

    That's fine if you know ahead of time, but I was never given a clue (at least not one that I noticed). If not deleting the resource files isn't feasible, perhaps putting a nice, clear, attention getting message in the uninstaller would be a good fallback.

  • Dave Hooton
    Dave Hooton MVP Posts: 36,339

    That's fine if you know ahead of time, but I was never given a clue (at least not one that I noticed). If not deleting the resource files isn't feasible, perhaps putting a nice, clear, attention getting message in the uninstaller would be a good fallback.

    An uninstall is usually complete, although an option to save resources could be presented. Go to User Voice to make a suggestion.

     

    Dave
    ===

    Windows 11 & Android 13