PPCGeeks - WM 6.5 Kitchen QVGA and VGA Developer Edition

PPCGeeks (http://forum.ppcgeeks.com/index.php)

- Windows Mobile Software (http://forum.ppcgeeks.com/forumdisplay.php?f=23)

- - WM 6.5 Kitchen QVGA and VGA Developer Edition (http://forum.ppcgeeks.com/showthread.php?t=54678)

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition

Quote:

Originally Posted by vin255764 (Post 873222)

Tested sms,sending and receiving works.
I did not deleted browsingie,I just took browsingie folder from 21018 and made an OEM.
Can you ,guys,test my OEM?It will show up in "Internet" group in ppck.

download ie toggle it allows you to use both.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition

Quote:

Originally Posted by joojoobee666 (Post 873431)

I thought XIP memory was a pre-allocated region, meaning if the program/dll is a XIP it would be loaded into given a slot in XIP portion instead of the normal application space, thus giving me more usable RAM in the normal application space, therefore only losing out on XIP allocation space (which the application on question would never use). Is this incorrect?

This is based from this:
"When execute in place (XIP) DLLs are loaded, they are loaded from the top of the 64 MB space down. Each XIP DLL is based (positioned in the address space) when the ROM is created. When a non XIP DLL is loaded, it is positioned below the 32 MB boundary. Non-XIP DLLs, also called RAM-based DLLs, are those that are loaded from the object store, decompressed from ROM or loaded from an external file system such as a Compact Flash card. The upper 32 MB of the applications virtual memory space is only used for XIP DLLs."

You're switching from .exe to .dll now. .exe's are not handled the same as .dll. To some extent, you are confusing physical addressing w/ virtual memory map, as well.

Quote:

Originally Posted by vickylife007 (Post 873439)

Hmmm, almost having an headache reading all these technical stuff, but amazed at the same time how much am learning.
So final analysis of what you are saying sir, is we could just get skewed overly too excited moduling everything including what stays more beneficial in the overall interest as a file?

If you xip too many things, you'll fnd that your device locks up/crashes/inexplicably won't run things. Nothing comes for free.

Quote:

Originally Posted by vickylife007 (Post 873472)

Next complicated question will be how to know what to Module, and what is best left as a file? I have followed all the theories, but how do I just pick my oems and say "you are better of a module, and you a file"

Usage and size are the key factors. If it's used a lot, lean towards xip. If it's tiny, lean away from xip. Usage matters more than size.

Quote:

I have studied the SYS from 21159 till 21501 and found out that most SYS folders that were files in 21159 and 21169, were either partially or completely converted into modules form 2117+ and above. So does this not account for the speed of subsequent builds and improved memory management and efficiency?

Quote:

Originally Posted by joojoobee666 (Post 873520)

Well, I am no expert here, but one suspicion I have is that whoever dumped the sys could have done that. Also, quite a few modules often had to be converted into files in order for G'Reloc to work on the 6.5 builds, hence the change to WMReloc in PPCKitchen. Anyone is welcome to correct me on this. :)

Correct. The device(s) some builds were taken from do not have the quantity of RAM that newer devices have, so the choice to XIP or not is much more critical. As applications get greedier, this will apply to modern devices as well.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition

Quote:

Originally Posted by gguruusa (Post 873690)

You're switching from .exe to .dll now. .exe's are not handled the same as .dll. To some extent, you are confusing physical addressing w/ virtual memory map, as well.

Ahh, I thought they were treated the same. And yes, I'm sure I am confusing the two as well as I am only confident in one thing at this point, and that is this: I am not fully competent in in my understanding of the Windows memory architecture as a whole, let alone Windows CE.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition

Hello everyone,

I have a good news for you all.

Check out here.

It worked perfect for me : Here

Thanks and regards

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition

Quote:

Originally Posted by aaronpoweruser (Post 873656)

download ie toggle it allows you to use both.

here is the cab for v 1.1

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition

Quote:

Originally Posted by ksrikanth (Post 873751)

Hello everyone,

I have a good news for you all.

Check out here.

It worked perfect for me : Here

Thanks and regards

Yes it worked for me too... :D
But didn't liked the performace. 200Mhz is too slow to work with this compression.
Or you have to increase your pp witch is out of my thoughts also... :D

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition

Quote:

Originally Posted by Zecanilis (Post 873906)

Yes it worked for me too... :D
But didn't liked the performace. 200Mhz is too slow to work with this compression.
Or you have to increase your pp witch is out of my thoughts also... :D

oh, it might be also.....

However, I gonna test for some days and will see the difference. :)

Anyway, can it be possible to make a program which changes the XPR to LZX while building ROMs? or anyother trick to make it automated?

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition

Does anyone have any StartMenu_GridScene for vga 640x480 with 4 icons per row? I have been looking for over an hr....

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition

I've automated mine. I've extracted imgfs.bin from my payload and changed de first "XPR" to "LZX". Then i puted it back in payload.
And that's all ...:D
(And replacing the cecompr.dll from xip folder)
All working well with plataformrebuilder.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition

anybody figured whats wrong with Pandora radio.it refuzes to play with any wm 6.5 build