Update on DB-updating-problem ...
I sent in the iriver story hd for repair or replacement since the device hung up when updating the db even when there was no SD-Card inserted.
Even an hard-reset was impossible.
Good news: I received the reader two days later as "repaired".
Inspected the device. They had managed to restart it, delete all the books on the main memory and had put three (in digits: 3) ebooks for test purposes on it.
Filling up the device with more books and sd-card: same problems as before.
Asking the support for a replacement, they denied and blamed it to the sd-card.
There is definitely no problem with my three tested sd-cards, which work in my wife's story hd without complaint.
Interesting what they stated in their reply (my translation from german, with comments):
...updating a database of 10GB files can last up to several hours...
Well, and the same procedure the next time the iriver was completely shut off, since you can't avoid the db-updating when restarting ?
...the battery can be uncharged during the process ...
I suspected so and had left the iriver connected via USB.
...this is no hardware-failure, other eBook-readers behave in the same way ...
Really, what is the experience of users of other machines?
...You should only put small amounts of data on your SD-Card...
This is like selling a bus and stating that only two persons should be driven at the same time ...
... if files on the SD-Card are damaged, the reader will hang up...
Does a proper implemented linux behave in such a way when accessing data-files?
...if files of a non-supported format are on your SD-Card, the reader will hang up...
Well, you managed to accidentally put a mobi-file on your reader and it crashes ?
... if it has problems to read it will hang up ...
If the kids from elementary school have problems to read, they will go on strike?
My experience: Very interesting device. Inacceptable software. Not to recommend for larger amounts of ebooks.
And this is what google recommends?
|