1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
2<html xml:lang="en-US" lang="en-US" xmlns="http://www.w3.org/1999/xhtml">
3  <head>
4    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
5    <meta http-equiv="Content-Style-Type" content="text/css" />
6    <link rel="stylesheet" href="../../css/manpage.css" type="text/css" />
7<title>SetSaveDataSecureValue</title>
8  </head>
9  <body>
10<h1><CODE><a href="../../nn/Overview.html">nn</a>::<a href="../../nn/fs/Overview.html">fs</a>::SetSaveDataSecureValue</CODE> Function</h1>
11<h2>Syntax</h2>
12    <div class="section">
13      <pre class="definition">
14void SetSaveDataSecureValue(
15     <a href="../../nn_types/bit64.html">bit64</a> value
16);
17
18void SetSaveDataSecureValue(
19     <a href="../../nn_types/bit64.html">bit64</a> value,
20     <a href="../../nn_types/bit64.html">bit64</a> mask
21);
22</pre>
23    </div>
24<h2>List of Overloaded Member Functions</h2>
25    <div class="section">
26      <table class="members">
27        <tr>
28          <td>
29<a href="./SetSaveDataSecureValue(0).html">SetSaveDataSecureValue ( bit64 ) </a>
30          </td>
31<td>Stores a 64-bit value in an application-linked format in the system.</td>
32        </tr>
33        <tr>
34          <td>
35<a href="./SetSaveDataSecureValue(1).html">SetSaveDataSecureValue ( bit64, bit64 ) </a>
36          </td>
37<td>Stores a 64-bit value in an application-linked format in the system.</td>
38        </tr> </table>
39    </div>
40<h2>Description of <CODE>SetSaveDataSecureValue ( bit64 ) </CODE></h2>
41<div class="section"><p>For SD applications, the 64-bit value specified by <SPAN class="argument">value</SPAN> is written to the save region in CTR system memory. The save region is unique to the application that called this function, so the same application always references the same save region. The same value is stored to the application's save data, so when you load the save data you can check whether the user has rolled back the save data by comparing this value to the value obtained by calling the <CODE><a href="../../nn/fs/VerifySaveDataSecureValue.html">VerifySaveDataSecureValue</a></CODE> function.</p><p>Nothing is done in the case of card applications.</p><!-- write here --></div>
42<h2>Description of <CODE>SetSaveDataSecureValue ( bit64, bit64 )</CODE></h2>
43<div class="section"><p>For SD applications, the 64-bit value specified by <SPAN class="argument">value</SPAN> is written to the save region in CTR system memory. However, the value written here comprises just the bits as specified by the <SPAN class="argument">mask</SPAN> argument, and bits not part of <SPAN class="argument">mask</SPAN> are maintained as their original values. The save region is unique to the application that called this function, so the same application always references the same save region. The same value is stored to the application's save data, so when you load the save data you can check whether the user has rolled back the save data by comparing this value to the value obtained by calling the <CODE><a href="../../nn/fs/VerifySaveDataSecureValue.html">VerifySaveDataSecureValue</a></CODE> function.</p><p>Nothing is done in the case of card applications.</p><!-- write here --></div>
44  <hr><p>CONFIDENTIAL</p></body>
45</html>