Titan 20226 kitchen

[dthames]

Originally Posted by mromblad

when are you all getting this error? what oems are you using?

I have made about 6 roms already from this base with no problems.

Getting the error during the build, I believe its during the regristry build part. Not using any of my own oems, just anything that comes with the base kit.

[pidsw]

Originally Posted by dthames

Getting the error during the build, I believe its during the regristry build part. Not using any of my own oems, just anything that comes with the base kit.

I turned off all of the options and it seemed to work.
I am not sure which one(s) are/is the culprit, but I supporse I can use install them all manually without the kichen.

[glintz]

Heya first off this kitchen stuff is amazing and addictive. I set up the phones in my office and they are a big hit. I use pretty minimal builds and everything is working great here but my programmable buttons. The only button i see is the vjcandela since i selected it for titan. No other buttons are available for programing. Not a big deal since voice command works great from bt I guess I would just miss the button to bring up the 6 buttom comm manager and a button on the phone for voice command is nice in case bt fails. I can add them to the registry i'm sure but since i program 10 or more phones I was wanting to fix it in the build.

Thanks for all your hard work on these kitchens,

Glintz

[biglcny]

Originally Posted by dthames

I keep getting "error building default.hv and user.hv"


Any ideas on why that is happening and how I can fix it?

I kept getting this with the 19588 kitchen. I kept playing OEM musical chairs and didn't get anywhere. I almost felt it was the kitchen and not my OEM's and became quite frustrated.

Believe it or not I used No2Chem's nueDSMZeroer tool and then used BuildDsm.exe to rebuild all the DSM's for my oems. After i did this the "error building default.hv and user.hv" errors went away.

I figured it out because I kept thinking it was something wrong with my RGU's even though they worked in previous kitchens. I swapped out an RGU from a working OEM into an OEM that crashed the build process not caring about the contents and it still failed. That's when I noticed the date modified on the DSM's were so old.

I was under the impression that the kitchen rebuilt all the DSM's during every build run...
Try it and see if it works

http://www.weienterprises.com/nue/nuedsmzeroer.html

[MogulDon]

this might sound dumb or stupid... What's preview 5 and preview 7???

[jhamilton]

Button assignments not showing up on mine.
There was one error on build about overwriting deviceinfo.htm

Scanning kitchens\Drivers_Titan.rar::OEMDrivers
user skipped OEMDrivers\DeviceInfo.htm

This was a base build, with Bell Mobility Carrier, and Beer drinking cat splash animation as my only selected options.

[gguruusa]

Originally Posted by biglcny

I kept getting this with the 19588 kitchen. I kept playing OEM musical chairs and didn't get anywhere. I almost felt it was the kitchen and not my OEM's and became quite frustrated.

Believe it or not I used No2Chem's nueDSMZeroer tool and then used BuildDsm.exe to rebuild all the DSM's for my oems. After i did this the "error building default.hv and user.hv" errors went away.

I figured it out because I kept thinking it was something wrong with my RGU's even though they worked in previous kitchens. I swapped out an RGU from a working OEM into an OEM that crashed the build process not caring about the contents and it still failed. That's when I noticed the date modified on the DSM's were so old.

I was under the impression that the kitchen rebuilt all the DSM's during every build run...
Try it and see if it works

http://www.weienterprises.com/nue/nuedsmzeroer.html

According to Avaya, ToucPal 3.5 is the (only?) culprit. We'll get it fixed. There was a change made last update cycle that made the build process more sensitive to correct .dsm/.rgu relationships - many .dsm had to be rebuilt, but we might not have gotten them all. Randomly zeroing .dsm is a bad idea: while .dsm are rebuilt every build, that doesn't mean what you are taking it to mean.

[biglcny]

Originally Posted by gguruusa

According to Avaya, ToucPal 3.5 is the (only?) culprit. We'll get it fixed. There was a change made last update cycle that made the build process more sensitive to correct .dsm/.rgu relationships - many .dsm had to be rebuilt, but we might not have gotten them all. Randomly zeroing .dsm is a bad idea: while .dsm are rebuilt every build, that doesn't mean what you are taking it to mean.

If zeroing a .dsm is a bad idea then what is the best way to handle rebuilding .dsm's for our presonal oem's?

[shifty]

Just noticed that the button mappings are no longer there. (i.e. cannot map button 123 and 4. only button 5 allows me to remap it to another program. It could be due to adding a bunch of Nue OEM's so I take full blame if I caused it, but it should be reported as a bug.

[davidbrownds]

After i Built a ROM with this Kitchen, When I try to change the button mapping all I see is the mapping for the nueLight2 of buttons. Has anyone else seen this? Is there a easy Fix?