Quote:
Originally Posted by SirBeardAlot
Thank you for taking time to explain this process for me. It is much appreciated.
The book that seemed to trigger this was about quite large, around 46MB if i recall correctly. It does not have a large ToC though, but alot of images. The one odd thing i can see is that it has a cover that is wider than its height. Not sure if that can cause anything like this though.
But maybe it is just the size of it, and that sickel reboots the device due to thinking that it has hung.
|
46MB is not that big if there are a lot of images. And if there ToC is not particularly big, it shouldn't have a problem. Any chance of seeing the book? If it is somewhere I can legally download it, can you post the link. Or, if it is in the public domain, you can post it here (not sure about the size though). Otherwise, you can upload it somewhere and send me a link. I'll try it on one of my devices and see what happens.
Quote:
I still cannot understand how this can mess up other books though, that was not transfered at the same time and that was working prior to transfering the book that messed things up.
|
Simple. Open a document on your PC, make some changes and pull the power cord out. Did the changes get save? Did the computer complain when it was started? That is basically what sickel is doing, restarting the device in a fairly brutal way that doesn't make sure changes are saved. And if it is in the middle of writing the changes to disk, you could lose a lot more.