PPCGeeks Unified ROM Project: Project Updates - Page 4

**schettj** · #31 (**permalink**) 03-24-2007, 12:08 PM

I also made an OEM out of the btd.dll file that works fine, but the kitchen should be "right" not "hacked" as much as possible, and the btd.dll isn't an OEM, it's a driver in the OS. So..... it should be done as such

**jamesus** · #32 (**permalink**) 03-24-2007, 08:45 PM

See first post on updated fixes, etc. for RC2.

We're getting closer!!!

boe · #33 (**permalink**) 03-30-2007, 02:24 PM

I see they've posted yet another RC!!!

Hopefully their hard work is paying off, I know I'm looking forward to testing it out!

Sogarth · #34 (**permalink**) 03-30-2007, 05:34 PM

As boe pointed out, yes, we've posted an RC3. We're expecting that the QA folks should be checking it out this weekend. Depending on how things turn out, we expect to be releasing RC4 to the general public in ROM format only* early to mid-next week (if there aren't major issues that come up). We'll post more about that when things are ready, so please be patient.

* We're only releasing the ROM, and not the kitchen, since we would prefer to keep things under fairly tight control until we've finished with the project. So please don't ask for the kitchen. We will be releasing it when we're done.

P.S. In case you're wondering why we've been labeling all of these as Release Candidates and not alphas or betas, it's because most of these are (debatably) good enough for release to the general public already. Case in point: all of the AKU 3.5 ROMs that many of you are using already.

**luv2chill** · #35 (**permalink**) 03-30-2007, 07:51 PM

To expound on the reason the kitchens aren't being publicly released... it's primarily becase kitchen customization complicates the test bed because it screws with the ROM prior to the ROM image being built. At this stage we are trying to test the ROM in as close to stock form as possible. This allows for all of the usual stuff to be tested without the potential for registry and file conflicts from OEM packages throwing a wrench into things.

This way also allows for testing the installation of all apps the "normal" way (by cab file) to make sure there are no problems doing that--because regardless of kitchens, we all still need to be able to install apps via cab file.

Once we are reasonably sure we've got things squared away under the hood, then we'll unleash the kitchen (and pre-built stock ROM) to the public-at-large for anyone & their mother to build a ROM from it.

It should not be long now. But we really need all the QA people at this point to do what they signed up for and put RC3 though its paces.

Despiser · #36 (**permalink**) 03-30-2007, 11:40 PM

Quote:

Originally Posted by Sogarth

As boe pointed out, yes, we've posted an RC3. We're expecting that the QA folks should be checking it out this weekend. Depending on how things turn out, we expect to be releasing RC4 to the general public in ROM format only* early to mid-next week (if there aren't major issues that come up). We'll post more about that when things are ready, so please be patient.

* We're only releasing the ROM, and not the kitchen, since we would prefer to keep things under fairly tight control until we've finished with the project. So please don't ask for the kitchen. We will be releasing it when we're done.

P.S. In case you're wondering why we've been labeling all of these as Release Candidates and not alphas or betas, it's because most of these are (debatably) good enough for release to the general public already. Case in point: all of the AKU 3.5 ROMs that many of you are using already.

For the life of me I can;t understand why you wouldnt release the kitchen. Who cares if it isnt perfect and if OEMs complicates the issue. Let US decide! I have ZERO interest in yet another pre-built ROM and Im sure most here feel the same way, as has been clearly documented.

The next pre-built ROM I install will be the WM6 upgrade (if it actually lives) and that from the looks of things will happen sooner than you all will release the kitchen.

Sadly all Ive seen over the last month is OEM development dwindle to almost zero since the "Bueracracy" decided they want to take control over the software being released. Fortunately most software Im interested in has a working OEM, even though its not perfect it works. That simple philosophy has been replaced with the typical "when its done" line so often used in the s/w industry.

As Ive said all along who are YOU all to decide when/if the kitchen gets released? Picture where we would be had Helmi_c decided to limit availability of his code to a small circle?

The Kitchen and the OEMs should be your ONLY priority, period but as typical when a select group decide they know better than the masses, the masses suffer.

I know this post sounds harsh but if you try to actually undertand my arguments as Ive plainly laid them out without your ego's getting in the way perhaps you will understand what people actually want as opposed to what you want to FEED them.

~Despiser

**willysp** · #37 (**permalink**) 03-31-2007, 12:17 AM

Despiser - wow, you had me scared for a moment!

I read your first sentence, agreed, and thought "OMFG I agree with Despiser!" (I also have no interest in another canned ROM that I can't apply my own OEM's to.)

But, then you reverted to your complaining, whining form.

I can't believe you asked "who are YOU all to decide when/if the kitchen gets released?" ANSWER = they are the developers, they're doing it for free, they can do what they want, when they want to. You might not like that answer, but it's the answer.

Having said that, I too would like to see more distribution of the in-process kitchen. It would not cause any additional work - I certainly wouldn't expect support. I'm getting along just fine with the 5 or 6 week-old 3.5 kitchen, but the gadget lover in me would really love a refresh.

But, unlike you, I don't feel like I'm in any position to demand, complain, whine, cast aspersions... I'll be getting a great return (a quality kitchen) on my investment ($0) and appreciate in advance their work.

EtherealRemnant · #38 (**permalink**) 03-31-2007, 12:22 AM

So say they release the in-process kitchen and it borks your phone. Then what?

Seriously, coming as one of the developers from the OSX86 project, this complaining only gets you one thing - loss of interest by those developing.

This, in turn, leads to the death of the development and the end of the project until someone else comes along and picks it back up.

It holds back everything.

So STFU and let them do what they need to do.

**luv2chill** · #39 (**permalink**) 03-31-2007, 12:46 AM

Quote:

I know this post sounds harsh

All of your 23 posts sound harsh, becuase quite frankly all you've done in your time on this forum is piss and moan about this and that and how everyone should give you this and that because you deserve this and that.

Your post, while easily refutable, is not even worth refuting because all you are is a shit-stirrer. You've contributed nothing of substance to this forum, therefore you've earned the right to demand nothing of the fine people here who have devoted hours and hours of their time to make your device better.

Take your BS somewhere else--we're not interested.

**colonel** · #40 (**permalink**) 03-31-2007, 12:55 AM

Just to add one other point, there are kitchens out there. Feel free to use them. The point of this project was to create a kitchen that was free of errors and ready for the general public. And, idealy, at some point even a fairly noobish person could build their own rom by just picking the OEMs that they want.