/INPUT=filename
Specifies that the value data is to be read from a file.
The input value data can be specified in one of the following
formats. With the exception of SZ, the format is specified by a
keyword at the start of the file. The keyword can be entered in
uppercase or lowercase. Input records following a keyword can
span multiple lines; use "\" at the end of any continuation lines.
o SZ: a null-terminated Unicode string
Enter SZ data by enclosing the record in quotes. You do
not specify an SZ keyword for this input value type.
You cannot continue the quoted string to a second line.
"This is Unicode Data."
o DWORD: A 32-bit number.
The data following the DWORD keyword is interpreted as
a single, 32-bit value. It can be entered as a single
value or as a list of values, separated by commas, with
the least significant value first, provided the total
is 32 or fewer bits.
For example, the following valid specifications are
equivalent:
dword:44332211 DWORD:11,22,33,44 Dword:2211,4433
The following specifications are invalid because the total
always exceeds 32 bits:
dword:5544332211
dword:11,22,33,44,55
dword:2211,554433
o EXPAND_SZ: A string of Unicode characters. The data
following the EXPAND_SZ keyword is interpreted as a list
of 4-byte Unicode values. For example:
expand_sz:43,44,45
This example stores the Unicode string "CDE".
o MULTI_SZ: A concatenated array of SZ strings. The data
following the MULTI_SZ keyword is interpreted as a list of
4-byte Unicode values, specifying two or more terminated SZ
strings. For example:
MULTI_SZ:52,61,69,6e,00,53,6c,65,65,74,00,53,6e,6f,77,00
This example stores the Unicode strings "Rain", "Sleet", and
"Snow".
o HEX: Binary data. The data following the HEX keyword is
interpreted as a list of hex values. For example:
HEX:0F,C0,F0,FF
o DEC: Binary data. The data following the DEC keyword is
interpreted as a list of decimal values. For example:
DEC:15,192,240,255
o OCT: Binary data. The data following the OCT keyword is
interpreted as a list of octal values. For example:
OCT:17,300,360,377
o BIN: Binary data. The data following the BIN keyword is
interpreted as a list of binary values. For example:
BIN:1111,11000000,11110000,11111111
NOTES
o The input format is similar to the IMPORT and EXPORT file format.
o The input data type is independent of the data storage type, which
is specified by the /TYPE_CODE qualifier.
o When you specify a binary input type (HEX, DEC, OCT or BIN)
for each value in the record, the data is stored in the fewest
bytes possible. No alignment is performed. To insure proper
alignment, always enter any list of values as byte values.
This input should be a stream of byte values, with the
least significant byte first. For example:
DEC:253, 254, 255, 256, 257 (bytes/words, unaligned)
DEC:253, 0, 254, 0, 255, 0, 256, 257 (bytes/words, word aligned)
DEC:253, 0, 254, 0, 255, 0, 0, 1, 0, 2 (byte stream, word aligned)
o The input and storage types must be compatible. For example,
you cannot specify value type DWORD (which means that the
stored data is 4 bytes) and then input the SZ string "A"
because then the SZ string would consist of the character
00000041 and the terminator 00000000, which cannot fit in a
DWORD. Attempting this will result in a REG-E-INVDATA error.
However, specifying an empty string ("") does work and stores
just the terminator. Conversely, the input type DWORD specifies
an input data length of 4 bytes. You cannot specify value type
SZ and input type DWORD:00000041 because SZ strings must be
terminated. The only valid DWORD you can enter in this case is
00000000.
o When specifying /INPUT, you cannot specify the /DATA qualifier.