I could try it, I guess. I had thought of that, but I wasn't sure if it would work. I do not have the ustealth libfat installed by default.You probably need to exchange the bundled libfat with this: https://gbatemp.net/threads/latest-precompiled-libfat-svn-library-with-ustealth-mod.613877/
thanks. I figured that out, since it's using devkitArm. I assumed it wouldn't be using fat as that seems to be fore devkitPPC. I gave up on it, so I'm returning everything to the way it was.Wait, I was wrong. Looks like neek doesn't use libfat but FatFS: https://github.com/Tilka/sneek/blob/master/fs/ff.c - So you probably have to add UStealth support to that (that file I linked).
0xAA55
with 0xAB55
in ff.c - Not 100% sure if this will do the trick as I just looked over the code real quick and don't know the inner details of FAT but it's worth a shot. No, I mean open the ff.c sourcecode file in a text editor or IDE and search for all occurences of the text "0xAA55", then replace them with "0xAB55". Yes, I know byte ordering seems wrong but this might just be little endian (x86) vs big endian (PPC).don't you mean 55 AA and 55 AB.
55 AA 1F 37 4B CF 5E 92
in a binary file but when you write sourcecode you prefix such hex sequences with 0x
and then write the numbers, like 0x55AA1F374BCF5E92
. And we write this in hex (or use hex editors) as binary knows two numbers: 0 to 1. Hex(adecimal) knows 16 numbers: 0 to F. So this just saves a lot of writing. As a reference decimal, which is the system we all learned in scool to do math, knows 10 numbers: 0 to 9.