To prevent disasters, this flag is ignored during installation if Subkey is blank or contains only backslashes. This flag can be combined with uninsdeletevalue. When the program is uninstalled, delete the key if it has no values or subkeys left in it. You should only use this on keys private to your application. It obviously wouldn't be a good idea to use this on a key that is used by Windows itself. When the program is uninstalled, delete the entire key, including all values and subkeys in it. This flag cannot be combined with the uninsdeletekey flag. When the program is uninstalled, set the value's data to a null string (type REG_SZ). If the value did exist and is a string type, it will be replaced with the same value type as the pre-existing value. When this flag is specified and the value did not already exist or the existing value isn't a string type (REG_SZ or REG_EXPAND_SZ), it will be created with the type specified by ValueType. This is only applicable when the ValueType parameter is string or expandsz. noerrorĭon't display an error message if Setup fails to create the key or value for any reason. Typically this flag is used in combination with the uninsdeletekey flag, for deleting keys during uninstallation but not creating them during installation. No error message is displayed if the key does not exist. When this flag is specified, Setup will not attempt to create the key or any value if the key did not already exist on the user's system. If ValueType is not none, it will then create the key if it didn't already exist, and the new value. When this flag is specified, Setup will first try deleting the value if it exists. If ValueType is not none, it will then create a new key and value. When this flag is specified, Setup will first try deleting the entire key if it exists, including all values and subkeys in it. This flag has no effect if the data type is none, or if you specify the deletevalue flag. When this flag is specified, Setup will create the value only if a value of the same name doesn't already exist. The following options are supported: createvalueifdoesntexist Multiple options may be used by separating them by spaces. This parameter is a set of extra options. This parameter can include one or more space separated values in the format: (There is no such limitation on 圆4 editions of Windows.) On Itanium editions of Windows, this parameter is only effectual on 32-bit registry keys. The permissions are not set if ValueType is none and the deletekey flag or deletevalue flag is used. The specified permissions are set regardless of whether the registry key existed prior to installation. Never change the ACLs on a top-level key like HKEY_LOCAL_MACHINE\SOFTWARE, otherwise you can open up security holes on your users' systems. This parameter should only be used on registry keys private to your application. In the event these conditions are not met, no error message will be displayed, and the permissions will not be set. It is not recommended that you use this parameter if you aren't familiar with ACLs or why you would need to change them, because misusing it could negatively impact system security.įor this parameter to have an effect the current user must be able to change the permissions on the registry key. Specifies additional permissions to grant in the registry key's ACL (access control list). On a string, expandsz, or multisz type value, you may use a special constant called in this parameter to embed line breaks (nulls). If the data type is none, this is ignored. If the data type is binary, this is a sequence of hexadecimal bytes in the form: "00 ff 12 34". "$7B"), or a constant which resolves to an integer. If the data type is dword or qword, this can be a decimal integer (e.g. If the ValueType parameter is string, expandsz, or multisz, this is a string that can include constants.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |