WM6.5 build 21501 kitchen

[brightedge]

Originally Posted by x10guy

I think I've narrowed it down to a conflict between some of the General utilities:

Enlarge StartMenu
Enlarge TitleBar
Menu Enhacment (I believe the spelling is wrong too)

When I had all 3 selected, I'd get this error. When I only selected Menu Enhacment it worked fine.
Can someone confirm this?

It appears to be an issue with the Enlarge Title Bar OEM. If I include it, I get the same error.

I recreated the .dsm and .rgu for the OEM, rebuilt, and it worked fine. I have attached the files and provided instructions below.

How to Fix:

1) Unrar the attached file to your desktop. You'll have a .dsm and .rgu
2) Open C:\Program Files\PPCkitchen.org\BuildOS\Kitchens\PPCkitchen_O EM_VGA.rar
3) Double-click on the "EnlargeTitleBar_4_46_0_0" OEM
4) Drag the .dsm and .rgu saved on your desktop into that folder and allow them to replace the existing .dsm and .rgu
5) Close the rar
6) Open PPC Kitchen and build yourself a new rom

[dan-htc-touch]

Originally Posted by brightedge

It appears to be an issue with the Enlarge Title Bar OEM. If I include it, I get the same error.

I recreated the .dsm and .rgu for the OEM, rebuilt, and it worked fine. I have attached the files and provided instructions below.

How to Fix:

1) Unrar the attached file to your desktop. You'll have a .dsm and .rgu
2) Open C:\Program Files\PPCkitchen.org\BuildOS\Kitchens\PPCkitchen_O EM_VGA.rar
3) Double-click on the "EnlargeTitleBar_4_46_0_0" OEM
4) Drag the .dsm and .rgu saved on your desktop into that folder and allow them to replace the existing .dsm and .rgu
5) Close the rar
6) Open PPC Kitchen and build yourself a new rom

oops, looks like we appended the version number to the oem without fixing the dsm. sorry bout that guys

[brightedge]

Originally Posted by dan-htc-touch

oops, looks like we appended the version number to the oem without fixing the dsm. sorry bout that guys

There is also a connection between this OEM and the breaking of HTC Volume Control. When Large Title Bar is enabled, pressing the volume keys just brings up the Large Title Bar selections. Tapping on the speaker icon also brings up the Large Title Bar selections.

If I disable Large Title Bar, HTC Volume Control works like a champ.

[dPhear]

Originally Posted by dan-htc-touch

what's your location? maybee from work, and the firewall is blocking the communication?

yea im on a school network, so its probley blocking it. I just wanted to make sure i wasn't doing something really wrong, like forgeting to regeter someplace or something like that.

ill just have to wait 2 weeks untill im out

thanks

[divedr]

Umm... Maybe I am missing something here but how do I cook a WM 6.5 ROM for my Sprint (Herman) Touch Pro? The only option I have for the OS is WM6.1 and have D/L all updates. Any suggestions or answers?

Thanks!

[dodge_longhorn]

Originally Posted by divedr

Umm... Maybe I am missing something here but how do I cook a WM 6.5 ROM for my Sprint (Herman) Touch Pro? The only option I have for the OS is WM6.1 and have D/L all updates. Any suggestions or answers?

Thanks!

did you click on herman then on the bottom scroll down to 6.5 .... VGA

[dodge_longhorn]

Does anyone know how to make a custom theme to put into the rom, iam trying but everytime i run the theme the color is a blue color while the pics in the theme is burnt orange

[divedr]

Originally Posted by dodge_longhorn

did you click on herman then on the bottom scroll down to 6.5 .... VGA

Yes I did this but in the kitchen it still lists the OS as 6.1 and it's greyed out and can't be changed.... I must be doing something wrong here!

[dodge_longhorn]

Originally Posted by divedr

Yes I did this but in the kitchen it still lists the OS as 6.1 and it's greyed out and can't be changed.... I must be doing something wrong here!

no dont worry about that it just says that but it is still 6.5 your doing just fine.

[gguruusa]

Originally Posted by divedr

Yes I did this but in the kitchen it still lists the OS as 6.1 and it's greyed out and can't be changed.... I must be doing something wrong here!

Fixed in the next big release.