[Touch GSM ROM Development] spocky12:
@tasomh : Well, I'll do my best :)

@ababrekar : thanks for your answer, but I'm afraid screenshots will lead us nowhere : I have absolutely no errors with buildxip, apart from the fact that it builds a non bootable xip. As I said in my previous message, I tried dumping my original xip (using "dumprom xip.bin -5 -d xip") and then immediately rebuilding it with buildxip. It showed no error message but resulting rom wouldn't boot. New xip filesize is good, I can even dump it again, but then I can see in imagefiles.txt that it modified some o32_readaddr values although it shouldn't have, as no file had been changed.

I tried to contact bepe, perhaps he was unavailable, I have no answer so far.

Note that dumping my original xip with xipport and rebuilding it immediately leaded in a xip a little bit different from the original one (compared in hex editor), but resulting rom boots correctly.

If you need some more information to give me an advice on what I should do, don't hesitate to ask.

@cruzzmz : thank you for your help but I'm stuck with your method too :( :

As you may have read a few lines above, for the moment, xipport seems to be a little more promising than buildxip.

- 1st issue : Xip Address tool doesn't work on my french windows (Xp sp2 & vista tested). I've changed "xipaddrtools.ini" and put lang=2 and "browse for folder" & "ok" french text, but it still does as if I hadn't set this file. So I finally downloaded an english virtual pc windows image (the one to test internet explorer). There, the tool works as it should. And here are the steps I've done :

- Extracted my ks20 xip.bin (wm6.0 aku0.4.10) with xipport into xip_ref (this will be my reference folder)

- made a copy into xip_work

- Extracted 19202-xip.bin (wm6.1) with xipport into xip_temp

- made packages from xip_temp

- copied files/modules contained into MSXIPKernel & MSXIPKernelTLK of those packages into xip_work, replacing the old ones (note that 2 modules were not present in the original ks20 rom : initvmmap.exe & mencfilt.dll as they were not part of wm6.0). I copied them too, because they seem to be part of the boot process. Is it an error ?

- ran xip address tool. Had approximately 12 yellow lines. Some conflits disappeared when I hit space, but some didn't :

* initmap.exe & mencfilt.dll were yellow although they shouldn't be in conflict as they are not in xip_ref. Pressing space on those files threw an exception.

* filesys.exe kept its original value no matter the strength I used on my space bar :p (running mreloc directly did the same)

* hd.dll & osaxst0.dll faked to resolve : relauching Xip Address tool showed they were only pretending as they were yellow again (running mreloc directly, I had "wrong value in o32_realaddr" message)

- Then of course, xipport's Preloc and Map crashed...

If someone wants to test my xips and see by himself, here are download links :

- ks20-xip (original ks20 xip from latest rom)

- 19202-xip (original 19202 xip found in a kitchen)

- xip_work (original ks20 merged with 19202 msxipkernel*.* files, not relocated, aka "f%£ù£ng-Xip-why-won't-you-build-correctly").

Now, I'll pray someone can get me out of this dark wm6.0 xip place and lead me to the light of wm6.1 ;)