This cache is placed in honor of Frank Druid of the Druids geocaching team. Frank has a very special birthday this month! Frank loves puzzle caches, so here is a little puzzle in his honor. Don't churn the water, piranhas! Let's let the birthday boy get FTF honors on this one. In the event Frank thinks he can't get to an area soon enough, he might post a note saying others can go for the FTF.
I saved the coordinates for my cache in hexadecimal format on my old computer system, whose chip architecture used "Big Endian" format (like the Motorola chip in an old Mac). But then I switched computers! My new computer is x86 architecture like a regular PC, which stores data in the "Little Endian" format. But I'm still using the same ol'dumb software which is trying to read it using the old storage convention! The difference between these two conventions is the order of the bits -- "Big Endian" stores the bits left to right just like we read. In a "Little Endian" system, each 8-bit word is stored left-to-right, but the words in each string of words is stored right-to-left.
A simple example of Big Endian versus Little Endian would be the hex digits 0xABCD. (I'm using "0x" to warn you that the next characters are to be read as hexadecimal digits.) In a Big Endian system they would be saved left to right just as shown: ABCD. In a Little Endian system, the words get moved to read right-to-left: CDAB.
So for example, when I stored the degrees latitude (33 degrees) for my cache, I saved it as a two-word integer, hex digits 0x0021, which in bits is 0000000000100001. In my old Big Endian system, it was stored left to right just as shown. However, when I moved to the new computer, my dumb ol' software still tried to read it left to right, but on the Little Endian architecture it was stored as 0x2100 (bits = 0010000100000000) so my software displayed the decimal number 8448.
That's all pretty straightforward, so you should have no trouble with the rest of the coordinates! Except that while I stored the Degrees as 16-bit integers, I stored the Minutes as IEEE-754 32-bit floating point values. Minor detail there :-)
There is a ROT-13'd hint for the cache in the Certitude in case you need it. My GPSR was bouncing a bit around the final, so it may be helpful.
You can validate your puzzle solution with certitude.