Quote:
Originally Posted by Ken Maltby
Exactly, on all points.
Although the parts of the firmware that would need addressing for (a) are the same parts/modules that they need to do extensive work on to get their database working properly.
Another issue might be how they are doing maintenance on the database. It appears that they do try and deal with the database all in one go. When they could just do a minimal catalog data acquisition on the file structure, at the start, and there after build data on a file as it is accessed. (Not that they should need that much from the files.)
Luck;
Ken
|
I would rather see all of the database upkeep, sorting, covers stored etc. at the time the books are sent to the reader, and then have it function quickly until more books are added. Other readers may take more time, or at least as much time to initialize, but then are much faster accessing books in day to day use.
Doing whatever it is they do whenever you open the shelf list for a minute or two is can be done at startup and save the interminable wait.
Helen