So if you tell me not to do it because it can possibly corrupt the file system and maybe not even on my camera then this is a situation where I have to make a different decision: I choose the best possible way instead of no way.
I'm not telling you not to do it, I'm only reporting behavior that has been observed in related situations
I mentioned filesystem corruption again to explain why the CHDK file browser uses copy and delete, not to say you shouldn't use rename if it works for you.
If there is anything we can do to fix the problem with os.rename, then I would appreciate it. Maybe it is possible somehow to write a fix.
As mentioned earlier, os.rename calls the underlying firmware rename() function. If the underling firmware doesn't have the capability you want, it's unlikely we add it, but it's always possible there are bugs in CHDK, or that understanding some additional details will show a way to accomplish what you want.
Does the problem still happen if intermediate directories exist?@reyalp: I caused a crash. Restarted the camera and executed the romlog script. Logfile is in the attachment.
Did you use a script, or the CHDK menu? (Miscellaneous stuff->Debug Parameter->Save ROM Crash log)
Did the camera shut down after you tried to save the romlog?
The romlog is odd, from the last 3 lines of camera log output, it appears to show a crash while trying to save a romlog
00020940: SystemEventInit
00020940: System.Create
00020940: GetLogToFile
@Caefix please post the full romlog as an attachment.