Checkpoint method of the Control class
If the current configuration is a result of the Undo/Redo/Restore, marks it as if it has been set explicitly, so that the history will preserve the time when it was set, and a backup file will be created for it on the next configuration change. If the current configuration was already set explicitly, has no effect.
Syntax
Uint32 Checkpoint(
[in] Uint32 OldTimestampLow,
[in] Uint32 OldTimestampHigh,
[out] string ErrorString,
[out] string WarningString,
[out] string InfoString,
[out] uint32 ErrorType
);
Parameters
-
OldTimestampLow [in]
-
The timestamp of when the current configuration was set. If not 0, enables the atomicity check: the action will be applied only if the timestamp of the old configuration matches (i.e. the configuration was not changed in between). This is the low part of FILETIME.
-
OldTimestampHigh [in]
-
The timestamp of when the current configuration was set. If not 0, enables the atomicity check: the action will be applied only if the timestamp of the old configuration matches (i.e. the configuration was not changed in between). This is the high part of FILETIME.
-
ErrorString [out]
-
The text string with explanation of the error.
-
WarningString [out]
-
The text string with warnings.
-
InfoString [out]
-
The text string with information about the configuration.
-
ErrorType [out]
-
The type of the error. Note that 0 or absent indicates success.
-
0
-
Success.
-
1
-
bad argument format
-
2
-
bad argument value
-
3
-
resource (socket) open error
-
4
-
persistence (file write) error
-
5
-
atomicity error (the old timestamp didn't match)
Return value
-
0
Failure
-
1
Success
Requirements
Requirement | Value |
---|---|
Minimum supported client |
Windows 10 [desktop apps only] |
Minimum supported server |
Windows Server 2016 |
Namespace |
Root\Microsoft\Windows\BootEventCollector |
Header |
|
MOF |
|
DLL |
|