Menuhax support won't be possible with a 90kb binary size, but I'm not sure of the details why (just repeating what Tux said)No. Maybe menuhax, but I'll make no effort for mset or gateway.
Menuhax support won't be possible with a 90kb binary size, but I'm not sure of the details why (just repeating what Tux said)No. Maybe menuhax, but I'll make no effort for mset or gateway.
Still hangs up, you know a place i could get a good firm key?
Menuhax support won't be possible with a 90kb binary size, but I'm not sure of the details why (just repeating what Tux said)
Could that be done by adding macros to the assembler? A proper macro assembler can be ridiculously powerful, far more so than the anaemic ones commonly available for todays mainstream systems.That could be part of the assembler and I could simply compile that to jmp, but then it isn't actually an "assembler" anymore. The less comparisons in the VM, the better. ;P
Could that be done by adding macros to the assembler? A proper macro assembler can be ridiculously powerful, far more so than the anaemic ones commonly available for todays mainstream systems.
Maybe there is a workaround actually, but if it's possible it's not straightforward (and likely not compatible with boot managers and such). I don't really know.Menuhax support won't be possible with a 90kb binary size, but I'm not sure of the details why (just repeating what Tux said)
Maybe there is a workaround actually, but if it's possible it's not straightforward (and likely not compatible with boot managers and such). I don't really know.
I am well aware of that, which is why I posted this. Besides, it'd be an advantage because iirc it can load raw ARM9 payloads (arm9loaderhax style)0x100000 is not 90kb. 0x100000 is 1048576 bytes, or 1MB.
I am well aware of that, which is why I posted this. Besides, it'd be an advantage because iirc it can load raw ARM9 payloads (arm9loaderhax style)
CakeHax implies mset/spiderhax support. In any case, what you want is CakeBrah (*hax).I quickly edited with a thanks because I was a bit terse. Apparently I was too late. ;/
Right now I want to focus on getting all of the features working, but it doesn't look like it'll be hard to add CakeHax as a submodule or anything.
m4 is a thing. Could always just use m4 to preprocess your stuff.Could that be done by adding macros to the assembler? A proper macro assembler can be ridiculously powerful, far more so than the anaemic ones commonly available for todays mainstream systems.
m4 is a thing. Could always just use m4 to preprocess your stuff.
Yeah, I just thought that putting higher level stuff like if/then logic into the assembler would be a better idea than adding complexity to the VM.It's not impossible, but it's not on my priority list at the moment.
Yeah, I just thought that putting higher level stuff like if/then logic into the assembler would be a better idea than adding complexity to the VM.
Maybe because i haven't name it correctly, i renamed firmkey.bin to native.key.It still hangs in release-3? It shouldn't. It should be skipping invalid AGB and TWL firms. I deliberately broke my firmware files in N different ways to test.
As for the FIRM key, you can either do some trickery with cakes, go find it at unspeakable places, or wait for the next release when I re-add the cetk code to the firm decryptor. Your choice.
I'm assuming that's the maximum payload size of the actual theme cache, from reading through the docs. Doesn't really matter much, anyways.