Apparently PG Offline doesn't like the messages.db3 file set to "read only"?
I archived a group and didn't want the file (a bit over a terrabyte in size) corrupted. but alas, PF Offline crashes after a brief time after it lists messages (or tries to do anything, actually).
Removing the "read only" flag on the db3 file restores PG Offline to a happy state again. Not a complaint necessarily, just logging and noting behavior.
UPDATE: Under > File >Options > Misc the setting "Mark message as read after [5] sec." Apparently PGO throws a tantrum when it can't?
SQLite does its own internal housekeeping for which it requires write access.
You cannot "read" an SQLite database in read-only mode because it has to maintain for example, its lock table, last accessed date, etc, etc.
Cheers,
Wilson.