[bdusmc]

Hey all,

I've tried to search for some info on this question and I keep coming up with useless results, so I figured I will just ask the question...

Can someone explain to me what is in the ROM folder of a kitchen?

The only conclusion that I have come to so far is that using a different "ROM" folder in conjunction with the same SYS and OEM folders seems to affect the "D" version number at boot up (the red text on the boot screen of the Diamond), which I presume is some kind of bootstrap file version or something. Some combinations of ROM/SYS folders will boot, some won't, which is why I figure it's a bootstrap file.

I have been experimenting with cooking my own ROMs and don't really feel comfortable releasing them to the wild until I understand what I am messing with, if you know what I mean.

If there is a tutorial online that someone can point me to, that would be awesome, but these are the two specific questions that I have:

ROM folder .nb Files:
What is the .nb file - I have X number of SYS versions downloaded to cook with, and the size of the .nb file varies anywhere from 2M to 8M, as does the filename (I have os.nb, base.nb, OS.nb.payload, to name a few).

XIP folder .rgu Files:
My guess is that it's a core framework for a registry hive... Is this used to construct the registry and then discarded? Is it usually tweaked by the chef's out there? What is XIP Porting?

Any insight into the core of ROM cooking would be invaluable... I would really like to experiment with this more seriously but up to this point it's all been a lot of trial and error... I could save myself a lot of frustration if I could find a good resource somewhere to read up on this!

Here's a huge thanks in advance!
BullDog