Quote:
Originally Posted by jhowell
I am surprised that replacing a notebook works at all. I wonder whether it was the time setting change or something else in the new firmware that causes the new behavior.
We discussed this back in May of last year. At that time you reported the same failure but with a different letter appearing. My response is here.
It may be feasible in principle but would require further research into what is going wrong and likely an ability to modify notebooks using outside software to correct the problem. That isn't something I intend to invest my time doing. |
Thanks for referencing previous posts and confirming my suspicions about misremembering things.
I will be happy to investigate and try to figure out what is involved.
Previous to the update, Kindle ran on GMT time. A file copied from computer (I'm in Pacific Time) would somehow appear 'in the past' with respect to the date Kindle last had for the file (in some 'sync' database, I infer). Scribe would infer that the cloud version was newer, and ignore the changed notebook and replace it with the earlier version on sync.
Changing the modify date time to some value greater than the current GMT time (9 ish hours for me) flagged the notebook as 'changed' and would then accept and sync it.
With the update, replacing the file generates a modify date that is greater than the last sync time, so it gets accepted as changed.