New BuildOS - Report Bugs Here - Page 31

sshearer · #1 (**permalink**) 12-18-2007, 03:40 PM

Hi, I tried creating my first build with the WM6 kitchen a little while ago and ran into the 'ROM too big' issue (so I'd like to add my voice to the chorus about wanting to see some sort of Current Build Size indicator as items are selected & de-selected).

But as a result of the above, I de-selected (among other things) my choices for JVM & .Net CE - and was able to get past the size issue.

However, in testing individual applications later, I ran into an error message for many of them (eg. WiFiFoFum) which indicated an error in the application. Sorry, I didn't write down the actual text, but for purposes of this posting, it doesn't matter anyway. At first, I just wrote it off as a WM5 vs WM6 application issue.

But then, I did another build where I included the .Net package, and the above run-time error (for WiFiFoFum anyway) no longer occurred. At which point I realized that there was a dependency.

In hindsight, DUHH !

But, it would be great if when selecting individual OEMs, BuildOS could tell the user that one or more other packages (eg. .Net, Java, ...) are required. I know that's already in place for some things, so hopefully adding these additional dependencies won't be too hard. I don't think the dependent packages should be automatically selected because there may be times when there are multiple choices (eg. .Net 2 & .Net 3.5).

Also, FYI, in trying to flash my ROM, I initially kept getting INVALID COUNTRY_ID (120). After some reading of postings & some experimentation, I changed by RUU selection to No ID, and then it flashed fine.

Then I realized that my issue was trying to flash a used (& imported from USA) Sprint 6700 when having selected Telus as my (Canadian) carrier. So, it might be helpful if the description of error 120 could be updated to include this scenario as an example.

Lastly, to be accurate, the carrier 'Telus' should be changed to 'Telus Mobility'. They are actually 2 separate companies ('Telus' controlling 'Telus Mobility'), and 'Telus' is all about land-line service.

**guitardoc64** · #2 (**permalink**) 12-18-2007, 08:56 PM

Test Rom completed with no problems. I figured it would, but wanted to check it out. The errors don't seem to affect the performance or the build.

bilson · #3 (**permalink**) 12-22-2007, 12:45 PM

Has anyone had a problem with Today Agenda not working now? I can't get it to run. It worked pre 121707.

Kolano · #4 (**permalink**) 12-22-2007, 02:37 PM

Quote:

Originally Posted by bilson

Has anyone had a problem with Today Agenda not working now? I can't get it to run. It worked pre 121707.

Yes, they have. Please see the Kitchen Bugs/Patches thread.

bilson · #5 (**permalink**) 12-22-2007, 03:46 PM

Quote:

Originally Posted by Kolano

Yes, they have. Please see the Kitchen Bugs/Patches thread.

Don't mean to be condescending but I believe the the title of this thread is New BuildOS - Report Bugs Here!

I did get it working by downloading the cab and reinstalling.

**gguruusa** · #6 (**permalink**) 12-22-2007, 04:27 PM

Quote:

Originally Posted by bilson

Don't mean to be condescending but I believe the the title of this thread is New BuildOS - Report Bugs Here!

I did get it working by downloading the cab and reinstalling.

Yes - perhaps you don't know what BuildOS is vs the kitchen?

OEM problems (like Agenda issues) are a kitchen problem, not a BuildOS problem. See post 1 of Kolano's kitchen thread for how to differentiate.

Thanks for the additional info, however. We'll look into it.

jjlwork · #7 (**permalink**) 12-24-2007, 12:31 AM

Is it possible to configure this for the Titan, or is there any documentation. I have a good base rom I use from another forum and I want to configure to build with this version of BuildOs. I assume the minimum I need is a BuildOS_config.txt, a selections file and obviously BuildOS and my rom....I've tried pointing build os to my "kitchen" folder, and set all of the options I could find to to Titan but I got an error, then I rar'ed it up and pointed it to that and it seemed to run fine without complaining, however it does not seem to recognize the option.xml files in the rarred kitchen...I looked at the apache rar file(as much as I can without the password) and noticed it has a "kitchen_config.txt" file, I am thinking this has something to do with it. Is there anyone who can help, or point me to some docs?

**gguruusa** · #8 (**permalink**) 12-25-2007, 05:02 PM

Quote:

Originally Posted by jjlwork

Is it possible to configure this for the Titan, or is there any documentation. I have a good base rom I use from another forum and I want to configure to build with this version of BuildOs. I assume the minimum I need is a BuildOS_config.txt, a selections file and obviously BuildOS and my rom....I've tried pointing build os to my "kitchen" folder, and set all of the options I could find to to Titan but I got an error, then I rar'ed it up and pointed it to that and it seemed to run fine without complaining, however it does not seem to recognize the option.xml files in the rarred kitchen...I looked at the apache rar file(as much as I can without the password) and noticed it has a "kitchen_config.txt" file, I am thinking this has something to do with it. Is there anyone who can help, or point me to some docs?

The titan code isn't ready for prime time. Neither is the Axim, Hermes, or Emulator code. If you want to play with it for your personal use, feel free - but please don't release a kitchen with buildos v.09.05 (new buildos) until I say it's ready for your device. Don't bother aksing questions about why it borked your device until then either.

It's not necessary to rar or have a kitchen_config.txt file - new BuildOS is 100% backwards compatible with the old familiar BuildOS structure, but there's more to making a titan ROM than reading the ROM files.

**guitardoc64** · #9 (**permalink**) 12-25-2007, 12:27 PM

Would be nice if this kitchen could be reconfigured to work with the Titan. It's not currently set up that way, but I'd bet the kitchen team could do it. It's probably on their list of stuff to do anyway.

ksquake · #10 (**permalink**) 01-01-2008, 04:36 PM

I have recently downloaded and started using Helmi_WM6_Apache_Kitchen_071217_1 which uses PPC-BuildOS with file version 9.5.02, the .9.05 version listed in the title here comes from the splash screen.

If this is in the wrong spot let me know and I will move it to the proper thread but I do believe the error comes from BuildOS.

After selecting the appropriate RUU and Carrier and splash screens and options I want to include I am getting the following error when building the ROM by clicking on the green play button “Build Rom”:
--------
PPC-BuildOS.exe - Unable To Locate Component
This application has failed to start because MSVCR71.dll was not found.
-------

This error appears during the "Building ROM" step and after clicking OK on the error then the Build Status dialog box reports:
Building ROM
Unable to load compression DLL!

The referred to MSVCR71.dll does exist in the \BuildOS\TOOLS directory.

Do I need to copy this DLL to another location?

I am running this in a VMWare Windows XP SP2 machine with Active Synch 4.5

Any help would be appreciated.

-----------------------

Well, try and try again as they say, it appears that copying this file into the \BuildOS directory has resolved the problem. I am not sure if there is an INI file that might be modified to specify the location but for now I am past the problem.