View Single Post
  #2 (permalink)  
Old 07-19-2007, 11:48 PM
luv2chill's Avatar
luv2chill
Retired Staff
Offline
Location: Lawrence, KS
 
Join Date: Nov 2006
Posts: 1,524
Reputation: 143
luv2chill is keeping up the good workluv2chill is keeping up the good work
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via ICQ to luv2chill Send a message via AIM to luv2chill Send a message via MSN to luv2chill Send a message via Yahoo to luv2chill Send a message via Skype™ to luv2chill
Well the first problem I see is that it has a setup.dll file. Cabs with those files are much more complicated to make into OEMs because that dll file can do various things after the cab is installed on the device (usually things like extra registry entries).

What you need to do to find out is use a registry editor to dump the phone's entire registry, then immediately install the cab, and immediately dump the registry again. Then you can use an app like Windiff to compare the contents of the two dump files. That will show you all the reg changes that the app made when it was installed. There will be some extra stuff in there you need to ignore so you kind of need to know what you're looking for to pull out just the entries that apply.

But crashing buildos is unrelated to that stuff. That indicates a problem with your option.xml file generally. Make sure that the option.xml contains the UUID that matches the one on the dsm and rgu files and that it really is a unique number (doesn't already exist somewhere in the OEM or SYS folders (which is unlikely if you generated it using a UUID generator).
Reply With Quote