diff --git a/library/2img-type-note.md b/library/2img-type-note.md
new file mode 100644
index 0000000..067dbf3
--- /dev/null
+++ b/library/2img-type-note.md
@@ -0,0 +1,70 @@
+Universal Disk Image file
+=========================
+
+- File Type: $E0
+- Auxiliary Type: $0130
+- Full Name: Universal Disk Image file
+- Short Name: 2IMG
+- Written by: Eric Shepherd, March 1999
+
+Files of this type and auxiliary type contain Universal Disk Image format disk images.
+
+---
+
+Files of this type and auxtype contain data in Universal Disk Image format. This file format, a recent standard developed by cooperation among Apple II emulator authors, is used to represent an entire Apple II-compatible disk in a data file. It's an extremely easy-to-use and flexible format that's compatible with most currently-supported Apple II emulation products.
+
+Univeral Disk Image files (also known as '2IMG' or '2MG', from the Macintosh® creator code and filename extensions typically used for these files) consist of four chunks: the header, the data chunk, the comment, and the creator-specific data chunk.
+
+### The Universal Disk Image header ###
+
+The header can be described using the following C structure. All values are little-endian (Apple II byte ordering):
+
+offset | size | description
+------ | ---- | -----------
++$000 | Long | The integer constant '2IMG'. This integer should be little-endian, so on the Apple IIgs, this is equivalent to the four characters 'GMI2'; in ORCA/C 2.1, you can use the integer constant '2IMG'.
++$004 | Long | A four-character tag identifying the application that created the file.
++$008 | Word | The length of this header, in bytes. Should be 52.
++$00A | Word | The version number of the image file format. Should be 1.
++$00C | Long | The image format. See table below.
++$010 | Long | Flags. See table below.
++$014 | Long | The number of 512-byte blocks in the disk image. This value should be zero unless the image format is 1 (ProDOS order).
++$018 | Long | Offset to the first byte of the first block of the disk in the image file, from the beginning of the file. The disk data must come before the comment and creator-specific chunks.
++$01C | Long | Length of the disk data in bytes. This should be the number of blocks * 512.
++$020 | Long | Offset to the first byte of the image comment. Can be zero if there's no comment. The comment must come after the data chunk, but before the creator-specific chunk. The comment, if it exists, should be raw text; no length byte or C-style null terminator byte is required (that's what the next field is for).
++$024 | Long | Length of the comment chunk. Zero if there's no comment.
++$028 | Long | Offset to the first byte of the creator-specific data chunk, or zero if there is none.
++$02C | Long | Length of the creator-specific chunk; zero if there is no creator-specific data.
++$030 | 16 bytes | Reserved space; this pads the header to 64 bytes. These values must all be zero.
+
+
+### Creator Codes ###
+
+If the file is created by a Macintosh application, this should be the creator code of the creating application; otherwise, this should be a unique ID specific to the creating application. As a courtesy, you should let A2Pro know the creator code you choose to use for your application.
+
+The following creator codes are already in use by various applications:
+
+- Bernie ][ the Rescue 'B2TR'
+- Catakig 'CTKG'
+- Sheppy's ImageMaker 'ShIm'
+- Sweet 16 'WOOF'
+
+
+### The Image Format field ###
+
+The image format is indicated as one of the following values:
+
+- DOS 3.3 Order 0
+- ProDOS Order 1
+- Nibblized data 2
+
+
+### The Flags field ###
+
+The flags field contains bit flags that specify details about the disk image. Bits not defined here must be zero.
+
+Bit | Description
+--- | -----------
+31 | If this bit is set, the disk image is locked and no changes should be permitted to the disk data it contains. This is used by emulators to provide support for write-protecting disk images.
+8 | If this bit is set, the low byte of the flags field contains the DOS 3.3 volume number of the disk image. This bit should only be set for DOS 3.3 disk images. If the disk is DOS 3.3 format (the image format is 0), and this bit is 0, volume number 254 is assumed.
+7-0 | The DOS 3.3 volume number, from 0-254, if bit 8 is set. Otherwise these bits should be 0.
+
diff --git a/library/nufx-addendum.htm b/library/nufx-addendum.htm
index bccfba8..0d9c08d 100644
--- a/library/nufx-addendum.htm
+++ b/library/nufx-addendum.htm
@@ -19,7 +19,8 @@
-NuFX Addendum - By Andy McFadden - Last revised 2004/09/26
+NuFX Addendum - By Andy McFadden - Last revised 2014/12/22
+
This addendum clarifies and extends certain aspects of the NuFX
specification. This was developed by Andy McFadden, and is not an
"official" modification of the original document.
@@ -158,8 +159,9 @@ strip any leading path components from disk image "storage names".&nbs
character in a disk volume name.)Extracting:
Applications extracting directly to a disk must strip leading path components
before assigning the ProDOS volume name. Applications extracting images to
-a file don't need to do anything unusual.
Filename
-case sensitivity
+a file don't need to do anything unusual.
+
+
Filename case sensitivity
There isn't a "filename is case-sensitive" flag in
NuFX archives. Since it was designed primarily for ProDOS and HFS
filesystems, neither of which is case-sensitive, we should assume that case is
@@ -170,7 +172,17 @@ to display archive contents as a hierarchical tree.
Applications
should try to recognize that "foo/bar", "foo/BAR", and
"FOO/bar" are the same file, but it's probably not worth
"probing" a case-sensitive filesystem like Linux ext2 to guarantee
-such.
Duplicate filenames
+such.
+
+
Filename character set
+GS/OS and contemporary Macintoshes used the
+Mac OS Roman
+character set. Since GS/ShrinkIt was designed to handle ProDOS and HFS
+filenames, it's reasonable to declare that all filenames should be interpreted
+as Mac OS Roman. Applications should convert filenames to and from the
+Unicode equivalents when extracting and adding files.
+
+
Duplicate filenames
There is nothing in the NuFX specification that prevents having
more than one file with the same name in an archive. In practice, this is
inconvenient, especially for users with command-line tools. On the other
@@ -530,7 +542,7 @@ also accept the year 0. However, if you find a Date/Time with zero in all
useful fields (second, minute, hour, day, month, year), treat it as an
unspecified date rather than midnight of January 1, 2000.
-This document is Copyright © 2000-2004 by Andy
+This document is Copyright © 2000-2004 by Andy
McFadden. All Rights Reserved.
The latest version can be found on the NuLib web site at
http://www.nulib.com/.
diff --git a/library/nulib2-preserve.htm b/library/nulib2-preserve.htm
index 0e39805..f6e075b 100644
--- a/library/nulib2-preserve.htm
+++ b/library/nulib2-preserve.htm
@@ -380,7 +380,7 @@ the comment designator (for "note") because 'c' is a valid hexadecimal
digit.
-This document is Copyright © 2000-2003 by Andy
+This document is Copyright © 2000-2003 by Andy
McFadden. All Rights Reserved.
The latest version can be found on the NuLib web site at
http://www.nulib.com/.