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>VerifySaveDataSecureValue</title>
8  </head>
9  <body>
10    <h1><CODE><a href="../../nn/Overview.html">nn</a>::<a href="../../nn/fs/Overview.html">fs</a>::VerifySaveDataSecureValue</CODE> Function</h1>
11    <h2>Syntax</h2>
12    <div class="section">
13      <pre class="definition">
14bool VerifySaveDataSecureValue(
15     <a href="../../nn_types/bit64.html">bit64</a> value
16);
17
18bool VerifySaveDataSecureValue(
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="./VerifySaveDataSecureValue(0).html">VerifySaveDataSecureValue ( bit64 ) </a>
30          </td>
31          <td>Performs comparison with application-linked, 64-bit value.</td>
32        </tr>
33        <tr>
34          <td>
35            <a href="./VerifySaveDataSecureValue(1).html">VerifySaveDataSecureValue ( bit64, bit64 ) </a>
36          </td>
37          <td>Performs the comparison with an application-linked, 64-bit value.</td>
38        </tr> </table>
39    </div>
40    <h2>Description of <CODE>VerifySaveDataSecureValue ( bit64 )</CODE></h2>
41    <div class="section"><p>For downloadable applications, gets the 64-bit value from the save region in CRT System Memory that was written there by the <CODE><a href="../../nn/fs/SetSaveDataSecureValue.html">SetSaveDataSecureValue</a></CODE> function, and compares this with <SPAN class="argument">value</SPAN>. The save region is unique to the application that called this function, so the same application always references the same save region.</p><p>If this function is called with the factory defaults or immediately after initializing the system, the values in the internal memory are treated as <CODE>0</CODE> for processing. Immediately after these initializations occur, the save data for the download application should be in an uninitialized state. If the save data is not initialized, do not make the assumption that the internal memory values are <CODE>0</CODE>. Even when you have not performed any processing that corresponds to <CODE>SetSaveDataSecureValue(0)</CODE>, such as downloading an application again, it is possible that the save data is in an uninitialized state. In short, do not call this function if the save data has not been initialized.</p><p>If the physical memory chips for a system were replaced to repair damage, or the system experienced corrupted internal memory data, the values in the internal memory are treated as <CODE>0</CODE> for processing, the same as for factory defaults. In these cases, because this function is called when the value is not <CODE>0</CODE>, the function returns <CODE>FALSE</CODE>. In other words, the passed value is not valid. If you cannot allow save data to become unusable because of repairs of damage to the internal memory, call the <a href="../../nn/fs/VerifySaveDataSecureValueLoosely.html"><CODE>VerifySaveDataSecureValueLoosely</CODE></a> function instead.</p><p>When this function is called from a card application, it always returns <CODE>TRUE</CODE>.</p><!-- write here --></div>
42    <h2>Description of <CODE>VerifySaveDataSecureValue ( bit64, bit64 )</CODE></h2>
43    <div class="section"><p>For downloadable applications, gets the 64-bit value from the save region in CRT System Memory that was written by the <CODE><a href="../../nn/fs/SetSaveDataSecureValue.html">SetSaveDataSecureValue</a></CODE> function, and compares this with <CODE>value</CODE>. No comparison is made on bits that are not set in the <SPAN class="argument">mask</SPAN> argument. The save region is unique to the application that called this function, so the same application always references the same save region.</p><p>If this function is called with the factory defaults or immediately after initializing the system, the values in the internal memory are treated as <CODE>0</CODE> for processing. Immediately after these initializations occur, the save data for the download application should be in an uninitialized state. If the save data is not initialized, do not make the assumption that the internal memory values are <CODE>0</CODE>. Even when you have not performed any processing that corresponds to <CODE>SetSaveDataSecureValue(0)</CODE>, such as downloading an application again, it is possible that the save data is in an uninitialized state. In short, do not call this function if the save data has not been initialized.</p><p>If the physical memory chips for a system were replaced to repair damage, or the system experienced corrupted internal memory data, the values in the internal memory are treated as <CODE>0</CODE> for processing, the same as for factory defaults. In these cases, because this function is called when the value is not <CODE>0</CODE>, the function returns <CODE>FALSE</CODE>. In other words, the passed value is not valid. If you cannot allow save data to become unusable because of repairs of damage to the internal memory, call the <a href="../../nn/fs/VerifySaveDataSecureValueLoosely.html"><CODE>VerifySaveDataSecureValueLoosely</CODE></a> function instead.</p><p>When this function is called from a card application, it always returns <CODE>TRUE</CODE>.</p><!-- write here --></div>
44  <hr><p>CONFIDENTIAL</p></body>
45</html>