Thread: New version of DRM removal tools ("DeDRM")
View Single Post
Old 09-23-2016, 04:08 AM   #738
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by 13xforever View Post
Not sure what you mean by this. I even cleaned up the app data and re-created everything from scratch, Kobo Desktop 4.0 creates the same DB as after migrating from 3.19. DbVersion is the same, the structure is mostly the same as it was since 3.17. Same content_keys, same master key generation function.
Kobo change the journal mode from "delete" to "wal". This is supported with SQLite 3.7 or later. Obok, the KoboTouch driver and all the other calibre plugins were using sqlite3 to access the database. On Windows, sqlite3 was built with a SQLite 3.6 library. When calibre tried to read the database, it gave an error because sqlite3 could not handle the WAL option. The error suggested the file was either encrypted or not a database. On the other platforms sqlite3, uses 3.7, so there were no problems.

I changed all the KoboTouch driver and other plugins to use apsw as this uses a later SQLite library and is what calibre uses for all of it's own database access. After making the appropriate changes to Obok, the books could be seen, but the DRM could not be removed. It could for a 3.19 database on one of my devices.

I can't check right now, are you sure it is the same DbVersion as 3.19? From memory, 3.19 would have been 126 or 127. 4.0 should be 129. That is what the devices use, and the desktop application is usually the same. I'll check when I get home, but there is something strange here.

What OS are you using?

Edit:

Just looked, the version of the desktop application is 4.0.5579. The database has DbVersion of 129. And I still have 3.19 on another machine. That has DbVersion of 125.
Last edited by davidfor; 09-23-2016 at 07:20 AM.
davidfor is offline