Himalaya WM6 CE OS 5.2.1620 (Build 18125.0.4.2)

edy_priyanto said:

could you let me know how to solve it?

Click to expand...

Click to collapse

chamine said:

helmi_c: maybe you will share some tech. info about your process of creation this working rom?
(yes, I haven't hima, mine is hx4700 and there is wm6 already for mine pda, just I'm curious about some things...)

1) XIP creation:
Did you copied all msxipkernel package modules from wm6? If so - where you've placed region_1 for two modules that wasn't in wm5 (encfilt and cachefilt you've moved above of ceddk? or different modules instead of them? or just removed them? (btw, you can simple remove encfilt and even cachefilt, at least for my hx i can do so)

2) .ROM and .VM ... didn't you modified their values?
I noticed (from two wm6's, universal's and m$ emulator's) that e32_vbase from .VM is set equal to ulRAMEnd from XIP's ROMHDR (and that wasn't so for wm5). Also one thought ... e32_entryrva ... isn't it pointing to highest vbase+vsize of imgfs modules (but not xip's modules)...

3) did you checked for a crossmapping between imgfs and xip modules?
(I noticed that wm6 modules vbase+vsize became more higher than wm5 ones)

3) more important - registry creation
How you've created a registry? Registry is really a thing from where bugs are coming... Did you created registry from .rgu's from packages? If so - in what order they was parsed?
(For my hx wm6's registry can be created just from rgu's but need to put them in a right order when parsing.)

Click to expand...

Click to collapse