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>An error occurred during reading or writing to a device.<br>The device might be unable to read or write (it might be damaged).</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 is returned when the FAT or boot sector is damaged and not executable, or when a directory that is not empty is specified with <CODE>VFDeleteDir</CODE>.
42  <tr>
43<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_EBADF</EM></STRONG></TD>
44    <TD>9</TD>
45<TD>Invalid file descriptor.<br>This error is returned when the data in the descriptor is an unexpected value.<br>Normally, this error is not returned.</TD>
46  </tr>
47  <tr>
48<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_ENOMEM</EM></STRONG></TD>
49    <TD>12</TD>
50<TD>Insufficient cache memory in VF.</TD>
51  </tr>
52  <tr>
53<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_EACCES</EM></STRONG></TD>
54    <TD>13</TD>
55<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>
56  </tr>
57  <tr>
58<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_EEXIST</EM></STRONG></TD>
59    <TD>17</TD>
60<TD>The file or directory already exists.<br>This error is returned when trying to create a file or directory that already exists.</TD>
61  </tr>
62  <tr>
63<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_EISDIR</EM></STRONG></TD>
64    <TD>21</TD>
65<TD>This error is returned when a directory is specified for <CODE>VFOpenFile</CODE>.</TD>
66  </tr>
67  <tr>
68<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_EINVAL</EM></STRONG></TD>
69    <TD>22</TD>
70<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>
71  </tr>
72  <tr>
73<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_ENFILE</EM></STRONG></TD>
74    <TD>23</TD>
75<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>
76  </tr>
77  <tr>
78<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_EMFILE</EM></STRONG></TD>
79    <TD>24</TD>
80<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>
81  </tr>
82  <tr>
83<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_EFBIG</EM></STRONG></TD>
84    <TD>27</TD>
85<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>
86  </tr>
87  <tr>
88<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_ENOSPC</EM></STRONG></TD>
89    <TD>28</TD>
90<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>
91  </tr>
92  <tr>
93<TD valign="top" width="120" bgcolor="#777777"><STRONG><EM>VF_ERR_ENOLCK</EM></STRONG></TD>
94    <TD>46</TD>
95<TD>Lock is not allowed.<br>Currently, this error is not returned.</TD>
96  </tr>
97  <tr>
98<TD valign="top" width="120" bgcolor="#777777"><STRONG><EM>VF_ERR_ENOSYS</EM></STRONG></TD>
99    <TD>88</TD>
100<TD>This feature is not implemented.<br>Currently, this error is not returned.</TD>
101  </tr>
102  <tr>
103<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_ENOTEMPTY</EM></STRONG></TD>
104    <TD>90</TD>
105<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>
106  </tr>
107  <tr>
108<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_SYSTEM</EM></STRONG></TD>
109    <TD>-1</TD>
110<TD>This is a VF internal error.<br>This error is returned when the data maintained internally by VF is in an unexpected state.<br>Normally, this error is not returned.</TD>
111  </tr>
112  <tr>
113<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_NOT_EXIST_FILE</EM></STRONG></TD>
114<TD>0xB001</TD>
115<TD>The <CODE>.vff</CODE> file does not exist.<br>This error is returned when a <CODE>.vff</CODE> file that does not exist is specified with <CODE>VFMountDrive</CODE>.</TD>
116  </tr>
117  <tr>
118<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_CANNOT_ALLOC_DRV</EM></STRONG></TD>
119<TD>0xB002</TD>
120<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>
121  </tr>
122  <tr>
123<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_NOT_ALLOCATED_DRV</EM></STRONG></TD>
124<TD>0xB003</TD>
125<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>
126  </tr>
127  <tr>
128<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_ALREADY_ATTACHED_DRV_NAME</EM></STRONG></TD>
129<TD>0xB004</TD>
130<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>
131  </tr>
132  <tr>
133<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_ALREADY_MOUNTED_DRV_NAME</EM></STRONG></TD>
134<TD>0xB005</TD>
135<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>
136  </tr>
137  <tr>
138<TD valign="top" width="120" bgcolor="#ffffe8"><STRONG><EM>VF_ERR_VFF_FILE_FORMAT</EM></STRONG></TD>
139<TD>0xB006</TD>
140<TD>The <CODE>.vff</CODE> file format is invalid.<br>Drives being handled for the first time must be formatted with <CODE>VFFormatDrive</CODE>. In this case, delete the <CODE>.vff</CODE> file, and then create it again with <CODE>VFCreateSystemFile</CODE>.</TD>
141  </tr>
142</TABLE>
143</p>
144
145<H2>Revision History</H2>
146<p>
1472006/11/14<br>2007/05/08 Corrected error descriptions.
148</p>
149
150
151<hr><p>CONFIDENTIAL</p></body>
152</html>
153