dcd's hermann ROM & kitchen 2.16

[peepeesea]

Originally Posted by jakdillard

DCD is using the platform kitchen in which you will need to go thru the ext folder and add or remove a "_skip" file manually to add or remove a package in the rom there are tutorials on this type of kitchen in this forum

link?

...please

[ebuechler3]

Originally Posted by mightymike

Probably because DCD didn't include option.xml's due to the fact that everything in there is necessary for the ROM to run therefore shouldn't be unchecked or checked. The possible purpose of the kitchen is to add your own oems such as additional software, personal tweaks, etc.

I have the same setup with my ROM because the stuff I cook in shouldn't be excluded therefore I don't show the choices within BuildOS.

thanks, i have cabs for everything. can i google oems to find them to place in the kitchen or shouid i "borrow" oem folders from other kitchens like calks? if there was a way i could add all my apps in this kitchen, i would be straight! thanks!

[killerkhatiby009]

So does anyone know whats really different in this release versus the previous beta 1.11 release? Besides the WM 6.5 build version seems to be older on this one than previously. Well I assume its an older build because of the number but you never know nowadays with the crazy build numbers of 6.5.

[jakdillard]

Originally Posted by peepeesea

link?

...please

http://forum.ppcgeeks.com/showthread.php?t=70776
my bad here ya go

[dcd]

thanks jakdillard.

the kitchen does not have a gui. you could adopt ervius's visualkitchen to manipulate my base, but its designed to run the way you see it today.

distributing software by cab is cleaner and easier, allows the end user more options, allows me to update software without updating a kitchen, and allows you to update your device without flashing.

there is a small repository of tested working cabs on my site.

my assumption is that the kitchen will be of use to other chefs. end users generally should use the ROM.

chefs will want to note that SYS is untouched. changes I want applied to SYS are done via EXT package. the idea is that you can drag and drop an OS into this kitchen.

[SkunkApe]

damnitttt.....i wanna install this so bad, but my pro took a crap on me yet again (keyboard stopped working AGAIN) so im waiting on my replacement, which should have been here today but got rescheduled for tomorrow

ill install tomorrow when i get a chance, but i know i wont be let down. Thanks again bud! cant wait to try it.

im gonna assume that the alarm clock issue is working now? lol

Wow....DCD...i'm flashing as soon as I get home. I wish I knew how to Remote into my computer at home to just get it started now lol

[doireallyhavetodothis]

Originally Posted by peepeesea

excuse my noob question but what are the pre requisites for running the kitchen?

A red spatula, 2 egg beaters and a flour sifter.

[quadjacks]

Originally Posted by mightymike

Probably because DCD didn't include option.xml's due to the fact that everything in there is necessary for the ROM to run therefore shouldn't be unchecked or checked. The possible purpose of the kitchen is to add your own oems such as additional software, personal tweaks, etc.

I have the same setup with my ROM because the stuff I cook in shouldn't be excluded therefore I don't show the choices within BuildOS.

Originally Posted by jakdillard

DCD is using the platform kitchen in which you will need to go thru the ext folder and add or remove a "_skip" file manually to add or remove a package in the rom there are tutorials on this type of kitchen in this forum

so it seems all i have to do is download mighty rom 4 OEM base, drag and drop the package files i want into the OEM folder of this kitchen?

[peepeesea]

Originally Posted by brushrop03

Wow....DCD...i'm flashing as soon as I get home. I wish I knew how to Remote into my computer at home to just get it started now lol

www.logmein.com