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

**Trident** · #1 (**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** · #2 (**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** · #3 (**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** · #4 (**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** · #5 (**permalink**) 03-12-2008, 10:25 PM

Quote:

Originally Posted by gguruusa

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

BuildOS completed with that error, but I haven't flashed it yet.
I'm going to guess that if option.xml isn't built correctly, AlarmClock it isn't going to work correctly (if at all) once I flash the device.

**gguruusa** · #6 (**permalink**) 03-12-2008, 10:37 PM

Quote:

Originally Posted by Trident

BuildOS completed with that error, but I haven't flashed it yet.
I'm going to guess that if option.xml isn't built correctly, AlarmClock it isn't going to work correctly (if at all) once I flash the device.

In this case, it's likely that the only symptom is AlarmClock will be included regardless of whether it's checked or not.

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

Quote:

Originally Posted by gguruusa

In this case, it's likely that the only symptom is AlarmClock will be included regardless of whether it's checked or not.

Really. That's interesting.
I just rebuilt the ROM without AlarmClock and am flashing as I type.
Dang the startup on this thing is fast!

Another quick question... is something up with the updater? It's updated something almost every time I've started it, but it always shows the same version number.

UPDATE: You're right. AlarmClock wasn't selected, but it showed up in the ROM and is working fine. Amazing.

**Trident** · #8 (**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 · #9 (**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.

PocketPcUser · #10 (**permalink**) 04-17-2008, 12:58 PM

Quote:

Originally Posted by mikeabnooy

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.

I think the problem is, you need to install Activesync; I may be wrong, but I think I recall that was the problem.