View Single Post
Old 02-13-2015, 05:11 PM   #99
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,829
Karma: 30277270
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by BookJunkieLI View Post
I'm at work now but when I get home tonight I'll re-install 2.14 Portable and then progressively update to each version to see where the break happened. Not sure what that'll do for me but it'll be something.
If you can isolate it to say - "OK in 2.14 & 2.15" and "not OK in 2.16 on" and its repeatable then you can report it as 'bug' and Kovid should be able to fix it.

That you saw a difference between, Portable, 32bit and 64 bit seems a bit weird (Portable is 32bit repackaged).

You could create a clone of your library with a subset of your books to try the 'edit json, rebuild db, set up VM options' suggestion. For the VM problem I fixed that way, the metadata preferences backup looked OK, i.e. the JSON wasn't malformed or wrong in respect of values. But I noticed that the relative position of the VM settings in library A (where I had the problem) were different to library B (where I didn't have the problem); that's what led me to do the remove/rebuild/recreate for the VM settings in library A... which fixed the problem. But caveat emptor - my memory is fallible, so I may be misremembering.

BR
BetterRed is offline   Reply With Quote