Without trying to decode the contents, I had a quick look at the files that were kindly sent to me.
Good files (from yesterday evening):
GPE.bin GPES.bin, sha256sums for both are:
04c89555a560bbdf35dc3d9ea1c679dc875c011e941c15fcc1a1e453f5e346ba
File type is: zip compressed data, original size modulo 2^32 216692
Unzipped the sha256sum is (for both):
f92218b089d6fd651154cd39090e4121bd8e5d576aae64e753606b473a4c1b7b
And the size: 216692 bytes.
Bad files:
GPE.bin: data file, cannot unzip it, size is 216692.
GPES.bin: gzip compressed data, original size modulo 2^32 16584
sha256sums:
f92218b089d6fd651154cd39090e4121bd8e5d576aae64e753606b473a4c1b7b GPE.bin
e6dfae1dc1be0e062136398843ff8ef89e68959be9efc1c2534b0f6c8423f166 GPES.bin
Notice that the sha256sum and the size of the "Bad" GPE.bin is the same as the _unzipped_ good GPE.bin
The size of the "Bad" unzipped GPES.bin is only 16584 bytes.
Obviously any software that expected a zipped GPE.bin would be unable to unzip it, because it was already unzipped.
The "Bad" GPES.bin is very small. This may or may not be signifcant, for systems that use EPO.bin you can obtain EPO files in different sizes (the bigger, the longer they are valid). A small file for a day, a bigger one for a week.
It does not answer anything but I thought I'd post it anyway just in case anyone else finds this kind of thing fascinating. :-)
