Quote:
Originally Posted by Soul_Est
Thanks for the quick reply on this latest development. I now know just how large the USER_OEM can be made before the available space is used up. This will help a lot. Thanks again.
-Best regards,
Soul_Est
|
Remember too, that when an oem is cooked into a rom, it is uncompressed and (close to) EVERYTHING from the OEM's resides in the \windows directory. At least a cab is compressed, and while it too will reside permanently in \windows, the user will have no problem unistalling the program, adding skins, etc. And because they are .cabs, they may actually save space as long as they don't want every .cab out there in their rom....Depending on their cabs added, it should be about the same size, and definately not as cluttered.
I was also playing with tierautoinstall briefly before I came into work, it will find cabs in the root directory of \windows and \storage card. So if a user didn't mind a cluttered \storage card, you would not have to cook them into the rom. So, if you provide a clean fast rom, users can still customize by placing their cabs on their storagecard and using tierautoinstall as long as it is cooked into the clean rom.