View Single Post
Old 02-28-2011, 12:42 PM   #6
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,694
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
The only functionality that has been lost with Mobi2Mobi is the ability to modify the TTS Flag and the Clipping Limit on DRM'ed Kindle files. Both of those metadata records are now tied into the DRM. If you change those values WITHOUT removing the DRM, they will be unreadable on your Kindle (or Kindle app).

The ASIN record and the CDEType record can still be modified to sync the "Furthest Read Page" for non-Amazon purchases. Nothing has changed with regards to that.
(occasionally, Amazon is neglecting to include a PALM database name... which renders Mobi2Mobi Gui pretty much useless. You can use the commandline version of mobi2mobi to give it a database name in this case, which will restore Mobi2Mobi-gui's functionality.)

If you want to enable TTS or change the Clipping Limit on Amazon purchases, you are basically being forced to remove the DRM first.

Last edited by DiapDealer; 02-28-2011 at 12:54 PM.
DiapDealer is online now   Reply With Quote