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 http-equiv="Content-Style-Type" content="text/css">
7<LINK rel="stylesheet" type="text/css" href="../CSS/revolution.css">
8<title>VFErr</title>
9</head>
10
11<body>
12
13<h1>VFErr</h1>
14
15<h2>Error</h2>
16<p>
17<TABLE border="1" >
18  <tr>
19<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_SUCCESS</EM></STRONG></TD>
20    <TD>0</TD>
21<TD width="520">No error.</TD>
22  </tr>
23  <tr>
24<TD valign="top" width="120" bgcolor="#777777"><STRONG><EM>VF_ERR_EPERM</EM></STRONG></TD>
25    <TD>1</TD>
26<TD>Not a possible operation.<br>Returned when an attempt is made to read a locked file.<br>Under the current VF, this error value is not returned because a lock-related function does not exist.<br></TD>
27  </tr>
28  <tr>
29<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_ENOENT</EM></STRONG></TD>
30    <TD>2</TD>
31<TD>The target file or directory does not exist.<br>This is returned when an invalid file path is specified for a function, using a file path such as <CODE>VFOpenFile</CODE>.</TD>
32  </tr>
33  <tr>
34<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_EIO</EM></STRONG></TD>
35    <TD>5</TD>
36<TD>This error occurs with <CODE>NANDRead()</CODE>, and so on, when one of the device's library functions fails.<br>You must use the <CODE>VFGetLastDeviceError</CODE> function to get the NAND error value and then perform the process that complies with the guidelines for that device.</TD>
37  </tr>
38  <tr>
39<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_ENOEXEC </EM></STRONG></TD>
40    <TD>8</TD>
41<TD>A runtime format error.<br>This error occurs when an attempt is made to delete a directory that is not empty, and for general operations that are inappropriate for the given read/write restrictions, such as trying to write to a read-only file. Since this is a logic error, it should be dealt with at the development stage. You should prepare ways of handling the error such as stopping the process since a read-only file cannot be changed, or recreating the archive if not being able to make the changes would be fatal.
42
43  <tr>
44<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_EBADF</EM></STRONG></TD>
45    <TD>9</TD>
46<TD>Invalid file descriptor.<br>This error is returned when a fatal problem arises at the level of the FAT table.<br>Because the directory structure of the <CODE>vff</CODE> archive has been corrupted, you must handle it the same way as when the Save Data is corrupted, recreating the <CODE>vff</CODE> file. This error does not occur within the normal scope of using VF.</TD>
47  </tr>
48  <tr>
49<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_ENOMEM</EM></STRONG></TD>
50    <TD>12</TD>
51<TD>Occurs when the drive is mounted if there is not enough VF cache memory for the size of the given <CODE>vff</CODE> file.<br>When this error is detected, use <CODE>VFMountXXXCache</CODE> to increase the size of the cache.</TD>
52  </tr>
53  <tr>
54<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_EACCES</EM></STRONG></TD>
55    <TD>13</TD>
56<TD>This operation is not permitted.<br>This is returned when <CODE>VFUnmountDrive</CODE> is run for the drive while a file is open.</TD>
57  </tr>
58  <tr>
59<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_EEXIST</EM></STRONG></TD>
60    <TD>17</TD>
61<TD>The file or directory already exists.<br>This error is returned when trying to create a file or directory that already exists.</TD>
62  </tr>
63  <tr>
64<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_EISDIR</EM></STRONG></TD>
65    <TD>21</TD>
66<TD>This error is returned when a directory is specified for <CODE>VFOpenFile</CODE>.</TD>
67  </tr>
68  <tr>
69<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_EINVAL</EM></STRONG></TD>
70    <TD>22</TD>
71<TD>The argument is invalid.<br>The file name, path name, parameter, or drive may be invalid.<br>In addition, this error is returned when trying to seek before the start of a file.</TD>
72  </tr>
73  <tr>
74<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_ENFILE</EM></STRONG></TD>
75    <TD>23</TD>
76<TD>There are too many open files in VF.<br>Up to five files for each drive can be open simultaneously in VF.<br>This error is returned when trying to open a sixth file in VF.</TD>
77  </tr>
78  <tr>
79<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_EMFILE</EM></STRONG></TD>
80    <TD>24</TD>
81<TD>The user has too many open files.<br>For each drive, up to five files can be open simultaneously.<br>This error is returned when trying to open a sixth file.</TD>
82  </tr>
83  <tr>
84<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_EFBIG</EM></STRONG></TD>
85    <TD>27</TD>
86<TD>The file size limitation has been exceeded.<br>This error is returned when trying to access a file that has a size in excess of the 4 GB maximum.</TD>
87  </tr>
88  <tr>
89<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_ENOSPC</EM></STRONG></TD>
90    <TD>28</TD>
91<TD>There is no space on the drive.<br>This error is returned when a write that exceeds the total sectors is attempted with a function such as <CODE>VFWriteFile</CODE>.</TD>
92  </tr>
93  <tr>
94<TD valign="top" width="120" bgcolor="#777777"><STRONG><EM>VF_ERR_ENOLCK</EM></STRONG></TD>
95    <TD>46</TD>
96<TD>Lock is not allowed.<br>Currently, this error is not returned.</TD>
97  </tr>
98  <tr>
99<TD valign="top" width="120" bgcolor="#777777"><STRONG><EM>VF_ERR_ENOSYS</EM></STRONG></TD>
100    <TD>88</TD>
101<TD>This feature is not implemented.<br>Currently, this error is not returned.</TD>
102  </tr>
103  <tr>
104<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_ENOTEMPTY</EM></STRONG></TD>
105    <TD>90</TD>
106<TD>There is no space in the directory.<br>This error is returned when an entry region cannot be allocated when creating a file or directory.</TD>
107  </tr>
108  <tr>
109<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_SYSTEM</EM></STRONG></TD>
110    <TD>-1</TD>
111<TD>This is a VF internal error.<br>The error occurs in one of three cases:<BR>* The SD library calls an SD mount function without being linked<BR>* <CODE> VFGetLastDeviceError(W)</CODE> is called before mounting<BR>* The argument for <CODE>VFGetOffsetByFd</CODE> is NULL<BR>It would be better to handle this in the application with the equivalent of an assert.
112</TD>
113  </tr>
114  <tr>
115<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_NOT_EXIST_FILE</EM></STRONG></TD>
116<TD>0xB001</TD>
117<TD>The vff file does not exist.<br>This error is returned when a .vff file that does not exist is specified with <CODE>VFMountDrive</CODE>.</TD>
118  </tr>
119  <tr>
120<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_CANNOT_ALLOC_DRV</EM></STRONG></TD>
121<TD>0xB002</TD>
122<TD>Too many volumes are attached.<br>This error is returned when trying to attach (mount) a drive when 26 drives are already attached (mounted).</TD>
123  </tr>
124  <tr>
125<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_NOT_ALLOCATED_DRV</EM></STRONG></TD>
126<TD>0xB003</TD>
127<TD>The drive could not be allocated.<br>This error is returned when specifying the name of an unmounted drive in a function such as <CODE>VFCreateFile</CODE>.</TD>
128  </tr>
129  <tr>
130<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_ALREADY_ATTACHED_DRV_NAME</EM></STRONG></TD>
131<TD>0xB004</TD>
132<TD>This drive name has already been attached.<br>This error is returned when running <CODE>VFAttachDrive</CODE> for a drive name that has already been attached.</TD>
133  </tr>
134  <tr>
135<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_ALREADY_MOUNTED_DRV_NAME</EM></STRONG></TD>
136<TD>0xB005</TD>
137<TD>This drive name has already been mounted.<br>This error is returned when running <CODE>VFMountDrive</CODE> for a drive name that has already been mounted.</TD>
138  </tr>
139  <tr>
140<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_VFF_FILE_FORMAT</EM></STRONG></TD>
141<TD>0xB006</TD>
142<TD>The .vff file format is invalid.<br>Drives being handled for the first time must be formatted with <CODE>VFFormatDrive</CODE>. In this case, delete the .vff file, and then create it again with <CODE>VFCreateSystemFile</CODE>.</TD>
143  </tr>
144</TABLE>
145</p>
146
147<H2>Revision History</H2>
148<p>
1492006/11/14<br>2007/05/08 Corrected the error descriptions.<br>2007/09/10 Added descriptions of errors.
150</p>
151
152
153<hr><p>CONFIDENTIAL</p></body>
154</html>
155