View Single Post
  #7 (permalink)  
Old 01-19-2009, 08:13 PM
Kolano's Avatar
Kolano
Regular 'Geeker
Offline
 
Join Date: May 2007
Posts: 422
Reputation: 71
Kolano is becoming a great contributor
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Question for our ROM cookers regarding program and storage memory of ROMS

Quote:
Originally Posted by aaronvlee View Post
So can you break down the process of how the apps are installed when the rom is first flashed? Is it cabs?
There are typically no CABs. The ROMs typically have files as if they had been installed to the \Windows folder. The process of flashing requires a copy of everything in the ROM to be there, so although some programs require files within certain subdirectories or locations outside of \Windows, any such files are typically copies of files from within \Windows.

Basic rundown would be...
  • A set of OEM packages and other files are selected
  • Kitchen tools parse these packages Merging some content/excluding some other content, but basically copying selected files together into a single folder.
  • This set of files is processed into a ROM.
  • Someone loads the ROM. Clearing their Storage/ROM memory, but leaving storage cards (or similar additional storage) untouched. Any actions taken from here on take up storage space.
  • Initialization scripts run on initial bootup. These may copy files, run CAB installations, etc. However, most software is already in a pre-installed state, and does not require these steps.
Reply With Quote