Important: The information in this document is obsolete and should not be used for new development.
FSpCreateResFileprocedure is not available, you can use the
CreateResFileprocedure to create an empty resource fork.
PROCEDURE CreateResFile (fileName: Str255);
- The name of the file to be created.
CreateResFileprocedure creates a file with an empty resource fork in your application's default directory--that is, the directory in which your application is located.
If no other file with the given name exists in the default directory or any of the other directories searched by
PBOpenRF(see the following section, "Special Considerations"),
CreateResFilecreates a resource file--that is, a resource fork, including a resource map. In this case the file has a zero-length data fork.
If a file with the specified name already exists and includes a resource fork with a resource map,
CreateResFiledoes nothing. Call
ResErrorto determine whether an error occurred. If the data fork of the specified file already exists but the file has a zero-length resource fork,
CreateResFilecreates an empty resource fork and resource map for the file.
Before you can work with the newly created file's resource fork, you must use
OpenResFileor a related function to open it.
CreateResFileprocedure may move or purge memory blocks in the application heap. Your application should not call this procedure at interrupt time.
CreateResFileprocedure first checks whether a file with the specified name exists. (If so,
ResErrorreturns the result code
dupFNErr.) To perform this check,
PBOpenRF, which looks first in the default directory for a file with the same name, then in the root directory of the boot volume (if the default directory is on the boot volume), and then in the System Folder (if one exists on the same volume as the default directory). It is thus impossible, for example, to use
CreateResFileto create a file in the default directory if a file with the same name already exists in the System Folder. To avoid this problem, use
noErr 0 No error dirFulErr -33 Directory full dskFulErr -34 Disk full nsvErr -35 No such volume ioErr -36 I/O error bdNamErr -37 Bad filename or volume name (perhaps zero length) tmfoErr -42 Too many files open wPrErr -44 Disk is write-protected fLckdErr -45 File is locked dupFNErr -48 Another file with the same name exists in the default directory, the root directory of the boot volume, or the System Folder
SEE ALSOTo check for errors, call the
ResErrorfunction as described on page 1-47.
For a description of the
OpenResFilefunction, see page 1-62.