Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

I am still having issues with building a 6.5 ROM for my Omnia. I'm hoping someone might have a clue for me for the following error:

BuildBootHive: (RGUComp) !ERROR unable to mount hive file ".\boot.hv"
wmain: (RGUComp) !ERROR failed building BOOT hive

I'm going to guess and say that this means there is something wrong with my xip. The question is what? Does anyone have an idea?

I used the xip kitchen to get my xip. I have not changed or removed any files (I tried removing the files that appeared in xipkitchen also and I got the same error).

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

It's not very hard. Download reversmode.exe aand dump it in your BuildOS tools folder. Then just drap and drop the dll's, exe and mui your want to convert on to that file and it will replace the file in the source folder with a folder. Afterwords, you must make sure that you update the dsm (if it's not 0 bytes that is) by using a tool called DSMinfo.exe (DSM Analyzer by MichyPrima). Run it, choose to analyze the dsm. Then click the manage files included button, remove all files and add all files again from the Add all file from a folder button. Click save selection, then save the dsm.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

ok u said doing this with tmail improved performance any other apps that preformed faster

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

try cooking with out a user oem

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

90% of that is the difference between onboard flash and SD load times. .exe's don't really play into the whole xip thing so much.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

Other than iGO8, I did the etphone.dll from my dialer, HTC Task Manager and ArcSoft (MMS app for verizon). I don't really have anything else I feels I could gain any benefits from doing that to. Those are my promary apps, other than whats already cooked in (but runs fine) and Skyfire (which I don't see a need for XIPing).

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

it means that your kitchen is broken (missing components). Nothing to do with your xip.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

All apps that it can be done to benefit from it. The problem is that they do so at the expense of resorces other apps might need to even function.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

Hmmm....didnt consider that, but the free RAM is obviously a difference. iGO8 is a RAM hungry bastard. So hopefully, this will help and will also not kill my VM to much to make my phone unusable and apps crash. I usually only run one or two apps at a time so I guess I don't anticipate that happening, but that's just a guess based off of my limited understanding of memory management in windows mobile.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

Unnecessary if all you do is convert files/modules, add files/modules, delete files/modules. All kitchens in use at this time will update the dsm during build time to compensate for these actions.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

Your gain in memory is misleading. You only have this perceived gain because you had slot memory going to waste before (slot memory is pre-allocated). If there truly was a free RAM savings by converting .exe's to xip, all .exe's would be xip.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

Thank you. I obviously have some investigation to do.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

I had some weird errors in BuildOS until I fixed the DSM on one of the OEM's I was changing around. I wish I had more detail then that. :(

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

So, forgive my ignorance, and thank you for your patience. If the slot memory was allocated already, but now I am just leveraging it, how is that not a gain in RAM (usable) when running iGO8?

I thought XIP is a method of executing programs directly from long term storage rather than copying it into RAM and was an extension of using shared memory to reduce the total amount of memory required.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

ok i used a completely clean rom and had notifications settings and sounds/vibrate but i started installing apps and lost it any one else have the same problem so we can narrow down the app

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

Did the punctuation keys fall off your keyboard? It's hard as hell to figure out what you intended to say when your post is one giant run on blob.

If installing apps makes you "lose it", I suggest therapy. As far as I know, you're the only one "losing it" because they performed an install. I definitely don't know anyone who "lost it" because of an app or has an app that can help you recover from "losing it"

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

If you have 10 cars, and you allocate 2 of them to me, then ask me to carry your suit case in one of my cars, are you better off than if you had allocated 1 car to me?

Maybe if we had uncompressed XOR flash storage.
except you're not sharing anything in the case of igo.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

Ok,guys,wish me a luck on replacing IE from 6.1.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

if you want old IE, just delete browsingie from sys

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

Thanks for narrowing down my plan.
Everything works.Now I can access and actually see the pictures in my sprint online albums using SPCS picturemail application.ActivX works too!:headbang:

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

Checkout sms also because I faced sms problem when I changed the ie to old.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

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.


spcs picture mail and 6.1 live search works great now,ActiveX works too.I wrote notes in oem info(its not compatible with 6.5 money,msn weather and search).

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

I guess that would be fine. If the ten cars just sat there a lot of times, why not waste 2? Or am I still missing one other key factor? (which is entirely possible, I'm sure...hell, it's probably more than one...)

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

You carrying the suitcase is equivalent to nonxip, me carrying the suitcase is equivalent to xip. Do you trully gain any space moving the suitcase from you to me? No. You still have 10 cars no matter how you slice and dice it, but 1.5 cars is wasted if you over allocate to me. Sure, 8 to you and 2 to me with you carrying the suitcase is the worst for you, and you get a perceived gain of .5 by me carrying the suitcase, but the best is to fix your allocation: 10 for you 0 for me, and you carry the suitcase (because you probably don't always have a suitcase). If you've really gotta have the suitcase handy at all times, even 9 for you 1 for me, and me carrying the suitcase is better than 8 + 2 and me carrying the suitcase.

The point is there is a fixed amount of memory over which to distribute stuff and optimal division of your resources will give you the maximum gain. You will not gain additional RAM by xipping (analogous to adding an 11th car). Overallocating and then pointing out the gain of moving from one area to the over allocated area is a poor example of gain compared to allocating efficiently in the first place.

Your original statement was that you save 4MB approx. of memory by moving igo to xip region. Now you're saying it's ok to waste some space because you have so much. These are competing ideas - either you are trying to maximize or you are not, but being wasteful in one area and then trying to maximize your wastefullness is not an optimum strategy.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

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."

But of course, I may be interpreting it wrong. Please don't assume I am saying you are wrong at all. I am just trying to gain a better understanding and appreciate all of your feedback thus far :)

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

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?

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

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"

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?

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

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. :)

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

ok lets try some punction today. There is some app or setting i changed on my device that inhibits my notifoicatins, meaning when i go into the notification app it wont save the changes or exit upon pressing ok. Also the settings i had before are no longer active so when i recive a text message it doesnt vibrate or ring

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

Hey, I've been reading this thread for a while, and I've been trying to port over the 21501 SYS to the i910. I've been cooking for WM6.1, so I understand enough to get a decent WM6.1 rom out, but I would really like to get 6.5 on the device. Through trial and error, I've gotten the device to the second boot screen. For a while it would boot, and the screen would turn off, and be frozen at the Welcome screen(when I hit a button, the backlight would turn back on). Now when it boots, it gets through 5-8 loops of the second boot screen and then the screen goes out of sync (doesn't take up the whole screen, lines are fuzzy). This leads me to think it's either not loading the correct driver for something. Has anyone run into this problem and can shed some light on what my next step in attempting to get a working rom should be?

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

download ie toggle it allows you to use both.

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

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.

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

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.

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
 

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
 

here is the cab for v 1.1

Re: WM 6.5 Kitchen QVGA and VGA Developer Edition
 

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
 

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