WM 6.5 Kitchen QVGA and VGA Developer Edition

[vishalgupta]

Originally Posted by joojoobee666

This one should work. http://forum.ppcgeeks.com/showpost.p...postcount=4358
This is the XIP that's needed. Just add it to the Titan_Core.rar. Don't forget to make the proper changes to you buildbases and devicebases files.

thanx mate

but didnt worked i already tried that
i made the req changes in the buildbases and devicebases files
could u compress a Titan_Core.rar and buildbases and devicebases files for ppck for both common sys 21725 and 96 dpi 21725 sys.

plzzzzzzz
thanxxxxxx

[joojoobee666]

Originally Posted by vishalgupta

thanx mate

but didnt worked i already tried that
i made the req changes in the buildbases and devicebases files
could u compress a Titan_Core.rar and buildbases and devicebases files for ppck for both common sys 21725 and 96 dpi 21725 sys.

plzzzzzzz
thanxxxxxx

Post the ones you have. I am using the Developers build of ppck and the files are different. I can look at them and see if they are ok and if not, try and fix them for you.

[vishalgupta]

Originally Posted by joojoobee666

Post the ones you have. I am using the Developers build of ppck and the files are different. I can look at them and see if they are ok and if not, try and fix them for you.

Thanx mate for ur time

here r the files

http://www.sendspace.com/file/yecm8v

[joojoobee666]

Originally Posted by vishalgupta

Thanx mate for ur time

here r the files

http://www.sendspace.com/file/yecm8v

You only missed one thing. You needed to add a line to the Titan_WM6.1.txt

XipFilename=Titan,WM6.5_21725,Titan_21725_xip.bin

Your builds were not inserting ANY XIP into the ROM, so I'll bet they weren't booting . You changed the BuildID in the BuildBase file, but there was not BuildID in the DeviceBase to tell tell it what XIP to insert for that particular BuildID

Here is the fixed one.

[fredcatsmommy]

anyone been able to build a custom taskbar for qvga into an oem to be used with wm6.5 (and I'm running 21725)? I've searched the threads and while finding lots of discussions about manually customizing the taskbar or installing a cab, I've not seen anything about custom oems.

[vishalgupta]

Originally Posted by joojoobee666

You only missed one thing. You needed to add a line to the Titan_WM6.1.txt

XipFilename=Titan,WM6.5_21725,Titan_21725_xip.bin

Your builds were not inserting ANY XIP into the ROM, so I'll bet they weren't booting . You changed the BuildID in the BuildBase file, but there was not BuildID in the DeviceBase to tell tell it what XIP to insert for that particular BuildID

Here is the fixed one.

Im getting



Processing "netcfagl3_5.dll"
Processing "l2tp.dll"
Processing "d3dm_ati.dll"
Processing "mscoree3_5.dll"
Processing "mscoree.dll"
341 modules rebased.

And nothing happens

[joojoobee666]

Originally Posted by vishalgupta

Im getting



Processing "netcfagl3_5.dll"
Processing "l2tp.dll"
Processing "d3dm_ati.dll"
Processing "mscoree3_5.dll"
Processing "mscoree.dll"
341 modules rebased.

And nothing happens

Does the 21501 build ok?

[vishalgupta]

Originally Posted by joojoobee666

Does the 21501 build ok?

yes its fine

[fredcatsmommy]

Originally Posted by vishalgupta

yes its fine

what's the number of modules with the 21501? I think I read in this thread that above a certain number, ppck will not work. I could be wrong, though.

[joojoobee666]

Originally Posted by fredcatsmommy

what's the number of modules with the 21501? I think I read in this thread that above a certain number, ppck will not work. I could be wrong, though.

It's not necessarily the number of modules, but the size of the modules. Safest bet is to convert any modules that are large into files (i.e. the browsing folder has some larger modules, so does adobe flash) thus freeing up more room for other modules so you won't have any overlaps. This is ONLY an issue with the 6.1 kernel since the 6.5 has an extra slot. 6.1 has Slot 60 (0x78000000-0x79FFFFFF), 6.5 has Slot 60 and slot 61(0x7A000000 – 0x7BFFFFFF).

Also, I believe that the slots are divided into 4KB blocks....but I may not be 100% right on any of this. Anyone, please feel free to correct me if I am wrong.