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

[Trident]

Originally Posted by The_Omni

Ok first off, thanks to Helmi C, the guys from PPCKitchen.org, Wideawake, and all the regulars around here for the kitchen and this site and it's continuing support of PPC Hacking.

Maybe I am dense/blind, but I don't see any threads that go into what people are and are not including in their personal ROMs.

I have now built and uploaded three ROMs (time consuming) deleting and adding items each time based on what I find when I actually upload and try out the ROM. There has to be a better way, are we allowed to share our projects selection .txt files? If so, how come no one I have seen is doing it, for instance I would love to see luv2chill, or Colonel's default selection.txt file. Seems to me that we could dramatically simplify this process for newbies by simply doing standard project selection.txt files based on combinations of files that work well together.

Maybe something like this:
WM Build 6.1 XXXXX Light Standard for bootloader 2.02(Includes the basic files dialer, theme, task manager, etc.
Please download and paste this file into your projects folder>

WM Build 6.1 XXXXX Medium Standard for bootloader 2.02(Includes the basic files dialer, theme, task manager, Includes xyz programs etc.
Please download and paste this file into your projects folder>

WM Build 6.1 XXXXX Heavy Build for bootloader 2.02(Includes the advanced files dialer, theme, task manager, Includes Programs XYZAB&C etc.
Please download and paste this file into your projects folder>

And then maybe a thread where users share their own custom Selection.txt files with a a bit of narrative of why they went with that config?

Anyway thanks for listening.

Thanks,
Omni

Not a bad idea. The only problem I have is that I include a personal OEM for my device that wouldn't work (nor would I want to share) with anyone else's device. But I wouldn't have a problem sharing a list of selections where I had just deleted that one OEM file. I don't know if that would work or not- but it is intriguing.

[guitardoc64]

Originally Posted by Trident

Not a bad idea. The only problem I have is that I include a personal OEM for my device that wouldn't work (nor would I want to share) with anyone else's device. But I wouldn't have a problem sharing a list of selections where I had just deleted that one OEM file. I don't know if that would work or not- but it is intriguing.

Well you wouldn't want to post your personal OEM for obvious reasons, but the selections.txt is just the "menu" for those selections. It does not include them.

[PocketPcUser]

Originally Posted by The_Omni

Ok first off, thanks to Helmi C, the guys from PPCKitchen.org, Wideawake, and all the regulars around here for the kitchen and this site and it's continuing support of PPC Hacking.

Maybe I am dense/blind, but I don't see any threads that go into what people are and are not including in their personal ROMs.

I have now built and uploaded three ROMs (time consuming) deleting and adding items each time based on what I find when I actually upload and try out the ROM. There has to be a better way, are we allowed to share our projects selection .txt files? If so, how come no one I have seen is doing it, for instance I would love to see luv2chill, or Colonel's default selection.txt file. Seems to me that we could dramatically simplify this process for newbies by simply doing standard project selection.txt files based on combinations of files that work well together.

Maybe something like this:
WM Build 6.1 XXXXX Light Standard for bootloader 2.02(Includes the basic files dialer, theme, task manager, etc.
Please download and paste this file into your projects folder>

WM Build 6.1 XXXXX Medium Standard for bootloader 2.02(Includes the basic files dialer, theme, task manager, Includes xyz programs etc.
Please download and paste this file into your projects folder>

WM Build 6.1 XXXXX Heavy Build for bootloader 2.02(Includes the advanced files dialer, theme, task manager, Includes Programs XYZAB&C etc.
Please download and paste this file into your projects folder>

And then maybe a thread where users share their own custom Selection.txt files with a a bit of narrative of why they went with that config?

Anyway thanks for listening.

Thanks,
Omni

That is actually, one of the best things about PPCKitchen; it saves a lot of time for us end users. I basically, have a very clean, basic nothing selections file, that I start all of my ROM's off, of. I also help out people, by testing the flash process, on my end; make sure the device boots, and then email that selections file. Then, all they have to worry about, is downloading that file, and saving it to their desktop. It can really be a streamlined, process. I just think people don't really know, all of the things ppckitchen is capable of. I bet half, don't even know that they can save as and keep copies of multiple selections files, for future use. They might just click save, and think that it only allows one file. It is a great idea, but would need to be strictly formatted:

Example:

Clean Selections - Contains:
Nothing, beyond the Mobile Office 2007.

...

It should just make a template, for others to follow. Perhaps even, there could be a sticky, for each carrier in groups:
Sprint gets its own, just as Verizon does.
Then, you can seperate the rest, into individual threads, or groups.

[CaliforniaPlaya]

Originally Posted by CaliforniaPlaya

ROM came from here. I've never done this before, learning as I go. Initially, the ROMs I was trying to build yesterday were too big, I kept getting erorrs. I slowly unchecked things until I got it down to size. .netCF was one I wasn't able to find information about, so thought I didn't need it and unchecked it.

I just checked both it and .netCF exception messages and built and installed the ROM again. Now I am back to "xxx is not a valid Pocket PC application." with both Dashwire and Mobile Calculator.

Is there anything else that needs to be in that ROM besides base OS of course? I checked most things off.

Thanks!!!

Any idea what I can do here? I've searched everywhere and can't seem to find a solution to this. I'm kind of stalled doing anything else with it until I can get this resolved.

Thanks!!!

[Trident]

When I try to create a ROM with this kitchen (after updating this morning)- the kitchen fails when it tries to extract the ppcgeeks_OEM.rar file.
Never done it before. The build status log is attached.
Error message says:

kitchens \PPCGeeks_OEM.rar
File create error

Any help appreciated. I need to get this redone soon. I made a ROM with Lenny's 19588 Kitchen, but there were too many things not working right.
And now it's happening with an older build. I must have screwed something up or this update did something.

I think I found my mistake. When I tried similar selections with the other kitchens, I started getting these errors also- until I selected the correct camera! I had been trying the Titan camera; that apparently breaks these ROMs. Trying with this kitchen again.

Success! Along with my failed build log, I'm now attaching what I think will be a great selections list. Syncing now- will edit again when I have it working right!

[kickercvx's]

i Just updated my ppc 6700 thgrough cricket ive had it up dated for aboput 3 days now my internet works great sms works fine i can send mms messeges but i cant receive them untill i do a soft reset and then it shows i have mms messeges but wont let me dowload the messeges any idea of whats goin on???? thanks for any help

[kickercvx's]

its updated to the wm6 the helmi version sorry if i made it seem i updated it through cricket

[mattatat]

anyone know if theres a patch or something that will let the camera use the sdhc card? it works fine with my old 1gig card, but with my sdhc card it tells me "unable to capture. not enuf memory. 36009:111:0"

[bzxzlg]

Originally Posted by mattatat

anyone know if theres a patch or something that will let the camera use the sdhc card? it works fine with my old 1gig card, but with my sdhc card it tells me "unable to capture. not enuf memory. 36009:111:0"

I seem to recall that there was a discussion around you needed to fill up half of your big card with data in order to force the camera to store on the other half ... Dig for the thread ... It's out there ...

You did of course include the SDHD driver in your build?

[mattatat]

Originally Posted by bzxzlg

I seem to recall that there was a discussion around you needed to fill up half of your big card with data in order to force the camera to store on the other half ... Dig for the thread ... It's out there ...

You did of course include the SDHD driver in your build?

yea i did include that.... i was so hoping there was a patch or sumthing for that