Re: dLite and Bookreader

Hitesh Brahmbhatt (hitesh@opti.com)
Wed, 6 Nov 96 12:02:38 PPE

> From owner-ogo@lifelike.com Wed Nov 6 11:50:17 1996
> Date: 06 Nov 96 12:31:21 EST
> From: Marcus Groeber <100712.270@CompuServe.COM>
> To: OmniGo List <OGo@lifelike.com>
> Subject: dLite and Bookreader
> Sender: owner-ogo@lifelike.com
> Content-Length: 715
>
> Hi all,
>
> 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.
>

Hi Marcus,

As far as I can see, it does give me message like "Encoding (XX%)" when I use
dpress on helpfiles or books. Which basically means that dpress is indeed compr-
-essing the file. DPRESS initially refused to compress files even as big as 30-40KB,
but then I used "dpress /a" option and it started compressing everything ! (This
is unrelated, but I just wanted to mention that DPRESS refused to compress the
file because of their size and nothing else and I got around it using /a option.)

> 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...

I initially suspected this too until Marc mentioned about PKWare compression.
Now, I am a bit confused.

>
> Could the problem be related to whether the file resides in the internal RAM or
> on an SRAM card?

I haven't used an SRAM card yet but I doubt that would make any difference.

>
> ciao marcus
>
>
>