Hi there.
OK. Bad news thus far, but I'm sure we're in early days/something simple going wrong. Procedure I used was as follows:
1. Took 4GB SDHC card and threw it through CardTricks 1.44. Formatted as FAT16, 16k sectors.
2. Pressed "NewDryOS" button on the menu options to dump the relevant files onto the card for automated firmware dump procedure.
3. Put file on card, renamed to bootdisk.bin, locked/READ ONLY, pressed "play".
4. Camera would "hang" and I'd see no power on or activity.
5. Waited 40 to 50 seconds.
6. After time had elapsed, I'd eject battery, then SD card.
7. I'd load into CardTricks, and inspect for strings. (used unix strings on my Mac box, just because I'm a unix guy and will never say die, to prove it to myself).
6. Systematically used these files, renaming them as "bootdisk.bin" every time:
offset-0x8.dance3.bin <-- failed to dump data/strings are not present
offset-0x4.dance3.bin <-- failed to dump data/strings are not present
offset+0xC.dance3.bin <-- failed to dump data/strings are not present
offset+0x10.dance3.bin <-- broke format of card entirely. Needed to reformat to "see" mounted in windows.
offset-0x8.dance2.bin <-- failed to dump data/strings are not present
offset-0x4.dance2.bin <-- failed to dump data/strings are not present
offset+0xC.dance2.bin <-- failed to dump data/strings are not present
offset+0x10.dance2.bin <-- failed to dump data/strings are not present
So, as it stands, I *think* I'm doing this correctly, or, at least, thought I was!
Could the offset+0x10 with dancing bits 3 be a clue, as it seems to "damage" the card format, which suggests something is actually being written, at least (albeit smashing over the top of the file allocation table, and thus we can't mount the volume?).
Where to from here?
Thanks guys.
z