Low Memory Error Processing; Resetting And Initializing The Classpad - Casio fx-CP400 User Manual

Warning Message
Time out.
The end of condition was not satisfied.
Too Many eActivity Files

Low Memory Error Processing

An error occurs on the ClassPad if it is unable to reserve enough work area memory to perform a particular
operation. When a low memory error occurs, any application in use at that point is shut down and an error
message like the one shown below appears.
Tapping the [OK] button clears the error.
Important!
• To avoid loss of data, you should make it a regular habit to periodically perform the save operation.
You may lose some of the data you are inputting with an application that shuts down due to a low memory
error. When the low memory error occurs while you are using the eActivity application to create data, for
example, any unsaved data you have input is lost.

Resetting and Initializing the ClassPad

The memory of your ClassPad is divided into four parts: main memory, a storage area for storing data, an
eActivity area, and a RAM area for executing various calculations and operations. Reset and initialize restore
normal ClassPad operation after some problem occurs.
RAM Reset: Perform RAM reset when the ClassPad freezes up or otherwise fails to perform as expected
for some reason. A RAM reset does not affect data stored in main memory, the storage area, or the eActivity
area, but it clears any data stored in the RAM area.
Memory Reset: There are four different types of memory reset operations. Deleting all variable and program
data in main memory, deleting all eActivity data, deleting all data in the storage area, deleting all three of the
above.
Memory Initialize: Initializing memory deletes all data and returns ClassPad memory to its initial factory
default state.
This section explains how to perform the RAM reset operations only. The memory reset and memory initialize
operations are performed using the System application. For details, see "14-2 Configuring System Settings".
Description
The data communication operation you are trying to
perform is not possible because there are too many
eActivity files.
–
Appendix 270