I thought I should post some comments about my latest findings. First, as seen in case of CnM net-books we have some files that we are interested in. The windows image is xip.nb0 but along with this one is very probable to have a similar nboot.bin and eboot.nb0. I still don't know yet what is about that Producer.nb0
Anyway as far as I can tell at this point, studying the partitions I found that nboot is a quite small bootloader and it doesn't do much, it's mainly used to load WinCE as quick as it is posible.
On the other side eboot is a more advanced bootloader. I has a lot of capabilities among which is flashing/reflashing each partition, as necessary. The problem at this point is that I do not know how to load eboot at startup. It may be a hidden combination of keys or maybe USB_boot short on mainboard would do the trick. I have to try this one. I haven't yet since all human interfaces is done though UART messages and I could'n find time to solder the wires and do all that adaptation stuff it requires to hook it up to PC COM - but I'll do it soon
Once I entered eboot I should be able to do a lot of thinks with Platform Builder. For instance one other feature would be to load a custom build of WinCE directly into ram, without making any change to the installed system.
One other thing that I want to share with you is that it should be an Updater already into flash, but again I don't know how to load it. The loader itdelf is part of eboot, but it's partition is not. That means it has a dedicated partition intended for system restore. It should have a backup in there.
Ok folks, that was it for now. I hope to have new information next time.
I almost forget, if anyone wants to add some more info on this king of stuff, please come forward.