View Single Post
Old 01-12-2014, 12:41 AM   #4
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,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
If the book was already on the device, DSNB is probably write. But, this behaviour will also happen if the TOC in the book is invalid. If the pointers in the TOC do not actually point to files and anchors in the book, any attempt to use them will fail. You can probably see this using the calibre viewer, but it is a bit more forgiving for errors than the Kobo ereaders.

The fix is probably to removed it from the device and regenerate the TOC using either calibre or Sigil. Then resend it to the device.
davidfor is offline   Reply With Quote