i just wanted to share this because i thought it was strange..is it me?
had this sd card that has been used in a S95 dual partition setup for a long time.
never had a reboot failure.
end of last year i reformatted it in the camera, placed it in the pc reformatted the single partition fat32 with fat32format for use in my g1x and created the boot flag in camera since it was single partition now.
this worked for a while, but today i noticed that yesterday it got stuck on the reboot, lens had not moved out and led was still flashing 'busy'.
since there was no obvious reason, it had succesfully rebooted a few times before, voltage was good...reboot flag was still set: after pulling and reconnecting the power script started running.
speed of card on the pc was also good.
so no obvious reason why it had failed.
i decided to reformat it back to dual partition, but now with the dual partition software for the s110-102b, so i placed the build on the single partition fat32 card.
after the cam had created dual partition and placing it in the pc to load the s110-102b build on both partitions.
the first partition already contained CHDK files.
i thought it was strange but decided, without first placing the s110 build on both partitions, to start up chimp to make the card bootable since dual partition boot can't be made in cam as far as i know.
and then chimp told me the build on the fat partition was 1.5 from the s95. ...and appeared to have the boot flag set since chimp only gave the option to remove it.
i checked that and yes, the first partition had the s95 software that i thought was destroyed (at least the tables referring to it) when i reformatted the card back to one partition in camera and then again with fat32format and after it has been used for a few month as such i would have expected it to be at least overwritten at some point.