Some of the earlier EEPROM dumps were done in a Text based format, that has added stuff in there to
make the file easy to read using a straight text editor.
The later ones (the .bin) files are essentially raw data. (not Text Editor friendly, but is supported by every EEPROM device out there).
If you are using a Mac, then HexFiend may be your best bet to open these files.
Also do not get too concerned about the file lengths.
Depending on the EEPROM type you choose on the EEPROM programmer software, the programmer will attempt to read data above and beyond the EEPROMs available size.
The software will typically PAD the extra data with FF or 00.
(So you may see with a couple of dumps lots and lots of FF at the end of the file).
Also, you will find that there is not a lot of EEPROM hardware that will work with the Mac.
Your options here may be limited (I too have a Mac, and have found that its just easier to boot in to Windows to support the EEPROM hardware, rather than trying stuff like virtualbox, or even Wine to run the windows software).
I have been toying with the idea of a Rasperry Pi, and connecting a USB OBD dongle to its USB port, and its composite video output to the Aux Input on the headunit, and trying to play around with displaying data on the screen.
The funny thing is I have all the required hardware for this (a supported dongle, the Pi, and Aux input enabled), but I just dont have the time to play around trying to get the serial port stuff working in Python, which is what is mainly supported on the Pi.
Too many projects, and not enough time