I Think I would be too scared to open up other peoples GP32's incase of damaging them . If I decide to do it to mine and it works I might But Im going to wait untill the Guarantee runs out like I did with my PS2Steve-o, would you be willing to take on modding gp32s for others? If I find any success on my end, I may consider it too. Besides, this looks a lot more interesting than modding a psx- which im glad I dont do anymore.
I don't know where you did get this assumption but of course the latest 32M capable MultiFW2 (also now available in ROb's site) is backward compatible.. which required patching also other things than just the ram controller and MMU setup. The only thing is that you screw up if you install 32M capable BIOS to a GP32 with only 8M as there is no dynamic memory configuration (i.e. the BIOS is hardcoded to support certain amount of memory - it doesn't try to find out if there is 8, 16 or 32M available).I realized that the bios may have to be reconfigured to enable running older progs- for example - before entering the desktop, one would have to select 8 or 32Mb ram configurations- otherwise, the 32mb jump may lead to a gp32 with absolutely no functionality. Or maybe pressing l+R at startup would enable the ram menu. Just an idea.
Depending how well the SDK memory management wrapper turns out, probrams compiled with 32M aware libs should also work in 8M GP32 (assuming they don't try to allocate too huge memory blocks, that won't fit into 8M). The intention is to make this RAM stuff as transparent as possible. And I know e.g. Rob is able to dofrom what i understand its backwards compatible meaning
the 3d2mb one could play 8 mb ones but the 8mb one couldnt play 32mbs ones