New BuildOS - Report Bugs Here

[gguruusa]

Originally Posted by bigdoofus

The quick way is if you aren't using patches. If you aren't, open Apache_Helmi_WM6 Selections.txt and remove the PatchDir=Patches line. Then open the kitchen. It should save just fine.

The Best way, however, is to read the very first post and see if I've already fixed the issue.

This issue was resolved shortly after the broken build was released.

This issue is also resolved in the latest release of the kitchen.

[gguruusa]

Originally Posted by Trident

This seems to be the where the failure occurs:
Failed to parse value name HKEY_CURRENT_USER\ControlPanel\Sounds!!!
InitRegistry FAILED in file ".\Registry\e54c0e41-3f65-4d9f-b104-4245cc434a86.rgu" within a few lines of line 50.
ImportFromPackageListStrict: (RGUComp) !ERROR failed importing ".\Registry\e54c0e41-3f65-4d9f-b104-4245cc434a86.rgu"
wmain: (RGUComp) !ERROR failed building DEFAULT hives

Search for e54c0e41-3f65-4d9f-b104-4245cc434a86.rgu in your kitchen. I think it's something you added to your kitchen.

[StarDestroyer]

Originally Posted by StarDestroyer

The BuildOS application runs great for me... this is actually the first time I've tried to use a kitchen and I find myself impressed and slightly overwhelmed. Anyway, I made all my selections, compiled my ROM and loaded it onto my phone as so far it's been working great (for all of 20 minutes ). My problem seems to be that I can't save my configuration.... when I try, I get the attached error (using either save or save as provides an error).

I just downloaded the 071108_1 update to both the Kitchen and the PPCGeeks_OEM and I can save my config now...

[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.

[luv2chill]

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.

[Trident]

Originally Posted by gguruusa

Search for e54c0e41-3f65-4d9f-b104-4245cc434a86.rgu in your kitchen. I think it's something you added to your kitchen.

Duh. I guess I should have known that. Looks like I had somehow screwed up my list of ringtones in that rgu file. Either that or I had forgotten to run the folder through the DSM builder. I fixed both and everything worked perfectly.
Thanks gguru.


This really is a fanfreakingtastic Kitchen/ROM.
I reinstalled and re-setup everything in record time.
And I really can't believe how beautiful this GUI is.

[gguruusa]

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]

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]

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]

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.