Dear list and HumanWare staff,
I'm guessing here that I've found another
memory-related bug (like last time). When a
program or two is run, it tends to eat (use)
more momory than it should. Also, when the
user exits the offending program, the memory
does not go down to the original value. In
the second scenario, the amount of memory
that is released corresponds to the size of
the file.
For example, the original memory value is
8000K, and the user opens a 200K file using
Book Reader. The resulting value is 11000K,
however when the user exits Book Reader, the
memory goes down to about 9550K, a difference
of 1.5 MB. This type of scenario has been
observed with Wordprocessor and Book Reader.
Same goes to Media Player (although it shows
no indicator that it is eating a lot of
memory).
Here are some obvious questions to HumanWare
staff (I'm sorry for posting lots of
questions): what's really going on with the
remaining memory? Will it be released later,
will it be used by other KeySoft and/or
Windows CE applications/functions/services,
or will it be considered as "pure waste?"
What will you do with the remaining memory?
And how come PK uses more RAM than Classic or
an mPower?
Also, the probability of encountering lock up
rises when speech is used in conjunction with
the braille display; when the speech is
active, the probability rises about 30 to 45%
vs. 10 to 25% when using braille alone.
Thanks to Vicky for her hard work. Thanks
for your considerations.
___
To leave the BrailleNote list, send a blank message to
[EMAIL PROTECTED]
To view the list archives or change your preferences, visit
http://list.humanware.com/mailman/listinfo/braillenote
