[Touch Pro, Fuze ROM Development] Noonski:
I have made Rom's for the Elf, Wizard, Wallabee (Way Back) and a Multi Language Diamond Kitchen And had had a cooking class over at the ELf forums. I just wanted to wait untill some cool cooks left the Touch Pro for the newer versions. I finally had the time to start again and i like some of the Guys active over here at the Raphael Forum's. But i like motivating people into cooking even more. I stopped reading a while back and trying out everything for myself, it's always nicer finding out stuff yourself makes life more interesting ;)

This build has been Made , chosen and tested by MS and HTC has used it on both the Diamond and Touch Pro for their Stock Rom Upgrades for a reason. Who am i to disagree with something that has been chosen as "Good For Release for multiple roms". I could however hunt down Builds that bhave not been fully developed and Deemed Ripe for RTM. Everyone likes breaking their heads over buggy new leaked builds that where never meant for public use. Not me I like to make a good and Stable Rom, but it can still be a bumpy ride.

I only ported over the Gwes.exe from a newer build so i could implement the HTC Menu Enhancement.

Stuff that is being used all the time in memory should be get their little set place in memory so it can perform better.

The Volume Overlay is the same as in all the Roms, But i hunted down as many Classnames of applications i use so it shows up in those apps. Before it was only used in for Instance in Youtube, WMP or Streaming Media player. It might not show up on some apps as i have not added these ClassNames to the Registry. You can find applications Classnames by using for instance Gsen or The Build in Dot Fred Taskmanager.

There is also a Volume overlay that pops up in the middle that cooks rarely use, but they always leave those graphics in the rom anyway, I chose to dump them if they are not needed.

XDA_UC is very simple just drop all your cabs into a Folder named XDA_UC The device will boot up and install them silently in the back ground.

Sometimes some cabs might ask for user imput or at the end ask to reset the device, if you chose to reset, it might be that some of your other cabs might still need to be sintalled. At the second boot the script does not run any more. Although it could run anyway as it is set to never install one cab twice.

So if you want to time the way the cabs get installed you coulc number them 01_cabname.cab 02_etc.cab. And put the cabs that ask for user input at the end.

After the message that XDA_UC has finished you can be sure that everything has been installed and unless you really need to, why bother with a reboot.

Sometimes OEM packages don't have all the registry settings that can be used for the application, sometimes you find them in one OEm and you stick with them and sometimes your forced to look inside a file because of issues your having. Thus finding out that a few missed registry settigns exist. This does not go for the Volume overlay as these settigns have been known since the beginning. But the Registry settings for the HTCAnimation Shutdown animation and sound i tripped over. (even thought some already knew these from other devices i never had)