24-Feb-86 15:54:00-PST,3188;000000000011 Return-Path: Received: from WISCVM.WISC.EDU by SUMEX-AIM.ARPA with TCP; Mon 24 Feb 86 15:48:49-PST Received: from (BOYD)TAMLSR.BITNET by WISCVM.WISC.EDU on 02/24/86 at 17:45:41 CST Date: 24 FEB 86 17:46-CST From: BOYD%TAMLSR.BITNET@WISCVM.WISC.EDU To: INFO-MAC@SUMEX-AIM.ARPA Subject: missing page in Inside Macintosh I just received a letter from Addison Wesley, publishers of Inside Macintosh. Someone had asked earlier whether they would provide a correction for the missing page II-91. Well, they actually did! In the interest of helping disseminate the corrections, the page follows. If you are wondering how they got my address, I won my copy of IM at the Macworld Expo in San Francisco. ------------------------------------------------------------------------- The File Manager Result codes noErr No error bdNamErr Bad file name dupFNErr Duplicate file name and version dirFulErr File directory full extFSErr External file system ioErr I/O error nsvErr No such volume vLckdErr Software volume lock wPrErr Hardware volume lock FUNCTION FSOpen (fileName: Str255; vRefNum: INTEGER; VAR refNum: INTEGER) : OSErr; [Not in ROM] FSOpen creates an access path to the file having the name fileName on the volume specified by vRefNum. A path reference number is returned in refNum. The access path's read/write permission is set to whatever the file's open permission allows. Result codes noErr No error bdNamErr Bad file name extFSErr External file system fnfErr File not found ioErr I/O error nsvErr No such volume opWrErr File already open for writing tmfoErr Too many files open FUNCTION OpenRF (fileName: Str255; vRefNum: INTEGER; VAR refNum: INTEGER) : OSErr; [Not in ROM] OpenRF is similar to FSOpen; the only difference is that OpenRF opens the resource fork of the specified file rather than the data fork. A path reference number is returned in refNum. The access path's read/write permission is set ot whatever the file's open permission allows. NOTE: Normally you should access a file's resource fork through the routines of the Resource Manager rather than the File Manager. OpenRF doesn't read the resource map into memory; it's really only useful for block-level operations such as copying files. Result codes noErr No error bdNamErr Bad file name extFSErr External file system fnfErr File not found ioErr I/O error nsvErr No such volume opWrErr File already open for writing tmfoErr Too many files open High-level File Manager Routines II-91