HFS File System Settings
List Resource Forks as separate files : You can set IsoBuster to display all Resource forks as separate files. This way you get to see the start address of the Resource Fork, the length of the Resource Fork etc.
Add .[R] to the Resource Forks' names : Because Resource Forks have the same file-name as the file they are associated with (The Data Fork), they cannot be extracted (copied) to a Windows system in the same folder, as Windows does not accept two files with the same name in one folder. To be able to work around that easily and to be able to extract all files of one folder to a Windows system folder, you can have IsoBuster add an .[R] extension to the file name, to give the name a unique character.
Extracting Resource Forks as seperate files is basically not needed for anything except for engineering purposes. E.g. to be able to inspect the content and properties (e.g. size) of the Resource Fork; for designers, developers, engineers or technical people. IsoBuster transparantly takes care of what to extract to a Windows system, in case the file has Mac Properties, so that the file is usable on the Windows system. IsoBuster also extracts Mac Resource forks to an NTFS formatted Hard Disk, and stores them in Alternate Data Streams. These streams are not visible to the user browsing the file system with explorer, but they are there. When you decide to extract files as MacBinary files, all Mac content is preserved, so that files can be exchanged on non Mac systems but when they are taken to a Mac System, Mac is able to re-create the two Forks and special Mac properties. MacBinary files are not understood by Windows, so can generally not be opened with any software, yet they are ideal for exchange purposes when files eventually need to end up on Mac systems again.
Extract Resource Forks and Properties
Extract files with Mac properties as MacBinary files : Click here for an explanation on MacBinary files.
Extract Resource Forks and Properties to NTFS Alternate Data Streams :
Alternate Data Streams in an NTFS file system are a way to store extra metadata for a file, not in the file body itself, but in a stream that is attached to the file. In fact, these Alternate Data Streams resemble Mac "Resource Forks" in this respect. IsoBuster is able to convert the Resource Forks, that are stored in the HFS file system, to NTFS Alternate Data streams, in a way that a Mac, accessing the NTFS partition, is able to understand and use the Resource Forks and other Mac specific Properties again.
Also do this for files with only a resource fork :
When IsoBuster does not extract Resource Forks to Alternate Data Streams, for instance when the option "Extract Resource Forks and Properties to NTFS Alternate Data Streams " is off, or when the extraction happens to a FAT file system, or to a network share where the file system of the remote drive is not known, and when the file consists of only a Resource Fork, no Data Fork, then IsoBuster displays (and extracts) the resource fork as a normal file. In other words, IsoBuster treats the Resource Fork as a Data Fork.
However, if you select this option, and if you are extracting to an NTFS partition, then files that consist of only a Resource Fork will solely be extracted to the Alternate Data Stream (on the NTFS file system). There will be no Data Fork, so there will be no content in the file body itself. The file will appear to be empty (zero bytes), however there will be a stream attached to the file.
Scan options (normal mounting of discs)