New BuildOS - Report Bugs Here - Page 10

tehrob · #91 (**permalink**) 11-09-2007, 11:21 PM

I don't know if this has been mentioned before, and it is more of a feature request than a bug... but technically... anyway.

I was wondering if it would be possible to add a SIZE column to the kitchen interface, and also to add up the size(approximate) of the ROM you are about to build. It takes a bit of time to get the "Out of memory" error, and it seems it would be nice as to help maximize usefulness of the ROM area. Thanks, and great job!

**luv2chill** · #92 (**permalink**) 11-09-2007, 11:28 PM

Quote:

Originally Posted by tehrob

I don't know if this has been mentioned before, and it is more of a feature request than a bug... but technically... anyway.

I was wondering if it would be possible to add a SIZE column to the kitchen interface, and also to add up the size(approximate) of the ROM you are about to build. It takes a bit of time to get the "Out of memory" error, and it seems it would be nice as to help maximize usefulness of the ROM area. Thanks, and great job!

Heh I think you're about the 100th requestor of that.

Gguru is working on it but it's going to be very difficult to implement properly.

Slwitek · #93 (**permalink**) 11-10-2007, 12:04 AM

I got my XP machine to work for a min, and I have successfully flashed the new rom. I look forward to a fix for Vista. I tried every thing on this board and it still wouldnt work.

tehrob · #94 (**permalink**) 11-10-2007, 03:25 AM

Quote:

Originally Posted by luv2chill

Heh I think you're about the 100th requestor of that.

Gguru is working on it but it's going to be very difficult to implement properly.

Hey, at least I'm not second.

Jimberly · #95 (**permalink**) 11-10-2007, 07:46 AM

Quote:

Originally Posted by luv2chill

Heh I think you're about the 100th requestor of that.

Gguru is working on it but it's going to be very difficult to implement properly.

For my own edification, can you explain in general terms why that is? I'm not complaining, just curious. Thanks.

**schettj** · #96 (**permalink**) 11-10-2007, 10:24 AM

Quote:

Originally Posted by Jimberly

For my own edification, can you explain in general terms why that is? I'm not complaining, just curious. Thanks.

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.

Ryan07 · #97 (**permalink**) 11-10-2007, 10:27 AM

*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** · #98 (**permalink**) 11-10-2007, 11:25 AM

Quote:

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.

**luv2chill** · #99 (**permalink**) 11-10-2007, 11:29 AM

Quote:

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** · #**100** (**permalink**) 11-10-2007, 12:34 PM

Quote:

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.