Legacy Document

Inside Macintosh: Files /

Chapter 1 - Introduction to File Management / File Management Reference

File and Directory Manipulation Routines / Opening, Creating, and Deleting Files

FSpCreate

You can use the FSpCreate function to create a new file.

FUNCTION FSpCreate (spec: FSSpec; creator: OSType; 
                     fileType: OSType; scriptTag: ScriptCode): 
                     OSErr;

spec

An FSSpec record specifying the file to be created.

creator

The creator of the new file.

fileType

The file type of the new file.

scriptTag

The code of the script system in which the filename is to be displayed. If you have established the name and location of the new file using either the StandardPutFile or CustomPutFile procedure, specify the script code returned in the reply record. (See the chapter "Standard File Package" in this book for a description of StandardPutFile and CustomPutFile.) Otherwise, specify the system script by setting the scriptTag parameter to the value smSystemScript.

DESCRIPTION

The FSpCreate function creates a new file (both forks) with the specified type, creator, and script code. The new file is unlocked and empty. The date and time of creation and last modification are set to the current date and time.

See the chapter "Finder Interface" in Inside Macintosh: Macintosh Toolbox Essentials for information on file types and creators.

Files created using FSpCreate are not automatically opened. If you want to write
data to the new file, you must first open the file using a file access routine (such
as FSpOpenDF).

Note

The resource fork of the new file exists but is empty. You'll need to call one of the Resource Manager procedures CreateResFile, HCreateResFile, or FSpCreateResFile to create a resource map in the file before you can open it (by calling one of the Resource Manager functions OpenResFile, HOpenResFile, or FSpOpenResFile).

RESULT CODES

noErr	0	No error
dirFulErr	-33	File directory full
dskFulErr	-34	Disk is full
nsvErr	-35	No such volume
ioErr	-36	I/O error
bdNamErr	-37	Bad filename
fnfErr	-43	Directory not found or incomplete pathname
wPrErr	-44	Hardware volume lock
vLckdErr	-46	Software volume lock
dupFNErr	-48	Duplicate filename and version
dirNFErr	-120	Directory not found or incomplete pathname
afpAccessDenied	-5000	User does not have the correct access
afpObjectTypeErr	-5025	A directory exists with that name