Does this ROM.LOG contain any useful clues about the failure/crash?
ASSERT!! FsIoNotify.c Line 451
ROM.LOG is a mystery to me but I see "ASSERT!! ... occurred time" is 12 seconds after "rebooting now" time for the failed reboot.
I don't have a good workaround at the moment, but I'll think about it.
If I understood you correctly, the file issue is unrelated to rebooting. So I should just confirm that after every fail/crash I've seen, the last item on the Ult Int log was attempted reboot. I never got a crash at another point in the Ult Int cycle.
If number of files matters, it might be relevant that some fail/crash events happened after less than 24 hours (reboot setting 1 day) when there were not many files on the card.
I do have an idea about one, but I don't know what kind of (scripting?) interface it would need.We could place a file rename hook in fwt_open. Saving the files to directories unknown by the camera would probably prevent this kind of incident. Downside is that those images will become invisible in the camera UI...
1) set a string once that has some simple substitution for file / directory numbers (how do you handle date based folders?)
2) set the full name from script for each shot before shooting. May be difficult in continuous mode, but could probably use shoot hook.
My feeling is jules is probably seeing this because of script autostart, and script still uses fopen() to read files in some places, meaning it doesn't benefit from the startup crash fix.
At least here on my SX200IS the boot failure happens also without startup scripts. Are you sure file access is the reason?
Started by timgor General Help and Assistance on using CHDK stable releases
Started by stagdriver « 1 2 3 4 » Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by stagdriver General Discussion and Assistance
Started by jules Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by philmoz General Discussion and Assistance