Bugs\Fixes\Updates WM6.1 build 20931 kitchen - Page 2

Kolano · #1 (**permalink**) 01-10-2009, 02:45 AM

Can anyone comment on the comparability of the...

Sprint Clock
Background on all tabs

...OEMs?

This link has me thinking they should not be compatible with each other, and this seems to provide different installs for each clock.

Kolano · #2 (**permalink**) 01-18-2009, 05:50 PM

Updated a number of updates, including a fix for incompatibilities with QuickMenu and Manila.

Imaginos · #3 (**permalink**) 01-18-2009, 09:50 PM

You sure look like you have a good handle on the between-release work that has to be done. Are you able to get any of these suggested fixes into the actual kitchen?

Kolano · #4 (**permalink**) 01-19-2009, 02:21 AM

Quote:

Originally Posted by Imaginos

You sure look like you have a good handle on the between-release work that has to be done. Are you able to get any of these suggested fixes into the actual kitchen?

Yes, I do try to work with gguruusa on such.

**gguruusa** · #5 (**permalink**) 01-19-2009, 03:18 AM

Quote:

Originally Posted by Kolano

Yes, I do try to work with gguruusa on such.

And a fine job you do!

Imaginos · #6 (**permalink**) 01-19-2009, 08:46 AM

Ah! Roger that. As a follow up then, are his updated incorporated into the live download servers that the kitchen updater uses? I have tried to pull fixes for the Titan and Herman/Raphael but nothing is showing up. Chefs should just do them manually on the client side?

Also - might I suggest in the core kitchen stuff that the OZ Messenger OEM info mention that it is for the Diamond, it does not work on the Titan/Mogul.

Kolano · #7 (**permalink**) 01-19-2009, 03:06 PM

Quote:

Originally Posted by Imaginos

Ah! Roger that. As a follow up then, are his updated incorporated into the live download servers that the kitchen updater uses? I have tried to pull fixes for the Titan and Herman/Raphael but nothing is showing up. Chefs should just do them manually on the client side?

Yes, these fixes are not yet incorporated into the kitchen and must be applied by chef's manually.

Quote:

Originally Posted by Imaginos

Also - might I suggest in the core kitchen stuff that the OZ Messenger OEM info mention that it is for the Diamond, it does not work on the Titan/Mogul.

Will be added to the mis-info section.

kyppcgeek · #8 (**permalink**) 01-19-2009, 11:23 AM

we need the newer xpi files. Is GC and Scott's versions newer than 20931??

Kolano · #9 (**permalink**) 01-19-2009, 03:16 PM

Quote:

Originally Posted by kyppcgeek

we need the newer xpi files. Is GC and Scott's versions newer than 20931??

Yes, both GC's and Scott's use 5.2.21109. Though there are reports of some issues with the current 21109 XPIs.

Kolano · #10 (**permalink**) 01-19-2009, 06:30 PM

Here are updated "Manila" OEMs. They doesn't address the issues reported above, but do implement additional compression. This reduces their size significantly and improves performance. The Option.xml files of each were also updated to exclude other Manila options, these OEMs will work side-by-side with existing options when extracted to the USER_OEM folder.

Manila:
Pre-compression: 18,000,929 bytes
Post-compression: 11,611,887 bytes

Manila Raphael:
Pre-compression: 17,781,179 bytes
Post-compression:11,496,698 bytes

Manila Sprint:
Pre-compression: 16,037,276 bytes
Post-compression: 9,079,523 bytes

Manila Sprint Raphael:
Pre-compression: 16,305,021 bytes
Post-compression: 10,670,080 bytes