OEM packages vs. Ext ROM

[lurker525]

I've started trying to cook my own rom for my wing and I've come to a bit of a cross roads on how to do certain things. I was wondering if I could get some other cook's opinions and advice on how they install programs while cooking a rom.
I've figured out how to change what is contained in the Extended ROM and was wondering why no seems to use it for including certain apps in their roms?
A good example would be S2U2. Alot of roms I've seen include it but why install it as a package when you could just run the cab from the extended rom?
It seems a little wasteful of space especially with a program updated as frequently as this one to have it sit resident in the rom if you overwrite it with a new version.
Is there a particular reason no one seems to change the extended rom and put it out there with the OS as an OS.nbh?

[ivanmmj]

The os.nb within the nbh has to be at least 51,200kb large. If it isn't and you padded to that size with just zero's in a hex editor, then you will have lost a lot of storage space. If you place it on the os.nb, then you will not have to use your storage space to store it.

[lurker525]

Excellent point. I think that is makes sense for most apps that don't get updated very often to install them in the main rom. But for anything thats going to be updated frequently, for me it makes more sense to be able to upgrade without losing additonal space on the device. Besides there is more than enough useful apps out there for me to pad out my base rom.

[EvgeniX]

but if I have os.nb within the nbh > 51,200kb - what different after :confused: