Quote from: philmoz on 08 / April / 2011, 20:19:47On the G12 and SX30 OPT_CHDK_IN_EXMEM works for both manual boot (PS.FI2) and auto boot (DISKBOOT.BIN).Thanks a lot. I've forgotten to change the boot.c file.Now its work with OPT_CHDK_IN_EXMEM.If you want to, you can write this info in your 7-point-instructions. ;-)Next steps are more testing and find out the addresses for sx20 1.02d and 1.00f. :-)
On the G12 and SX30 OPT_CHDK_IN_EXMEM works for both manual boot (PS.FI2) and auto boot (DISKBOOT.BIN).
fmb, are you having any problems with the video on your sx20 with the opt_chdk_in_exmem enabled?
Quote from: bdasmith on 15 / April / 2011, 00:35:01fmb, are you having any problems with the video on your sx20 with the opt_chdk_in_exmem enabled?Hello bdasmithat the moment i don't have found problems with video and exmem. But if you want to test my local version, i posted on Link
I also confirmed the D10 exmem is corrupted by video recording and needs a similar workaround to other dryos cameras. I have not confirmed whether this is needed in vxworks.
Hi, Probably not relevant here since I dont know if SDM implements experimental alternate memory allocation which is the title of this thread. But I just wanted to let you know that with extended memory in SDM I have no difference in edge overlay, RAW, zebra, and everything else that I've tried so far, except that the Menu image sometimes remains plastered on screen with the extended memory version and it does not happen in the normal version. My conclusion is that extended memory does not make things better, infact in case of the menu, it makes things worse. Just my conclusion so far, still testing.I have an ixus 105 / SD 1300.
Quote from: sh1981 on 24 / May / 2011, 03:17:56Hi, Probably not relevant here since I dont know if SDM implements experimental alternate memory allocation which is the title of this thread. But I just wanted to let you know that with extended memory in SDM I have no difference in edge overlay, RAW, zebra, and everything else that I've tried so far, except that the Menu image sometimes remains plastered on screen with the extended memory version and it does not happen in the normal version. My conclusion is that extended memory does not make things better, infact in case of the menu, it makes things worse. Just my conclusion so far, still testing.I have an ixus 105 / SD 1300.Your post is very confusing. If you don't even know whether SDM uses this function why are you posting about it here ?What "extended memory" are you referring to ? How are you enabling/disabling it ?The only reason to use exmem is to avoid running out of memory. If you aren't running out of memory, there's no reason to use it. It will not make any thing faster or better or change the behavior in any other way, except for not crashing or shutting down because it's out of memory. SDM should be less prone to running out of memory, since it doesn't include lua and some other bloat that appears in normal CHDK builds...If your menu problem is actually triggered by using exmem, that would indicate that it isn't implemented correctly on your camera. However, it is far more likely that your menu problem is just intermittent and the association with whatever you were changing was coincidental...
Started by Microfunguy General Discussion and Assistance
Started by mp9_sit Script Writing
Started by Barney Fife Completed and Working Scripts
Started by Lebeau General Discussion and Assistance
Started by CanonBlue General Help and Assistance on using CHDK stable releases