BinMod Tool (Windows Embedded CE 6.0)
1/6/2010
The BinMod Tool (binmod.exe) extracts files from a run-time image, and replaces files in a run-time image.
binmod [-i imagename] [-r replacement_filename.ext | -e extraction_filename.ext]
Parameters
-iimagename
File name of the .bin file to stamp. The default is nk.bin.
-rreplacement_filename.ext
File name of the file for replacement.
-eextraction_filename.ext
File name of the file for extraction.
Examples
The following command-line syntax extracts filename.ext out of the run-time image. The file can be any file within the tools limitations, such as a text file, a dynamically-linked library (DLL), and so on:
binmod –i nk.bin –e filename.ext
You can use BinMod to insert a placeholder file of the correct stamp size into the run-time image, and then run the -r command in a loop in a batch file to find the placeholder file in the image, and then replace it with a file that contains the stamp for the run-time image.
For more information about stamping, see Stamping a Run-Time Image.
Remarks
To stamp multiple run-time images, use the BinMod tool with a batch file. Otherwise, you must manually navigate the Platform Builder IDE to stamp each run-time image.
The BinMod tool can can only be used with .bin run-time images, and it can only be used on files in the FILES section of the run-time image. If the file is the same size or smaller than the original module, taking compression into account, replacement is guaranteed for any file in the FILES section. If the new file is larger, the BinMod tool makes a best effort to find free space in the run-time image. If there is no free space available, the file will not be replaced. If there is free space available, the space occupied by the original file is no longer useful. Typically this is not a problem, because the files that are usually replaced are uncompressed text files that are adjusted to the final expected size and the file and run-time image remain the same size.