★ PROGRAMMER'S GUIDE ★ File system library
▲ Back ｜ ■
File system library

Appendix B

Error handling

The causes and remedies for the following error codes are described.

GFS_ERR_CDRD

Origin:
The CD block has a read error.
handle:
When a read error occurs in GFS_NwExecOne and GFS_NwExecServer , GFS_ERR_CDRD is returned as a function value, but if the server function is called as it is, recovery processing will be performed. In the completed return type access, only GFS_ERR_CDRD is returned and no recovery process is performed. In this case, read the file again.
If read errors occur frequently, check the CD-ROM hardware and media.

GFS_ERR_CDNODISC

Origin:
The CD-ROM is not set.
handle:
Insert the CD-ROM and try again.

GFS_ERR_CDROM

Origin:
A disc that is not a CD-ROM is inserted.
handle:
Insert the correct CD-ROM and try again.

GFS_ERR_DIRTBL

Origin:
The contents of the directory management structure are invalid.
handle:
Before calling GFS_Init and GFS_LoadDir , make sure that you have not forgotten to set a value for each member of the directory management structure and that an invalid value has not been set.

GFS_ERR_OPENMAX

Origin:
The maximum number of open values is invalid.
handle:
Make sure that the maximum number of open numbers does not exceed the range 1 to 24 in the call to GFS_Init.

GFS_ERR_DIR

Origin:
The specified file is not a directory.
handle:
Check the correspondence between the file identifier and the file.

GFS_ERR_CDBFS

Origin:
I tried to use it even though I did not declare the use of the CD block file system.
handle:
If you use the CD block file system, specify NULL for the address of the directory management area and call GFS_Init.
If you do not use the CD block file system, do not specify NULL in GFS_LoadDir , GFS_SetDir.

GFS_ERR_NONAME

Origin:
The current directory cannot handle file names.
handle:
Call GFS_Init or GFS_LoadDir by specifying the directory management area where GFS_DIRTBL_TYPE is set to GFS_DIR_NAME.

GFS_ERR_NEXIST

Origin:
The specified file name does not exist.
handle:
Make sure that the current directory settings or file name specifications are correct.

GFS_ERR_FID

Origin:
The file identifier specification is invalid.
handle:
Make sure that the specified file identifier does not exceed the range of GFS_DIR_NDIR of the directory management structure set in the current directory.

GFS_ERR_HNDL

Origin:
The file handle is invalid.
handle:
Make sure you haven't forgotten to set the GFS_Open function value for the variable that stores the file handle, and that you haven't corrupted the contents of that variable.

GFS_ERR_SEEK

Origin:
The seek position is incorrect.
handle:
Check the seek position calculated from the reference position and offset.

GFS_ERR_ORG

Origin:
The reference position of GFS_Seek is invalid.
handle:
Make sure the reference position is one of GFS_SEEK_SET, GFS_SEEK_CUR, or GFS_SEEK_END.

GFS_ERR_NUM

Origin:
The number of bytes was specified as negative.
handle:
Check the number of bytes specified by GFS_ByteToSct.

GFS_ERR_OFS

Origin:
The offset is invalid.
handle:
Check the read start sector position specified by GFS_Load.

GFS_ERR_FBUSY

Origin:
Processing for the specified file handle remains.
handle:
Modify the program so that the desired file is accessed again after it has been accessed, or reconsider the file structure.

GFS_ERR_PARA

Origin:
The parameter is invalid.
handle:
Make sure that each of the following functions has the correct arguments.

GFS_ERR_BUSY

Origin:
I tried to do multiple processing.
handle:
See 6.3 Multiple Processing.

GFS_ERR_NOHNDL

Origin:
There is no space in the file handle.
handle:
Increase the maximum number of files that can be opened simultaneously with GFS_lnit, or decrease the number of files that can be opened at the same time.

GFS_ERR_FATAL

Origin:
CD drive It is a state.
handle:

  1. For GFS_Init and GFS_LodDir , try again.

  2. While reading the file, close the file, reopen it, and read it again.

  3. If an error occurs even after repeated execution, it may be due to a failure. Display a message or move to multiplayer.

GFS_ERR_PUINUSE

Origin:
Called GFS_CdMovePickup during pickup operation.
handle:
Make sure to call GFS_CdMovePikup without file access.

GFS_ERR_ALIGN

Origin:
The destination of the file is not placed on the word boundary.
handle:
Place the read area on word boundaries.

GFS_ERR_TMOUT

Origin:
No response was obtained from the CD block within the specified time.
handle:
The hardware may be abnormal.

GFS_ERR_CDOPEN

Origin:
The CD drive tray is open.
handle:
Call SYS_EXECDMP () back to multiplayer.

Even when the DCHG bit (bit5) of the interrupt factor register (HIRQREQ) of the CD block is 1, it is treated as if the tray is open.
During development, make sure the CD status is not open and clear the DCHG bit before calling GFS_Init.
In the retail version, the BOOT ROM clears the DCHG flag and should not be cleared by the application.

GFS_ERR_BFUL

Origin:
When the eject mode is GFS_GMODE_RESIDENT , the CD buffer is full and reading is aborted.
handle:
When the eject mode is GFS_GMODE_RESIDENT, adjust the access order and read amount so that the CD buffer does not fill up.
▲ Back ｜ ■
★ PROGRAMMER'S GUIDE ★ File system library
Copyright SEGA ENTERPRISES, LTD., 1997