If I export the whole banner.bin file using ndstool in a dsi-enhanced, that file is sized 0x840, just as the non-dsi-enhanced titles
But now that you mention it, I opened the raw nds dsi-enhanced title and jumped to where it's supposed to be the icon (above the 6 language name, right?), and it seems to be more bigger than the exported with ndstool. So I have a lot of doubts.
1) Is ndstool broken? I am using it wrong? I use 'ndstool -x dsi-enhanced_rom.nds -t banner.bin -h header.bin', with every nds file, and as I said, the size of those files are always 0x840 for banner.bin and 0x200 for header.bin
2) I can detect which roms are dsi-enhanced in my tool, but i don't really know what to do then with those.
3) If I read the raw dsi-enhanced nds, how can I know the offset of the giant (0x23C0) banner? Is it so big due to it's animated?
4) 0x23C0 is the size of dsi-enhanced banners, do you mean the whole banner, including extra data, such as it's own header and also the 6-lang game names? Or you mean just the raw game icon?
5) Then, assuming I have the raw dsi-enhanced icon (where is the animation data?), how can I inject that in a no-animated dsiware game (my card booter)
6) If the number 5 is impossible, can I split the animation in, for example, the first frame, and then inject that just as always? (assuming one frame is equal sized as the non-dsi enhanced)
Sorry for the inconveniences