New BuildOS - Report Bugs Here - Page 11

**luv2chill** · #1 (**permalink**) 11-09-2007, 01:57 PM

Quote:

Originally Posted by Ryan07

I have another question regarding the Patches folder. Thanks for that heads up, by the way. It works great.

In the 3.5.1.0.4 kitchen, I edited my initflashfiles.dat to change the path of the applications that show up in the Start menu initially. I did this rather than going into settings and unchecking the boxes in Menus. With the old kitchen it was saved in the OEM_HTC folder.

With the new BuildOS, I cannot have initial access to this file since it's in the password protected rar file. Actually, I did a search in and I didn't see the file at all. I was able to pull that file out of the dump folder and make the appropriate changes as before.

What I would like to know is if I can put this new, edited file in the Patches folder and it will overwrite just as the folder was designed. It's not an OEM, per say, as it has other vital information for the OS to load (system folders and shortcuts).

Should this overwrite work?

Thanks again.

No, unfortunately it will not. initflashfiles.dat is compiled prior to the patch folder files being copied in. If you try it, net result is that you'll be missing any of the items in initflashfiles.txt files from the OEMs you selected.

The password to the rar archive is not a secret--it's "PPCGeeks" (no quotes). It's just meant to keep some degree of consistency to a kitchen build (makes it much easier to troubleshoot) and to encourage users to make all their changes via OEMs and patches.

So until we figure out what to do about initflashfiles feel free to go in there and edit it directly if you want to.

**gguruusa** · #2 (**permalink**) 11-09-2007, 02:29 PM

Quote:

Originally Posted by luv2chill

No, unfortunately it will not. initflashfiles.dat is compiled prior to the patch folder files being copied in. If you try it, net result is that you'll be missing any of the items in initflashfiles.txt files from the OEMs you selected.

The password to the rar archive is not a secret--it's "PPCGeeks" (no quotes). It's just meant to keep some degree of consistency to a kitchen build (makes it much easier to troubleshoot) and to encourage users to make all their changes via OEMs and patches.

So until we figure out what to do about initflashfiles feel free to go in there and edit it directly if you want to.

You can accomplish initflashfile changes by building a new OEM with your changed initflash files in USER_OEM. It's not perfect, as the old initflashfiles will run also, but it works.

EDIT: Luv2chill explained to me what you're doing in more detail. I'll have an improved mechanism avail soon.

Ryan07 · #3 (**permalink**) 11-09-2007, 04:41 PM

So rather than patching the initflashfiles, I'd be better to just take into a custom OEM and let it overwrite the changes? That confuses me as I thought that's what the Patches folder was for. Won't I get an error that the file already exists like I did previously?

Thanks again you guys.

Edit: Okay, disregard that. Knowing the password will give me what I need.

**gguruusa** · #4 (**permalink**) 11-09-2007, 05:02 PM

Quote:

Originally Posted by Ryan07

So rather than patching the initflashfiles, I'd be better to just take into a custom OEM and let it overwrite the changes? That confuses me as I thought that's what the Patches folder was for. Won't I get an error that the file already exists like I did previously?

Thanks again you guys.

Edit: Okay, disregard that. Knowing the password will give me what I need.

You shouldn't...initflashfiles.dat, initflashfiles.txt files, .dsm files, and .rgu files aren't handled like other files. (the Patches folder only relates to the "other files")

If you make a file called initflashfiles.dat, place it into an OEM, place that oem in USER_OEM, it will be the initflashfiles.dat that the rom is built with (regardless of uuid). You shouldn't get a duplicate files warning. You should NOT try this by modifying the initflashfiles.dat from the dump folder - you need the base initflashfiles.dat.

Ryan07 · #5 (**permalink**) 11-09-2007, 05:12 PM

Cool, thanks. I pulled the original from the rar and worked on that. I actually put it back in the rar file, but I saved a backup for good measure.

tehrob · #6 (**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** · #7 (**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.

tehrob · #8 (**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 · #9 (**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** · #10 (**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.