recently some people mentioned problems with dLite and Bookreader files. Judging
from dLite's theory of operation, these problems should not be caused either by
the files being already compressed (which should just make dpress turn off its
compression or in the worst case reduce the performace of file access somewhat)
or by random access to hyperlinked files, which is supported by dLite.
At the moment, I can only think of two possible reasons for such a problem:
either a specific bug in dLite, or a special mode of access to files that is
used by Geos and which partly bypasses dLite...
Could the problem be related to whether the file resides in the internal RAM or
on an SRAM card?
ciao marcus