<reference id="GUID-8792CCC3-B70F-53FC-B394-B0069AF90349" xml:lang="en"><title>InterpretSIS</title><abstract> <p>The <codeph>InterpretSIS</codeph> tool is a PC-side

command-line tool. It can be used by device creators to install SIS

files to a data drive image that can be flashed to a device internal

drive or removable media. </p><p><codeph>InterpretSIS</codeph> can

be invoked either through BUILDROM while creating a data drive image

or as a stand-alone tool. If invoking the tool through BUILDROM, the

SIS files to be installed are listed in the OBEY file using the SISfile

keyword. For an example OBEY file, see <b> ROM Tools Guide &gt; ROM Tools

Guide &gt; Using ROM Tools &gt; Building a Data Drive Image</b>. </p> </abstract><prolog><metadata><keywords/></metadata></prolog><refbody>

<section id="GUID-3003AA1E-5C97-4568-992D-55BD949DF733"><title>Syntax</title><p><userinput>interpretsis <parmname>[OPTIONS]</parmname> <cmdname>&lt;ARGS&gt;</cmdname> </userinput> </p> <p>The following table lists

the options supported by the <codeph>InterpretSIS</codeph> tool: </p> <table id="GUID-EB7B464E-6D7A-56EB-A4DD-94352C9250DB"><title>Interpretsis

tool options</title>

<tgroup cols="3"><colspec colname="col0"/><colspec colname="col1"/>

<colspec colname="col2"/>

<entry><p>The directory representing the <filepath>Z</filepath> drive

on the device. </p> </entry>

<entry><p>(Mandatory). The directory representing the system drive

on the device. </p> </entry>

<entry><p>List of ROM or ROFS build log files. For example, see <xref href="GUID-882DCE58-5E5F-44D2-9E84-093709EAA4BE.dita#GUID-882DCE58-5E5F-44D2-9E84-093709EAA4BE/GUID-0bddead5-381b-4d8c-9437-74a4d9ef48b5">Configuring the content of ROM drive</xref>. </p> <p>This option

must not be used with <varname>-z</varname> option or define the <filepath>Z</filepath> drive in the configuration file. </p> </entry>

<entry><p><userinput> interpretsis [-r rofsbuild_log_file1,rofsbuild_log

_file2,...]</userinput> </p> </entry>

<entry><p>Disables eclipsing and SID checks using <filepath>Z</filepath> drive. The <codeph>-z</codeph> or <codeph>-r</codeph> is not required

when this option is used. </p> </entry>

<entry><p>Configuration file with HAL attribute values for installation.

For example, see <xref href="GUID-882DCE58-5E5F-44D2-9E84-093709EAA4BE.dita#GUID-882DCE58-5E5F-44D2-9E84-093709EAA4BE/GUID-b4a2d72c-95ab-44e6-8bf3-5cba3957c67e">Supporting device variant creation</xref>. </p> </entry>

see <xref href="GUID-882DCE58-5E5F-44D2-9E84-093709EAA4BE.dita#GUID-882DCE58-5E5F-44D2-9E84-093709EAA4BE/GUID-bd93fd67-d9b3-491b-802c-27cbd1038c0e">Configuring the registry version</xref>. </p> </entry>

<entry><p><userinput>interpretsis [-k [4.0 | 5.0 | 5.1 | 5.2 | 5.3

| 5.4]]</userinput> </p> </entry>

<entry><p>The log file in which the diagnostic information is stored.

By default, the information is stored in <filepath>stderr</filepath>. </p> </entry>

<entry><p>Specifies the file containing additional parameters. Command

line arguments specified after the file overrides the file contents. </p> </entry>

<entry><p>Specifies the SIS files to install.</p> <p>This option can

be used to override the drive specified in the PKG file. For example,

see <xref href="GUID-882DCE58-5E5F-44D2-9E84-093709EAA4BE.dita#GUID-882DCE58-5E5F-44D2-9E84-093709EAA4BE/GUID-5ddda82b-39b2-4240-b89b-3f796f8f8e94">Overriding the installation drive specified in the PKG file</xref>. </p> <p>The <codeph>+sucert</codeph> option can be used with this

option to indicate that the file is signed by a <codeph>SU</codeph> certificate. For example, see <xref href="GUID-882DCE58-5E5F-44D2-9E84-093709EAA4BE.dita#GUID-882DCE58-5E5F-44D2-9E84-093709EAA4BE/GUID-1df8c2ad-3bab-4b03-8245-b37826c2910d">Installing system upgrade packages</xref>. </p><p>For more information

about the options, see <xref href="GUID-8792CCC3-B70F-53FC-B394-B0069AF90349.dita#GUID-8792CCC3-B70F-53FC-B394-B0069AF90349/GUID-37F7F864-6228-56DA-A62F-43A0E6CAEA96">additional options</xref>.</p></entry>

<entry><p><userinput>interpretsis [-s [sisfile | dir] [+drive [+mcard

| +mcardnr | +mcardalone | + mcardalonenr | +nonremovablepkg] [+sucert]]]

[-s ...]</userinput> </p> </entry>

<entry><p>Removes the files installed for a package. For example,

see <xref href="GUID-882DCE58-5E5F-44D2-9E84-093709EAA4BE.dita#GUID-882DCE58-5E5F-44D2-9E84-093709EAA4BE/GUID-2e68d8df-461c-428e-9874-9b0df47072f0">Uninstalling preinstalled packages</xref>. </p> <p>This option must

not be used with <codeph>-s</codeph> option. </p> </entry>

<row>

<entry><p> <codeph>-a</codeph>  </p> </entry>

<entry/>

<entry/>

</row>

</table> <p>The following table lists the additional options that

can be used: </p> <table id="GUID-37F7F864-6228-56DA-A62F-43A0E6CAEA96">

<title>Additional options</title>

<entry><p>Generates stub SIS file for the installation package. This

is required for package propagation. </p> </entry>

<entry><p>Generates non-removable stub SIS file for the installation

package. </p> </entry>

<entry><p>Generates stub SIS file for the installation package and

does not generate the SIS Registry entry in the <filepath>$:\sys\install\sisregistry\&lt;package

UID&gt;\</filepath> directory. It just creates a preinstalled package

on the media card. </p> </entry>

<entry><p>Generates non-removable stub SIS file for the installation

package and does not generating the SIS Registry entry in <filepath>$:\sys\install\sisregistry\&lt;package UID&gt;\</filepath> directory. </p> </entry>

<entry><p>Generates a non-removable installation package.</p><note> This option converts a removable SIS file to non-removable SIS file

at install time. It reduces the effort of creating a new SIS file

with the <codeph>NR</codeph> flag during device creation.</note></entry>

<entry><p>The installed package UID either in Hexadecimal or Decimal

format (for example, 0x12345678, 305419896). </p> </entry>