readme-fstest.txt

用于测试文件处于最大处或者没有空间时的程序运行情况的源代码。代有DLL和MOD文件。

Readme file for fstest, version 1.2
Nov. 11, 2003
Copyright (c) 2003 Unicom-BREW Technologies. All rights reserved.

=====================
DESCRIPTION
=====================

This application is to test the performance of device's file system when it reaches maximum file count or full storage usage, it can also be used by developers in preparing their device for adverse EFS conditions. It implements the following functions:

1. File Count: Keep creating 10 bytes files untill failed, and return the final count number.

2. Storage Usage: GetFreeSpace of EFS, and keep writing 100k per file to ESF until the maximum storage size is reached.

3. Remove Files: Remove all the files created.

4. Settings: Set default max file numbers, which is used to set a default max file number, when carrying out file count examination, either the max file number is reached or the new file creating failed, it stops the action and returns. 
 
Note: when user executes 1 or 2, he/she must select 3 to remove files created, otherwise he/she can't finish the other operation.

=====================
BUILD INSTRUCTIONS
=====================

Emulator:
Assumption: you have BREW SDK 2.0, BREW Tool Suite and Microsoft Visuall C++ 6.0 installed.

Open fstest.dsw in Microsoft Visual C++ 6.0, select Build All, and run it on the emulator. (Make sure you have not put ANY .sig file under the ths directory, or it can't be executed on the emulator).

Device:
Assumption: you have BREW SDK 2.0, BREW Tool Suite and Gnude(Gnu GCC for ARM Compiler) installed.

From a Windows "cmd" shell, cd to this extracted location, compile the application, "make -f fstest-gcc.mak".

Copy fstest.mif to the root directory on your device;
Create fstest directory on the root directory;
Copy fstest.mod to ringertest directory; 
Generate a signature file according to your device, name it fstest.sig, put it to fstest directory.
Restart the device and run it.

=====================
Known Issues:
=====================

Suspend & Resume events are not handled, so application may be terminated abnormally when these events occur. At this condition, user should run this application and execute "Remove Files" to free resources created.