You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is to achieve booting separate atmosphere instances (that can contain different LayeredFS / kip / exefs / nxthemes patches / saves redirection / or even an entirely different version of Atmosphere ) so as not to interfere with other eMMC instances, by utilizing m4xw's SDMMC driver (somehow) (also since support for /Nintendo folder redirection to a arbitrary path is already in place for a while now).
For configuration, this would preferably be done in hekate_ipl.ini per boot entry (concept as shown):
The preferred outcome would be when Horizon is reading from and writing to /atmosphere/, its actually accessing "/emuMMC/RAW1/atmosphere/" (as an example).
ams.mitm was rewritten as part of Stratosphere's refactor.
Saves redirected to the SD card are now separated for sysmmc vs emummc. ____(Though not sure how it works)
In addition, some niceties (e.g. having a separate Atmosphere folder per emummc instance) still need some thought put in before they can be implemented in a way that makes everyone happy.
The text was updated successfully, but these errors were encountered:
Hekate has nothing to do with that. The support must come from the cfw side.
Something that you can do is to replace all these folder strings and recompile atmosphere. This way you can have atmo1, atmo2, etc folders. Like how some people opted to do, in order to have different atmosphere folders for sys and emu.
Also the fusee-secondary.bin file for fss0, doesn't matter where it is. hekate can launch it from anywhere. The issue as I said is that the kips from inside fusee-secondary.bin have the folders hardcoded.
Related reference: Atmosphere-NX/Atmosphere#704
The idea is to achieve booting separate atmosphere instances (that can contain different LayeredFS / kip / exefs / nxthemes patches / saves redirection / or even an entirely different version of Atmosphere ) so as not to interfere with other eMMC instances, by utilizing m4xw's SDMMC driver (somehow) (also since support for /Nintendo folder redirection to a arbitrary path is already in place for a while now).
For configuration, this would preferably be done in hekate_ipl.ini per boot entry (concept as shown):
The preferred outcome would be when Horizon is reading from and writing to /atmosphere/, its actually accessing "/emuMMC/RAW1/atmosphere/" (as an example).
Other related details:
The text was updated successfully, but these errors were encountered: