Changes

350 bytes added ,  18:37, 2 March 2012
no edit summary
Line 1: Line 1: −
{{Delete | This application is Complete Bullshit™}}
  −
   
{{Infobox homebrew
 
{{Infobox homebrew
 
| title      = CiTRUS
 
| title      = CiTRUS
Line 10: Line 8:  
}}
 
}}
    +
= '''IMPORTANT''' =
 +
To use this tool, proper keys need to be supplied. For developer-unit keys, you need to be an official Nintendo 3DS developer, and have access to the official Nintendo 3DS SDK. For retail-unit keys, don't even bother.
 +
 +
= Notes from users =
 +
This application may not generate completely perfect files yet.
 +
 +
 +
== Introduction ==
 
Over the past weeks I have been working on Project CiTRUS (citrus). Currently this tool boasts the capability to output "proper" Nintendo 3DS (CTR) BaNneR and ICoN files using my XBSF format.
 
Over the past weeks I have been working on Project CiTRUS (citrus). Currently this tool boasts the capability to output "proper" Nintendo 3DS (CTR) BaNneR and ICoN files using my XBSF format.
   Line 27: Line 33:     
----
 
----
      
== USE ==
 
== USE ==
Line 68: Line 73:       −
I understand some of the misinformed users of gbatemp may think this is developer-only but in fact it can be retail signed, provided the right RSA keys. In my demo, I used a fake RSA key. When using this program, I provide you an option to specify your own RSA keys for signing. No illegal keys will be provided. The CXI is a format used by both retail and developer 3DS's, not just developer!
+
<del>I understand some of the misinformed users of gbatemp may think this is developer-only but in fact it can be retail signed, provided the right RSA keys. In my demo, I used a fake RSA key. When using this program, I provide you an option to specify your own RSA keys for signing. No illegal keys will be provided. The CXI is a format used by both retail and developer 3DS's, not just developer!</del>
 
+
This tool is practically for developer-units only.
    
Please note that this CXI has not been tested for loading but it has valid structure, a valid ExeFS (contains ARM11 code, banner, icon, and logo) and has been accepted in transformations to other formats. To the best of my knowledge this is very close to a proper CXI, if not a proper one already.
 
Please note that this CXI has not been tested for loading but it has valid structure, a valid ExeFS (contains ARM11 code, banner, icon, and logo) and has been accepted in transformations to other formats. To the best of my knowledge this is very close to a proper CXI, if not a proper one already.
604

edits