|
What appears to be "Locked up" is not actually the case. Certain file types
will /can cause the 700 to HOLD the CPU while it scans
the entire document and searches through each page. The problem is, the time
it takes for the CPU to release may give off the impression that the device has
"Locked up" when it actually is still checking. I've tested this theory on a large
volume dictionary and a 2000 page PDF. When I searched for a word, the entire
system devotes 100% of the processor cycles to that task.
The odd thing is, it does not always happen in the same document. Some searches
are fast and others take a while. This leads me to believe that an improvement
can be made in how the system responds while in search state. Perhaps an ABORT/
CANCEL function could be added.
|