Apache WM6.1 Kitchen CE OS 5.2.19716 (Build 19716.1.0.0) - UPDATED 20080308

**colonel** · #1 (**permalink**) 03-12-2008, 10:54 AM

Quote:

Originally Posted by midniteslice

found my first issue. cannot open prime contacts. i'll play with it when i get home tonight. may be somehting i did. thought i'd throw this out there to see if i am the only one...awesome.

A week or two ago, Prime Contact went commercial. I was in the process of updating the OEM, but ran into a few issues. I will get it updated at some point, but it will not dial from the selected contact. If you need, you can just install the cab and it should function for the time being. Or you can build with the PocketCM OEM.

midniteslice · #2 (**permalink**) 03-12-2008, 11:00 AM

Quote:

Originally Posted by colonel

A week or two ago, Prime Contact went commercial. I was in the process of updating the OEM, but ran into a few issues. I will get it updated at some point, but it will not dial from the selected contact. If you need, you can just install the cab and it should function for the time being. Or you can build with the PocketCM OEM.

HA! i post, i head to xda to look into the prime contact thing. i come back and theres your answer! why can't commercial tech support be as good as ya'll. thank you colonel.

**Trident** · #3 (**permalink**) 03-12-2008, 11:07 AM

You guys are tricky. Past Kitchens all installed in the same directory and would incorporate my custom OEMs and files into the file structure.
This time I had to hunt around to find them. I'm still getting some wierd errors and haven't been able to build a ROM small enough yet, but I'm getting close.
Not so close. I've got this ROM pretty stripped down and it still says I need to remove over 3mb (if I'm reading that Hex correctly).
Selections and log attached. Any advice appreciated.

**colonel** · #4 (**permalink**) 03-12-2008, 11:10 AM

Quote:

Originally Posted by Trident

You guys are tricky. Past Kitchens all installed in the same directory and would incorporate my custom OEMs and files into the file structure.
This time I had to hunt around to find them. I'm still getting some wierd errors and haven't been able to build a ROM small enough yet, but I'm getting close.

What issues are you having? You should be able to put your OEMs in to User_OEM. What did you have to hunt for?

Yes, size is an issue. Unfortunately that is the burden the Apache user must carry. WM6+ is larger as we have seen. And, if you have a new bootloader, your ROM partition is reduced even more.

**Trident** · #5 (**permalink**) 03-12-2008, 11:20 AM

Quote:

Originally Posted by colonel

What issues are you having? You should be able to put your OEMs in to User_OEM. What did you have to hunt for?

Yes, size is an issue. Unfortunately that is the burden the Apache user must carry. WM6+ is larger as we have seen. And, if you have a new bootloader, your ROM partition is reduced even more.

The kitchen is overwriting many files (less now that I changed some selections)- most seem to be image files for the dialer?
My old AlarmClock OEM doesn't seem to get recognized properly.
I had to hunt for the new file directory. Not a big deal at all.

No new bootloader...
My post above is amended with files- any suggestions appreciated.

**gguruusa** · #6 (**permalink**) 03-12-2008, 11:29 AM

Quote:

Originally Posted by Trident

The kitchen is overwriting many files (less now that I changed some selections)- most seem to be image files for the dialer?
My old AlarmClock OEM doesn't seem to get recognized properly.
I had to hunt for the new file directory. Not a big deal at all.

No new bootloader...
My post above is amended with files- any suggestions appreciated.

What do you mean by "doesn't seem to get recognized properly?"

The overwriting is a warning...buildos doesn't know what they are, and in some circumstances overwriting is both unintended and deleterious. A future release will avoid/reduce the multiple popups issue.

**Trident** · #7 (**permalink**) 03-12-2008, 02:36 PM

Quote:

Originally Posted by gguruusa

What do you mean by "doesn't seem to get recognized properly?"

The overwriting is a warning...buildos doesn't know what they are, and in some circumstances overwriting is both unintended and deleterious. A future release will avoid/reduce the multiple popups issue.

When I say that, I mean that I see the following error when I open my project file. When I watch the progress of the build, it looks like the Alarm program errors then works correctly.
Error in BuildOS window: Internal Error- Option.xml GUID not found (BigJAlarmClock-26316bb1-c258-11db-8314-0800200c9a66)

**gguruusa** · #8 (**permalink**) 03-12-2008, 02:52 PM

Quote:

Originally Posted by Trident

When I say that, I mean that I see the following error when I open my project file. When I watch the progress of the build, it looks like the Alarm program errors then works correctly.
Error in BuildOS window: Internal Error- Option.xml GUID not found (BigJAlarmClock-26316bb1-c258-11db-8314-0800200c9a66)

The option.xml in your OEM is not built correctly.

**Trident** · #9 (**permalink**) 03-12-2008, 03:10 PM

Alright, what the heck are you guys including (or more importantly, NOT including) that's allowing your ROMs to build. I'm stripping almost everything out and it still says it's too big.

Oh, and the errors when press play start with: "kitchens\PPCGeeks_OEMrar::Skin-Phone-no2chem_dualtouch-battery.bmp- Overwrite existing file?" and continue with about 20 more images.

mikeabnooy · #10 (**permalink**) 04-03-2008, 01:56 AM

installed and uninstalled BuildOS a few times now and I'm still getting the same error:

ROMUpgradeUT.exe - Unable to Locate Component
this application has failed to start because RAPI.dll was not found. Re-installing the application may fix this problem.

No luck. Any ideas? I've been attempting this on and off all day. I don't know exactly what I'm doing except installing, picking and choosing what i want and then Building. Am I missing something? I haven't been able to get farther than that so far.