Hmm so it does indeed. Though the "Atmosphere File" option results in it generating the separate Boot0/Boot1 files along side the main partition. So it's not really a single bin file. Unless I use the SX OS option. But I don't use SX OS.... So I'd prefer not to use that option.
As for multiple partition support...seems it only accesses the currently selected emummc setup for Atmosphere so I'd have to boot up my Switch and select the other one in Hekate before I can dump that one too...That's kind of annoying. Hekate doesn't really store the partition locations on it's own. Seems to just auto detect them so that not be as simple for you to implement yourself. Well hopefully handling of more then one partition becomes easier in the future. I'll keep an eye on this one.
Oh and I did do a backup to Atmosphere File option. No error to report. Seems to run fine under my Windows 7 64bit OS.
When you create a partition Emu, Hekate creates a folder (RAW1, RAW2, etc.) with a raw_based file inside that contains the starting address of that specific partition in binary data, so Hekate stores the partition location. But Warning if you create an Emu with Hekate, the starting sector of the Emu is not the starting sector of the partition.
Hekate put some free space before the real Emu data, this is why I read it from emummc.ini file and not from disk info.
The sector field in EmuTool version 0.2.6 is freely editable, so if you know the real starting sector you can edit the field manually.
Keep in mind that if you are able to create multipartitions with different Emus, you probably don't need this Tool
The binary file are splitted for two reason: portability across different file system (Fat32 or exFat), and to be ready to be used for a File based eMMC.
They are simple raw data, so you can have a single file using a command like
copy /b BOOT0 + BOOT1 + 00 + 01 ..... + 07 singleFile.bin or using joiner_scripts from Hekate's github.
I can add an option to have a single file, but is it really needed?
Thank you for let me know you can run the tool, I'm not able to figure out where is the bug.
Ciao!