Reviewed By: Sous-Chef
In early kitchen and ROM cooking, chefs used to delete Device Side Manifest (.DSM) files from OEM packages that resided in the .\PACKAGES and/or .\EXT folder. Other chefs would delete the .DSM file and create an empty version of a .DSM file as a placeholder. As we learned more about the Windows Mobile, we discovered that .DSM files contained pertinent information that was used during the compilation of a ROM and should be properly managed. BuildDSM is a utility to create an initial .DSM file or update an existing .DSM file..
A Device Side Manifest file (.DSM) describes the contents of a package and has the name <GUID>.DSM. Each package has its own .DSM file. The .DSM file is a binary file and the format may change at any time. The .DSM file is created by parsing a package definition file, package shadow file, and a build manifest file. Each item specified within a build manifest file is used to determine the item's file type.
The .DSM file contains the following information:
- Public key certificate data used for signature validation.
- Version information which includes the previous version of a package so as to create a delta package between an older or baseline package and a new package.
- Package GUID
- Dependency GUID information
- File names and file information in the form of raw file size and original VBase for MODULES so they can be re-based and differentiated during an update.
- Renaming an empty .TXT file to .DSM will allow the tool to update the file with the known .DSM file information.
- Drag-and-drop a package folder that contains a .DSM file onto BUILDSM.EXE.
- The .DSM created may not contain all of the information required as the tool is outdated.
- Requires an existing .DSM file in the directory - empty or other.
- Requires Microsoft Visual C++ 2005 SP1 Redistributable Package (x86).