New BuildOS - Report Bugs Here

[luv2chill]

Originally Posted by schettj

I'll give it a shot.

The question is, which size? The size on disk for any OEM is knowable. The size that OEM will take in rom is not, since the ROM itself is compressed pretty heavily during build. So, for example, my current rom selections take a bit more then 100MB on disk just before they are churned into a rom image, and then (after much crunching) they end up wedged into the 60MB or so for the rom. You could say that the size used in rom is 3/5ths of the disk size, but you'd be wrong more often then not.

Couldn't have said it any better.

[gguruusa]

Originally Posted by schettj

I'll give it a shot.

The question is, which size? The size on disk for any OEM is knowable. The size that OEM will take in rom is not, since the ROM itself is compressed pretty heavily during build. So, for example, my current rom selections take a bit more then 100MB on disk just before they are churned into a rom image, and then (after much crunching) they end up wedged into the 60MB or so for the rom. You could say that the size used in rom is 3/5ths of the disk size, but you'd be wrong more often then not.

that's actually the easy part of it

To do it right, you need incremental building...which fundamentally is a different architecture. In the short run, I'm making a solution that will approximate the in ROM size, but won't be exact...so if you try to fill every last little byte, it may take you a couple iterations, but you'll have a fair indication of when you're near the edge.

[Ryan07]

*Should I start a new thread on this since it's technically not a Bug?*

I edited and replaced initflashfiles.dat in the OEM_Lang_0409 and built my ROM. On the first boot, The top bar came up but the WM logo stayed up on my today screen. The phone had an X over it. I couldn't get any of the buttons to recognize except Start+D. I aligned the screen and could then get to my today screen.

The problem then was the file I edited only partially ran. The start menu was totally jacked and I basically couldn't do anything. There was no Settings folder and the Programs folder only contained Windows Medie Player. Where the Menu items would be normally, coldinit and one other file were listed. They normally go in the Startup folder and are hidden.

So, I started over. I put the default file back in the OEM and added my edited version to a custom OEM as suggested. The result is the same. So basically that file, with this new format, cannot be edited. Or, you know, I'm doing something wrong. It's like the file partially processes, but skips the entire top portion where folders are created. I didn't remove any entries. I only commented out the items I do not want to run and changed the Menu entries from Start Menu to Start Menu\Programs.

I've attached the file for someone to go over along with my WM5 kitchen file that always worked.

Thanks smart people.
.

[luv2chill]

Originally Posted by Ryan07

*Should I start a new thread on this since it's technically not a Bug?*

I edited and replaced initflashfiles.dat in the OEM_Lang_0409 and built my ROM. On the first boot, The top bar came up but the WM logo stayed up on my today screen. The phone had an X over it. I couldn't get any of the buttons to recognize except Start+D. I aligned the screen and could then get to my today screen.

The problem then was the file I edited only partially ran. The start menu was totally jacked and I basically couldn't do anything. There was no Settings folder and the Programs folder only contained Windows Medie Player. Where the Menu items would be normally, coldinit and one other file were listed. They normally go in the Startup folder and are hidden.

So, I started over. I put the default file back in the OEM and added my edited version to a custom OEM as suggested. The result is the same. So basically that file, with this new format, cannot be edited. Or, you know, I'm doing something wrong. It's like the file partially processes, but skips the entire top portion where folders are created. I didn't remove any entries. I only commented out the items I do not want to run and changed the Menu entries from Start Menu to Start Menu\Programs.

I've attached the file for someone to go over along with my WM5 kitchen file that always worked.

Thanks smart people.
.

First thing's first--the file you attached was called BOS_initflashfiles.dat.txt. Did you add the .txt extension in order to attach it to this message or was it there all along? If so, that's your problem. Make sure in Windows you have the Folder Options->View tab->Hide extensions for known file types UNCHECKED so that Windows will always show you the whole file name, including the extension. Otherwise you would see initflashfiles.dat but Windows would hide the .txt, which it considers to be the true extension of the file.

If you added the .txt just to be able to attach the file, reply back and we'll go from there.

[Ryan07]

Yes, that was simply to be able to add the attachment. One from BuildOS and one from the 3.5.1.0.4 kitchen.

Hurray, my first post from my phone!

[gguruusa]

Originally Posted by Ryan07

The result is the same. So basically that file, with this new format, cannot be edited. Or, you know, I'm doing something wrong.

I'm going to go with the 2nd option

I haven't looked at your files yet, but it's definitely something you're doing wrong.

[sagamoredad]

First off the whole thing is awesome. The following are a couple of issues I am having with the OEMizer:

1. The address in the Owners info doesn't seem to stick. I save it as a default but when I close it and come back it is blank. All other fields are OK. Once they are in the OEM folder they make it to the phone just fine.

2. For both the POP3/IMAP4 and MAil2Web/Exchange radio buttons. When I select either one I cannot enter any data in the fields. Everything is just greyed out.

3. For the Inernet & PIE field I cannot get the hompeage to transfer to the phone. I can enter the fields OK and they seem to be saved correctly but they don't get to the phone.

4. Not sure if this is Kitchen or OEMizer. I was able to add my personal theme and it made it to the phone and shows up as the selected theme. However the phone is still displaying the default theme. It only takes effect when I select another theme and go back to my personal theme.

I am using the kitchen, tools and OEM files from the 071108_1 build.


Also can anyone give some "big picture" help and explain to a noob how to use the features in the "files & shortcuts", "additional registry entries", "autorun" and the patches folder?

Thanks in advance and keep up the friggin awesome work !!!!!

[verizonguy]

Originally Posted by sagamoredad

First off the whole thing is awesome. The following are a couple of issues I am having with the OEMizer:

1. The address in the Owners info doesn't seem to stick. I save it as a default but when I close it and come back it is blank. All other fields are OK. Once they are in the OEM folder they make it to the phone just fine.

2. For both the POP3/IMAP4 and MAil2Web/Exchange radio buttons. When I select either one I cannot enter any data in the fields. Everything is just greyed out.

3. For the Inernet & PIE field I cannot get the hompeage to transfer to the phone. I can enter the fields OK and they seem to be saved correctly but they don't get to the phone.

4. Not sure if this is Kitchen or OEMizer. I was able to add my personal theme and it made it to the phone and shows up as the selected theme. However the phone is still displaying the default theme. It only takes effect when I select another theme and go back to my personal theme.

I am using the kitchen, tools and OEM files from the 071108_1 build.


Also can anyone give some "big picture" help and explain to a noob how to use the features in the "files & shortcuts", "additional registry entries", "autorun" and the patches folder?

Thanks in advance and keep up the friggin awesome work !!!!!

Yeah, so this is the BuildOS bugs thread, not OEMizer thread

[daveedem]

Thought I'd move my one post over here instead since it's really build OS.

BUILDOS question ---- I put tiermann's split Office files in the UserOEM folder. Now whenever I go back into the build OS it tellsme "required module not in project Module Office Excel", then a ref number. I have to do this for each of the 3 folders, Word, PP and Excel. BUT once BuildOS comes up, they are listed in the selections area. and they install properly.

Not really a bug, just a nuisance.

I really like the fact I can save my settings from previous flashes.....

[GaMedic]

Originally Posted by daveedem

Thought I'd move my one post over here instead since it's really build OS.

BUILDOS question ---- I put tiermann's split Office files in the UserOEM folder. Now whenever I go back into the build OS it tellsme "required module not in project Module Office Excel", then a ref number. I have to do this for each of the 3 folders, Word, PP and Excel. BUT once BuildOS comes up, they are listed in the selections area. and they install properly.

Not really a bug, just a nuisance.

I really like the fact I can save my settings from previous flashes.....

Did you put the Hidden-Office-Requirements folder into OEM?