WM 6.5 Kitchen QVGA and VGA Developer Edition

[joojoobee666]

Originally Posted by ahmedfikry

thanks joojoo


some users over XDA are reporting "black screen" & failure to wake up from sleep mode

anyone having this problem with 23534 here? and if yes....any fix?

I will get some changed files up later today.

UPDATE: Changed Common files are up. No need to get new DPI. Let me know how it goes.

[da_reeseboy]

Originally Posted by joojoobee666

I will get some changed files up later today.

UPDATE: Changed Common files are up. No need to get new DPI. Let me know how it goes.

Just out of curiosity, what did you change?

[joojoobee666]

Originally Posted by da_reeseboy

Just out of curiosity, what did you change?

These common were dumped from the DIO file. This give all the modules a different starting e32_vbase which, according some members at XDA, fixes the issue. The Rollups have all modules assigned to 0x10000000 which throws the reallocation for a tizzy (both PPCk's and Bepe's) and I am guessing causes some overlaps or odd address assigments that some modules do not like.

[ahmedfikry]

Originally Posted by joojoobee666

I will get some changed files up later today.

UPDATE: Changed Common files are up. No need to get new DPI. Let me know how it goes.

thank you

[dibbson]

Originally Posted by justpctech

Oh, so it IS a race for you then? Instead of "helping out Joojoobee666" like you said last time. You still haven't fixed your deprecated tags in your options files yet either...just another one of your "down and dirty copy stuff from the last base so I can be first again" SYS's I guess eh!

Ok then, you win.

Oh, by the way... using greatguy320 nic instead of Ryan Mogul isn't fooling anyone either.

LOL at JustPCTech, get him.... lol. That post made my day

Originally Posted by joojoobee666

These common were dumped from the DIO file. This give all the modules a different starting e32_vbase which, according some members at XDA, fixes the issue. The Rollups have all modules assigned to 0x00010000 which throws the reallocation for a tizzy (both PPCk's and Bepe's) and I am guessing causes some overlaps or odd address assigments that some modules do not like.

I thanked you over at ppck too, but i'll thank you again here again as well i forgot all about this thread as u know i frequent ppck more than this thread for a long time now.

[Tplane37]

I haven't posted here in a while either. Actually, I haven't posted much of anywhere in a while. Most of my info is shared on the IRC now... it's just faster and easier I guess LOL. Anyway, it is good to see that work still continues in here. Keep it up. These are the folks keeping WinMo alive and running so M$ can stay in the mobile phone business

[cybersailor]

Originally Posted by joojoobee666

These common were dumped from the DIO file. This give all the modules a different starting e32_vbase which, according some members at XDA, fixes the issue. The Rollups have all modules assigned to 0x00010000 which throws the reallocation for a tizzy (both PPCk's and Bepe's) and I am guessing causes some overlaps or odd address assigments that some modules do not like.

Thanks, fixed the problems on my Vogue.

[ahmedfikry]

Originally Posted by joojoobee666

These common were dumped from the DIO file. This give all the modules a different starting e32_vbase which, according some members at XDA, fixes the issue. The Rollups have all modules assigned to 0x10000000 which throws the reallocation for a tizzy (both PPCk's and Bepe's) and I am guessing causes some overlaps or odd address assigments that some modules do not like.

i used your updated common files
my cooked rom boots up...but it looks "blue" like the default windows themes & the icons & menues are looking ugly

what is going on?

[ahmedfikry]

Originally Posted by joojoobee666

These common were dumped from the DIO file. This give all the modules a different starting e32_vbase which, according some members at XDA, fixes the issue. The Rollups have all modules assigned to 0x10000000 which throws the reallocation for a tizzy (both PPCk's and Bepe's) and I am guessing causes some overlaps or odd address assigments that some modules do not like.

when i used your updated files to recook, i get a rom that boots but i have the old "blue" default windows theme with ugly icons/menus

any idea whats going on?

[ABM30]

Originally Posted by ahmedfikry

when i used your updated files to recook, i get a rom that boots but i have the old "blue" default windows theme with ugly icons/menus

any idea whats going on?

You have missing this files from MSXIPKernel (in fact from XIP):
723fb954-d931-4348-b672-82a188e587b5.dsm
723fb954-d931-4348-b672-82a188e587b5.rgu
boot_ms.rgu
sysroots.p7b
And from MSXIPKernelLTK:
d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm

Normally they are part of xip.bin, but you can put them in SYS folder to. (at least for me worked)