HFSExplorer 0.22.1

• Feature: The "Load file system from device" dialog is enabled for non-Windows
  systems (Mac OS X, Linux, FreeBSD and Solaris are supported initially).
• Change: The HFSExplorer Windows launcher (hfsexplorer.exe) can now open the
  Java download page from the dialog box displayed when no Java runtime could be
  located.
• Change: Binaries and scripts have been relocated into the "bin" directory.
• Bugfix: Extracting files in Windows under Java 7 or higher caused false errors
  to be thrown because HFSExplorer tried to set UNIX-specific UID/GID properties
  for the extracted files.
• Bugfix: The HFSExplorer Windows launcher (hfsexplorer.exe) threw errors in
  certain situations because the JVM couldn't locate the Microsoft Visual C++
  runtime (msvcr*.dll) required by the JVM. This has now been fixed by appending
  the path of the directory containing the required .dll to the system path
  before loading the JVM.

HFSExplorer 0.22

• Feature: Sparse bundles (.sparsebundle) are now supported by HFSExplorer, both
  plain and encrypted.
• Feature: AES-256 is now a supported encryption method. However this also
  requires support in your Java runtime.
  In most cases Sun/Oracle's Java runtime needs to be updated with the "Java
  Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files" in
  order to support AES-256.
• Feature: Preserve file attributes for extracted files. Which attributes can be
  preserved varies with the platform. On Java 5/6 only the last modified date
  can be set for the extracted file. For Java 7 and higher we can also set the
  last accessed date and creation date where the underlying file system supports
  it. When using Java 7 on UNIX platforms, the mode and ownership can also be
  set.
• Feature: More detailed information about the B-tree files is added to the
  "File system info" window, and a new view of the Journal is added.
• Change: HFSExplorer now hides specially protected files and directories by
  default. The affected files and directories are the file and directory inode
  directories ("\u0000\u0000\u0000\u0000HFS+ Private Data" /
  ".HFS+ Private Directory Data\u000d") and the journal files
  (".journal_info_block" / ".journal").
• Bugfix: Incorrect key compare order for extent keys led to issues with
  overflow extents in resource forks.
• Bugfix: Original HFS catalog key comparison algorithm was incorrect, leading
  to various lookup issues on HFS. Fixed by implementing the 'relstring'
  case-folding table.
• Bugfix: Recognizing HFS/+/X filesystems failed when operating on devices
  requiring aligned I/O.
• Bugfix: int overflow bug in caching layer led to OutOfMemoryError in
  certain situations when reading large disks.
• Bugfix: Missing string length check when checking for reserved Windows
  filenames caused an exception to be thrown.
• Bugfix: When extracting directories with names containing spaces, the files
  in these directores could not be extracted. The fix is to check that the
  created directory name is really equal to the name that we intended to create
  (method deepEquals) and to fail if it isn't, requiring the user to rename the
  directory to something sane.
• Many other fixes are also included. Please refer to the git log for detailed
  info.

HFSExplorer 0.22pre (snapshot 2014-05-01)

buildllio.bat: Fix to work with current buildllio_compile.bat.

'buildllio.bat' didn't treat the architecture argument properly and
passed it quoted to both gcc and vc build while it should be unquoted
and only passed to vc build.

Also added some helpful error output to help the user pass the correct
argument.

HFSExplorer 0.22pre (snapshot 2014-02-28)

FileSystemBrowserWindow.java: Set last modifed time for extracted dirs.

Previously we only set the last modified time for extracted files in the
HFSExplorer application, while UnHFS also set it for directories. Now
HFSExplorer can also set the last modified time for directories,
bringing it up to parity with UnHFS.

HFSExplorer 0.22pre (snapshot 2014-02-26)

MasterDirectoryBlock.java: Fix StructElements description of 'drAlBlSt'.

The old description was too vague.

HFSExplorer 0.22pre (snapshot 2014-02-25)

hfsexplorer-0.22pre-snapshot_2014-02-25

UnHFS.java: Show stack trace on error when extracting file.

HFSExplorer 0.22pre (snapshot 2014-02-22)

hfsexplorer-0.22pre-snapshot_2014-02-22

FileSystemBrowserWindow.java: Add error messages on set file time error.

HFSExplorer 0.21

• Feature: New command line utility unhfs added which makes it possible to
  extract the contents of an HFS/HFS+/HFSX file system from the command line.
  Run unhfs.bat/unhfs.sh for instructions on how to use it.
  Thanks to Sebastian Lisken for suggesting this utility and participating in
  its development.
• Feature: Ability to view and extract the contents of resource forks built into
  the file information dialog (will only appear if there is resource fork data
  in the file).
  Also available as an external program, Resource Viewer, which will appear on
  the start menu for Windows users, and can be accessed through the startup
  script resview.bat/resview.sh for other users.
• Feature: New File menu item "Load file system from path" added, enabling users
  to type the pathname to a device file or disk image instead of having to
  select it with the file chooser dialog. This makes it a lot easier to load
  devices in Mac OS X and *nix systems.
• Improvement: Increased compatibility with devices that are unwilling to state
  their size, such as certain iPod devices attached to Windows systems.
  Original problem report:
  http://sourceforge.net/forum/message.php?msg_id=5709684
• Symlink bugfix: Symlinks referring to themselves caused infinite recursion and
  StackOverflowError.
  Original problem report:
  http://sourceforge.net/forum/message.php?msg_id=5723203
• HFS bugfix: Incorrect structure definition for CdrFilRec led to an inability
  to extract resource forks and fragmented files.
• Bugfix: Proper resource fork file format now generated when extracting
  resource forks.
  The earlier versions extracted resource forks as raw resource data, which is
  incompatible with Mac OS X. Now proper AppleDouble format files are generated,
  making the resource forks readable through SMB network shares when mounted by
  Mac OS X.

HFSExplorer 0.20.1

• Bugfix: The status field in the main window could expand vertically.
• Installer fix: Uninstalls current version before installing new one.
• Mac OS X fix: Dock icon gets set to the HFSExplorer icon.
• Bugfix: Some annoying debug messages were printed in the debug console.

HFSExplorer 0.20

• Experimental support for reading encrypted UDIF/raw disk images (.dmg).
  Feedback is much appreciated, as I can only generate a certain amount of test
  cases.
• Experimental support for older HFS (Mac OS Original) file systems. Feedback is
  much appreciated here as well.
• Support for hard links, both to files and directories (yes, HFS+ supports
  directory hard links, but so far Apple only uses them for the purpose of Time
  Machine backups).
• Support for POSIX-style symbolic links.
• Ability to create a read/write disk image (.dmg) from a loaded file system.
• Java 6+ only: Table header sorting for the file table is now implemented. The
  last (empty) column will sort on the internal sort order, if you need to reset
  your sorting choices.
• More flexible extract options, such as setting default actions for different
  events that may occur.
  (Example: "Could not create directory" -> Skip / Auto-rename / ...)
• Major restructuring/modularization of core components to ease future
  development.
• Bugfix: Thread safety is now a reality within HFSExplorer. The extract
  progress dialog no longer needs to be modal.
• Bugfix: Specifying a device path as argument when launching the app failed
  previously due to incorrect assumptions about input data.
• Bugfix: Caching layer was suffering from a logic error, mostly encountered
  when reading very small filesystems (such as disk images), which then could
  not be loaded.
• Bugfix: Autodetect failed for some MBR partitioned drives.
• Bugfix: Corrected a small rounding error that affected the last digit of
  displayed file sizes, making 4,5 KiB files appear as 5 KiB files instead of
  4 KiB (only affected what was presented to the user, and none of the internal
  workings). Whether this is the correct way of displaying a file size is
  arguable, but it's a floor estimate, and usually much more usable.
• Bugfix: The user previously wasn't able to abort the "Calculating selection
  size" phase when extracting files.
• Bugfix/feature: When extracting resource forks or both forks, empty resource
  forks are now skipped over, rather than being extracted as 0-byte "._" files.