GRAMPS
GENViewer
GENMatcher

Thanks for posting this here. If I may add for the readers a few important things that you pointed out to me in your emails to me about this:

FTM 2010 could not read this file because it says it is GEDCOM Version 5.5.1 and FTM gave the message: “GEDCOM file must be version 5.5 or greater”. Hmmm. So when I produce my totally GEDCOM 5.5.1 compliant output, does that mean FTM won’t be able to read it?

Legacy wouldn’t open the file because it just hung. To me, I don’t care what the cause is. If Behold hangs on anything, it’s my top priority to fix that.

TMG 8 wouldn’t open the file because Unicode is not supported.

GedPad Pro and Genealogica Grafica did open the file, but you said they reported unlinked people/families. That would indicate that the Hex 00 prevented them from inputting the complete person records that contained the Hex 00.

Regarding the other programs that do read it, as Tamura points out in his comment in his Google+ posting, “Many applications will read it because they do not bother to properly parse GEDCOM files. One could add that most of these applications are likely to export it too.”

Thanks Louis (and Bart) for a copy of the GEDCOM file.

Results for some software include:

Ahnenblatt Opened file
Behold Imported 9 records only
dynastree Home Edition Opened file
Family Historian Opened file
Family Tree Legends Opened file
GedPad Pro Opened file
Genealogica Grafica Opened file
Legacy Standard Edition Did not open file
Family Tree Builder Opened file
Family Tree Maker Did not open file
Personal Historian Essentials Imported 9 records only
RootsMagic Opened file
The Complete Genealogy Builder Opened file
The Complete Genealogy Reporter Opened file
The Master Genealogist 8 Did not open file, Unicode not supported
TNG Opened file

But what actual effect to Behold load time will this do for large GEDCOM files?