UDF Dateisystem Einstellungen (Mac)


[Diese Seite ist noch nicht auf Deutsch übersetzt.  Wenn eine bestimmte Seite für Sie sehr wichtig ist, senden Sie bitte die genaue Adresse, und wir werden die Ubersetzung vorantreiben. Vielen Dank für Ihr Verständniss.]

IsoBuster - UDF Dateisystem Einstellungen (Mac)

Extended Attribute Files

Extended Attribute Files : The UDF File System can contain Extended Attribute Files.  These files have the exact same name as the file they are associated with.  
Windows itself and Windows applications ignore these files but other systems often use them.  E.g. Macintosh uses associated files to store the "Resource Fork" in.
Be aware that Mac "Resource Forks" don't take up the complete associated file-size, instead, "Resource Forks" start at a certain offset inside the extended attribute files.
IsoBuster finds associated files and automatically keeps track of them when they contain Mac properties and a Resource Fork as part of the transparent Mac support.  

List Extended Attribute Files as separate files : You can also set IsoBuster to display all extended attribute-files as separate files.  
This is independent from their content.  Also non-Mac / non-Resource-Fork extended-attribute files are listed then.

Add .[EA] to the Extended Attribute Files' names :  Because extended-attribute files have the same file-name as the file they are associated with, 
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. 
[EA] extension to the file name, to give the name a unique character.

List Mac Resource Forks as separate files : You can also set IsoBuster to display all Resource forks as separate files.  So, next to possibly displayed. 
EA files you also get Resource Fork files which are in fact physically located inside the .[EA] files.  But this way you get to see the start address of the 
Resource Fork, the true length of the Resource Fork, the byte offset in the first block etc.  Furthermore you get the unique ability to extract the "true" 
Resource Forks from the disc without having to "peel open" the extended attribute files first.

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.  
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.

Convert to MacBinary

Extract files with Mac properties as MacBinary files : Click here for an explanation.


Scan options (normal mounting of discs)