1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2<html> 3 4<head> 5<META http-equiv="Content-Type" content="text/html; charset=windows-1252"> 6<META name="GENERATOR" content="IBM WebSphere Studio Homepage Builder Version 7.0.0.0 for Windows"> 7<META http-equiv="Content-Style-Type" content="text/css"> 8<title>Memory File Archives</title> 9<LINK rel="stylesheet" href="../css/nitro.css" type="text/css"> 10</head> 11 12<body> 13 14<h1 align="left">Memory File Archives <img src="../image/NTR.gif"align="middle"><img src="../image/TWL.gif" align="middle"></h1> 15<h2>Overview</h2> 16<p> 17This section explains the Memory File Archive that is prepared by default in the file system. 18</p> 19<H2>Specifications</H2> 20<P> 21The basic operations of the Memory File Archive are outlined below: <br> � It is loaded automatically the first time the <code><a href="file/FS_CreateFileFromMemory.html">FS_CreateFileFromMemory</a></code> function is called.<BR> � It is accessed at the memory location specified by the <code><a href="../mi/memory/MI_CpuCopy.html">MI_CpuCopy8</a></code> function, making it possible to manipulate it as a file.<BR>Cache disabling and cleaning are not performed internally. Other than file reading/writing, it does not support any manipulations (general directory and path-related commands). The archive name is not registered in the file system.<br> Operations are always conducted synchronously, even when the asynchronous versions of functions are called.<br> <br> <BR> 22</p> 23<H2>Implementation</H2> 24<P> 25The Memory File Archive is implemented as follows: <br> <STRONG>Read Callback:</STRONG> Data is read from memory by the <code><a href="../mi/memory/MI_CpuCopy.html">MI_CpuCopy8</a></code> function. The response is always <CODE>FS_RESULT_SUCCESS</CODE>. <br> <STRONG>Write Callback:</STRONG> Data is written to memory by the <code><a href="../mi/memory/MI_CpuCopy.html">MI_CpuCopy8</a></code> function. The response is always <CODE>FS_RESULT_SUCCESS</CODE>.<br> <STRONG>User Procedures:</STRONG><br> 26<TABLE border="0" height="310"> 27 <TBODY> 28 <TR> 29 <TD width="207" height="10"> 30 <CODE><A href="command/fs_command_seekdir_spec.html">FS_COMMAND_SEEKDIR</A><br> <A href="command/fs_command_readdir_spec.html">FS_COMMAND_READDIR</A><br> <A href="command/fs_command_findpath_spec.html">FS_COMMAND_FINDPATH</A><br> <A href="command/fs_command_getpath_spec.html">FS_COMMAND_GETPATH</A><br> <A href="command/fs_command_openfilefast_spec.html">FS_COMMAND_OPENFILEFAST</A></CODE> 31 </TD> 32<TD height="5">These commands are not supported. Issuing any of them always returns <CODE>FS_RESULT_UNSUPPORTED</CODE>.</TD> 33 </TR> 34 <TR> 35<TD width="207" height="15" style="background-color : white;">Other</TD> 36<TD height="15">Returns <code>FS_RESULT_PROC_UNKNOWN</code> and defaults to default commands.</TD> 37 </TR> 38 39 </TBODY> 40</TABLE> 41 42</P> 43 44<h2>See Also</h2> 45<p><CODE><A href="fs_archive_type.html">FSArchive</a><BR> <A href="fs_archive_proc_func_type.html">FS_ARCHIVE_PROC_FUNC</A> <BR> <A href="archive/FS_SetArchiveProc.html">FS_SetArchiveProc</A></CODE></p> 46 47<H2>Revision History</H2> 48<P> 492005/06/28 Initial version. 50</P> 51<hr><p>CONFIDENTIAL</p></body> 52</html> 53