<dt id="ie">FR_INT_ERR</dt>\r
<dd>Assertion failed. An insanity is detected in the internal process. One of the following possibilities is suspected.\r
<ul>\r
-<li>Work area (file system object, file object or etc...) is broken by stack overflow or any other application. This is the reason in most case.</li>\r
+<li>Work area (file system object, file object or etc...) has been broken by stack overflow or any other tasks. This is the reason in most case.</li>\r
<li>There is any error of the FAT structure on the volume.</li>\r
</ul>\r
Note that if once this error occured at any operation to an open file, the file object is aborted and all operations to the file except for close will be rejected.\r
<dt id="io">FR_INVALID_OBJECT</dt>\r
<dd>The file/directory object structure is invalid or a null pointer is given. All open objects of the logical drive are invalidated by the voulme mount process.</dd>\r
<dt id="wp">FR_WRITE_PROTECTED</dt>\r
-<dd>Any write mode action against the write-protected media.</dd>\r
+<dd>Any write mode operation against the write-protected media.</dd>\r
<dt id="id">FR_INVALID_DRIVE</dt>\r
<dd>Invalid drive number is specified in the path name. A null pointer is given as the path name. (Related option: <tt>_VOLUMES</tt>)</dd>\r
<dt id="ne">FR_NOT_ENABLED</dt>\r
<dd>Not enough memory for the operation. There is one of the following reasons:\r
<ul>\r
<li>Could not allocate a memory for LFN working buffer. (Related option: <tt>_USE_LFN</tt>)</li>\r
-<li>Size of the given CLMT buffer is insufficient for the file fragments.</li>\r
+<li>Size of the given buffer is insufficient for the size required.</li>\r
</ul>\r
</dd>\r
<dt id="tf">FR_TOO_MANY_OPEN_FILES</dt>\r
projects / z180-stamp.git / blobdiff