Page history
17 August 2023
28 July 2020
10 June 2018
10 April 2018
8 January 2018
9 December 2017
4 October 2017
3 October 2017
TID 0004009b00010202 seems to get its content ID 0 accessed with 0x2? MSET's manual (index 1) is accessed with 0x5 and 0x1 seems to be the norm for most archive's content index 0.
+10
no edit summary
+68
25 March 2017
12 February 2017
10 February 2017
29 November 2016
23 November 2016
24 October 2016
19 October 2016
17 October 2016
Undo revision 18425 by Neobrain (talk): this makes no sense, that's not how it works
-225
(conclusion drawn from https://www.3dbrew.org/w/index.php?title=AM:ImportTwlBackup&curid=793&diff=18423&oldid=16892 )
+225
13 September 2016
6 September 2016
5 September 2016
4 September 2016
Courtesy of fincs, be ridiculously pedantic
+22
Explicitly denote character encoding (according to ctrulib).
+2
1 September 2016
29 August 2016
6 August 2016
1 June 2016
19 May 2016
No idea what this was supposed to mean (OpenFile returns kernel handles, which are inherently different from archive handles), and it seems rather confusing than helpful.
-67
Rephrase for clarity. In particular it's more clear that this is exactly the lvl3 image, not more and not less.
-56
→RomFS
+25
18 May 2016
→Archives
+11
Fixup header levels
-18
Same for the path format.
+21
While this is technically a "common type", it's central enough to the FS design to deserve its own toplevel section.