Thread: For those that need a personalized OEM for their ROMS!!!!!
View Single Post
  #47 (permalink)  
Old 08-18-2007, 01:43 AM
gguruusa's Avatar
gguruusa
Deep Thinker
Offline
Location: Mountain top
  
Join Date: Jan 2007
Posts: 3,252
Reputation: 4726
gguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributionsgguruusa should be added to the payroll for their contributions
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quote:
Originally Posted by tiermann
PS: WTF is a dsm file anyway, and how does buildDSM come up with the gibberish in the file, hehe. I would like to incorporate this into OEMizer instead of having to shell to another app.
A .dsm file basically defines hardware/OS base requirements, module name, unique IDs, certificates, components, and dependencies. It's kind of like a .cab's .inf file in binary.

Generating a real .dsm (like BuildOS does) takes some magic that only a few possess, to my knowledge. BuildDSM makes a half-assed .dsm that if you're really determined you can replicate for simple OEM folders. It's not worth the effort unless you are seriously bored.
Reply With Quote