I am using Visual Kitchen to build my ROMs. There are five types of files that are used to eventually create the registry: *.hv *.rgu *.reg *.provxml *.xml. I'm trying to find a program that takes all these files one by one and create ONE *.rgu file. When adding keys to the One.reg the program should check whether the key exists with different value and ask the user whick value to keep. Is there a program like that? Could someone make one? I am not a programmer myself so i can't do it but i believe that this would be very useful for all cooks.
Provxml files are only added to the registry after Flash/1st Boot not during cooking process.
You could try and catch the default.hv and user.hv from the Kitchen Temp folder, to at least have those files with all the .rgu entries from the kitchen already inside them.
But i haven't seen an application that does exactly what you need it to do.
Related
Guys, before i brick my tytn i need to know whether the cooking method i'm using is correct. I'm using:
RUU-signed.nbh ---(*NBHExtract)---> OS.nb ---(NBSplit)---> OS.nb.payload -->--(ImgfsFromNb)---> imgfs.bin ---(ImgfsToDump)---> 'dump' directory, delete some files, add some files (with dsm and rgu if needed), edit initflash, edit default.hv and reverse the proces to build me the rom. The thing that wonders me if i'm doing it correct is that i'm not using the package tool to build the oem and sys dir. I'm just doing the work on the dump dir and rebuild from there. Would this be correct ?
From the dump, use bepe's package tool and convert it into SYS and OEM. Then you can add packages with .rgu, .dsm and initflashfiles.txt
Or..yeah ...that can work too. It's the old way , but you wouldn't need to add rgu's and dsm's since you make your changes right in the default.hv and user.hv, and of course, edit the initflashfiles.dat
can work or will work ... it's a big difference
btw. if i convert to oem and sys, reversing the proces starting with ImgfsFromDump errors out on me with processing OEM as module ...
Post a descriptive title for your threads.
Man, every time I see a thread titled "newbie question" or "please help" or some such nonsense it makes me wonder what these people are thinking. This thread for example, would be better titled something that indicated what you want assistance with, then if the right people see it they can respond instead of ignore it because it didn't blip their radar.
Hi all
I'm cooking my own rom using Core Pro Kitchen, so far it's going OK.
I read most of this forum and the WiKi, but still have a couple of questions
first:
Do we really need .rgu files in imgfs? AFAIK they are only used to build .hv files.
I tried to delete theese from \temp\dump before creating OS.nb (after running BuildOS), and the ROM works, at least I don't see any drawbacks.
second:
I'm cooking my own custom package into the rom and need all the files in it to be impossible to modify/delete. All files in the package have +r +s +h attributes set, but I'm sill able to modify them on device.
It seems like the modified file is created "above" the ROM one (sort of copy-on-write), because when I use TotalCommander to delete it, it just reverts to the original file from ROM. Is there anyway to make a file completely unmodifiable? Put it in XIP? do I have to rebuild any of three .dsm files in XIP if add my file there?
The file is about 1-2kb
Any ideas?
Thanks, Serge
Hi everyone,
I'm wondering about the differences between these files, since they are both used to modify registry. Well PROVXML files seems to be more powerful with file management.
Which one is better to use ?
Quick:
provxml is not only for change registry.
For file operations too.
And .provxml writes in the registry after .rgu, so if you want to change something for sure, you should use .provxml
maxstegi said:
And .provxml writes in the registry after .rgu, so if you want to change something for sure, you should use .provxml
Click to expand...
Click to collapse
Wow this is a very good point you mentionned here ... i did not know in which order the information is written into the registry. Thank you man !
But what about the order these files are dumped into the final registry ... Is it by package name ?
For example, i have in my cooking OEM:
- PACKAGE_Diamond_A
----mxipupdate_A.provxml
- PACKAGE_Diamond_B
----mxipupdate_B.provxml
What will be the result if these two packages write at the same location different value?
Will the value be the A one or B one ?
Saw something like: *_100.provxml, *_200.provxml ...
I'm pretty new to this cooking but learned a lot in the past week. I got a slimmed down rom running without problems, compressed some stuff. It works great.
However I can't figure out the registry. For example, I can edit the .rgu files directly with success. But if I add a .rgu myself, the values get overwritten with the defaults. I know they get added because I created some check values.
So basically my question is, can I add my own .rgu or .provxml file and where or do I need to edit the default .rgu files each time when cooking a new rom?
roufneck said:
I'm pretty new to this cooking but learned a lot in the past week. I got a slimmed down rom running without problems, compressed some stuff. It works great.
However I can't figure out the registry. For example, I can edit the .rgu files directly with success. But if I add a .rgu myself, the values get overwritten with the defaults. I know they get added because I created some check values.
So basically my question is, can I add my own .rgu or .provxml file and where or do I need to edit the default .rgu files each time when cooking a new rom?
Click to expand...
Click to collapse
Under SYS, I normally create my own customization folder which gets executed last (alphabetically).. e.g. folder called zzz_Customization. I then put my customization RGU and provxmls there. Nothing in the OEMs or SYS can overwrite them except for provxmls.
Actually I think the RGUs in the XIP can overwrite them but I have not tried it.
Forgot to say thanx for the tip. I got it working now.
Better use provxmls, since they get implemented last.
You can also resort to mortscripting, as it's becoming more and more popular.
A.
which function of the files with extension .DSM and .RGU within the packages. How do I create them?
marcolero said:
which function of the files with extension .DSM and .RGU within the packages. How do I create them?
Click to expand...
Click to collapse
.dsm file = this contains what there is in the folder, you can use builddsm to make them.
.rgu file = is the registery files of that folder. You can create this on by yourself in notepad. You just have to remember " REGEDIT4 " at the beginning.
the DSM files that I do in the package creator ervius are blank. what's wrong if I leave them blank?
as I use buildDsm?
grateful for the help
marcolero said:
the DSM files that I do in the package creator ervius are blank. what's wrong if I leave them blank?
as I use buildDsm?
grateful for the help
Click to expand...
Click to collapse
You can also make them blank, dosen't make the biggest' diffrent.
danny_and_2 said:
You can also make them blank, dosen't make the biggest' diffrent.
Click to expand...
Click to collapse
learned to use the buildDsm
have to drag the package into the oem folder for the buildDsm
grateful
And don't forget to save the RGU files as Unicode.
Not populating DSM files just make it harder to extract the rom correctly for beginners.
Even thought i remove .DSM, files i populate them anyway.