in reply to
Storable byte order problem
You've moved from one architecture to another. Storable has the following in its blurb...
Storable writes a file header which contains the sizes of various C language types for the C compiler that built Storable (when not writing in network order), and will refuse to load files written by a Storable not on the same (or compatible) architecture. This check and a check on machine byteorder is needed because the size of various fields in the file are given by the sizes of the C language types, and so files written on different architectures are incompatible. This is done for increased speed. (When writing in network order, all fields are written out as standard lengths, which allows full interworking, but takes longer to read and write)
I would recommend jumping back to a Linux box and thawing your blob out there. Then store it using Network order (nstore) and throw it back to Windows. Then cross your fingers.