I've been using WinHex to analyse some soundfiles created by the Dalet radio automation system (version 5.1). I have made a couple of templates for this purpose and I thought I'd share them. There are three templates.

Dalet SND file header.txt
Dalet VOL file header.txt

One for reading the header of files with the SND extension. These are the old style soundfiles used to store MPEG-layer II audio. All SND files are accompanied by a VOL file which is used to store the volume information. This enables the Dalet system to quickly draw the waveform.

The third template describes the Broadcast Wave Format as developed by the EBU. This format can be used to store MPEG as well as linear (uncompressed) audio. The BWF format is not only used by Dalet, but also by other programs used in radio and television production. (Steven Scholte)

This template should work for Linux implementations of JFS. (Jens Kirschner)

Start with the Reiser4 Superblock.tpl on Sector 64.

From the root, follow Reiser4's internal tree using the Reiser4 Node Header.tpl on the nodes and either of the following on their node entries: Reiser4 Item Header Large.tpl or Reiser4 Item Header Small.tpl . 'Large' and 'Small' refer to the key size, large is usually what you want being default on Reiser4. The best way to use these templates: Put your cursor on the first byte of the node for the node header template; but put it on the first byte of the following (!) block for the item header templates and (within the template view) move backwards - one to start and then repeatedly to see the other keys.

Reiser4 Stat Data.tpl Reads the Reiser4 variant of inode-like file management.
Reiser4 Directory Entries.tpl Reads all entries in a Reiser4 directory structure.

Finding the structures for Stat Data and Directories is more of a problem and a bit beyond this little description... (Jens Kirschner)

Some WinHex templates for viewing the Volume Descriptor, Path Tables, and Directory Entries on ISO9660 CDs. (Chris Taylor)

The NTFS FILE records are of a pretty variable structure. However, the first template extracts the main parts of the $STANDARD_INFORMATION (0x10) and $FILENAME (0x30) attributes. It also parses the FILE records header and at least lists all the other attributes present.

If you do find the beginning of a data run within one of the attributes, apply the second template to the beginning of that data run and all the data runs within the set will be extracted.

Keep in mind, though, neither of these templates knows anything about the fixup bytes which basically replace two bytes of potentially crucial information with more or less random values at the end of each sector making up a FILE record, so there may be the occasional odd value. (Jens Kirschner)

1. The volume serial number doesn't match the physical case SN for hard
drives; it does match the Windows-assigned volume serial number returned by
the VOL command.
2. There's some additional info at the end of the .lnk files which is
described as 'an unknown structure' in Jesse Hager's article
(http://www.i2s-lab.com/Papers/The_Windows_Shortcut_File_Format.pdf); I can
see that the computer name forms a part of this, but am currently at a loss
to discern how to reliably retrieve this data.
3. On some link files created under Windows 98 and earlier versions, you may
not see a length value preceding the strings for description, relative path,
working directory, etc. at the end of the template, so you may want to
modify those sections to simple zstrings rather than char[n] strings. (Steve Guty)

UFS1 Cylinder Group Descriptor BE.tpl (big-endian)
UFS1 Cylinder Group Descriptor LE.tpl (little-endian)
UFS1 cylinder group descriptor

UFS1 Inode BE.tpl (big-endian)
UFS1 Inode LE.tpl (little-endian)
UFS1 inode structure

UFS2 Superblock BE.tpl (big-endian)
UFS2 Superblock LE.tpl (little-endian)
UFS2 superblock, located 65536, 131072 or 262144 bytes from the start of an UFS partition

UFS2 Cylinder Group Descriptor BE.tpl (big-endian)
UFS2 Cylinder Group Descriptor LE.tpl (little-endian)
UFS2 cylinder group descriptor

UFS2 Inode BE.tpl (big-endian)
UFS2 Inode LE.tpl (little-endian)
UFS2 inode structure

UFS directory entry BE.tpl (big-endian)
UFS directory entry LE.tpl (little-endian)
UFS directory entry, identical for UFS1 and UFS2.
These templates display only regular entries in a directory block, not deleted ones.

EVT_Event.tpl
Event record.

EVT_Header.tpl
Header record.

More information: http://www.dfn-cert.de/events/ws/2005/dfncert-ws2005-f4.pdf

HFSPlus_Catalog_Key.tpl
Defines a file or directory. Includes the file or folder record that follows.

HFSPlus_B-Tree_Header.tpl
HFSPlus_Index_Node.tpl

POS_File_Format_1.1.tpl
POS_File_Format_2.0.tpl

ZIP_Local_File_Header_Structure.tpl
ZIP_Data_Descriptor_Structure.tpl
ZIP_Central_Directory_Structure.tpl
ZIP_End_of_Central_Dir_Structure.tpl