API Differences Between FAT and ISO 9660

RTFiles-32 presents an ISO 9660 file system much like a FAT file system to the application. For example, function RTFFindFirstEx can return a MS-DOS/FAT directory entry of a file. The same structure is also returned for files located on an ISO 9660 volume even though ISO 9660 uses a completely different structure. RTFiles-32 translates the ISO 9660 format to the FAT format to allow applications to use a uniform API which does not depend on or change with the accessed file system. However, the following RTFiles-32 API functions may behave differently on ISO 9660 volumes:

Any file I/O operation which would write to the disk will return error code RTF_WRITE_PROTECTION or RTF_INVALID_FILE_SYSTEM.
If a function returns structure RTFDOSDirEntry, the file name and extension stored in structure RTFDOSDirEntry is invalid (FileName[0] is '\0'). Unlike FAT, ISO 9660 file systems do not contain short and long file names; there is only one name per file.
For the reasons given in the previous paragraph, function RTFMakeFileName cannot be used on ISO 9660 volumes.
Function RTFGetDiskInfoEx does not support flag RTF_DI_FAT_STATISTICS. If it is nevertheless specified, it will be unset in the function's return value. Fields FATCount and MaxDirEntries in structure RTFDiskInfo are set to zero.
Function RTFGetPartitionInfo does not return any CHS (Cylinder, Head, Sector) data for CDs. However, all other returned fields are valid.
Functions RTFCheckDisk, RTFCreateMasterBootRecord, RTFSplitPartition and RTFCreateBootSector are not supported for ISO 9660 volumes.

Left The ISO 9660 File System Structure