I have done all of this. The problem now is that that data is being stored elsewhere and I am not sure where. Identical SDCARDs both boot into SXOS properly, but the second card has the last games rearranged in a different order and the save games are different. Launching the same game on one starts at a different place I left off then starting the same game on an identical SDCARD. Not even using Atmosphere at all. I put that on hold until I can figure out what exactly is going on. I even tried backing up the saves using both Tinfoil and SX Installer on the good SDcard, mirrored it to the secondary SDCARD, and restored the saves for the game and the starting point is not where I left off. To be clear, saves were restore with Tinfoil and game started in wrong place. Saves were restored with SXInstaller and the progress was started in the wrong place. Somewhere progress data is *not* being written to the SDCARD when booting all of the above in EMUNAND.You can use a separate emunand for sx os atmosphere. That's how I was setup at one point. You need to create the sx os emunand first then you can resize the fat32 partition leaving the correct sized partition unformatted as the last partition. You can then use emutool to restore either a nand backup or a backup of the sx os emunand to the unformatted partition.
That’s my setup also, working fine, and I keep Sxos to be able to play Xcis from usb docked or on the road with my ssd, as there’s no sd card large enough for all my games. And Atmosphere, because some homebrews (or overlays) can’t work properly under Sxos.TL;DR: Using multiple emummcs is problematic. A nuisance at best. For now, my emummc is on 11.0.0 and I use it with both sx and Atmosphere.
Different features on both, none having a damn thing to do with 11.0.1. That firmware adds nothing to the equation (at this point). I was addressing the OP's concerns. Your post, isn't helpful in the slightest.What is the use of using the same emunand for both?
SX can atm only do 11.0.0, atmosphere can do 11.0.1.
So when you update emunand to 11.0.1 sx will become useless.
If you stay on 11.0.0 what is the point of using atmosphere when you already use sx?
Pick one cfw or use two SD cards
you didn’t read my post, or didn’t understood it.What is the use of using the same emunand for both?
SX can atm only do 11.0.0, atmosphere can do 11.0.1.
So when you update emunand to 11.0.1 sx will become useless.
If you stay on 11.0.0 what is the point of using atmosphere when you already use sx?
Pick one cfw or use two SD cards
That’s my setup also, working fine, and I keep Sxos to be able to play Xcis from usb docked or on the road with my ssd, as there’s no sd card large enough for all my games. And Atmosphere, because some homebrews (or overlays) can’t work properly under Sxos.
Well sorry for living.... Your reaction isn't polite in the slightest.Different features on both, none having a damn thing to do with 11.0.1. That firmware adds nothing to the equation (at this point). I was addressing the OP's concerns. Your post, isn't helpful in the slightest.
It is perfectly clear and @urherenow gave you a very accurate answer.Just so we are clear, I am NOT trying to have 2 different emunands. I am trying to have SXOS and Atmosphere share the same one. Somewhere from the OP this got twisted into something else.
The main reason I wanted to be able to share one emunand between atmosphere and SXOS is the future of SXOS is very uncertain. This is the longest time they have delayed a working update for a firmware (11.01).
Not quite sure why you feel the need for 2 emummcs, except for wanting Atmosphere always on the latest HOS FW, while keeping one for SX that you will delay updating. Currently a waste of space, since no game currently REQUIRES 11.0.1 or above to run. With some caveats:
1) With this setup, you will ALWAYS have disparities with save games. Unless you backup with checkpoint, and then restore with checkpoint when loading a different emmc/emummc. Saves are stored ON THE EMMC, not on the SD, so sharing the Nintendo/Emutendo folder won't help with that.
2) When installing a title, A ticket is also installed ON THE EMMC. Just because you share the Nintendo/Emutendo folder, does not mean that installing while using 1 emummc will allow it to show up in another, even though it would otherwise be valid and is using the same encryption keys. The tickets aren't there.
3) manually copying the ticket.db/title.db between systems to keep them synchronized (you can mount any emmc as read/write using nyx, and mount them on PC using HacDiskMount)... if a game was run on 11.0.1, it might refuse to run under 11.0.0. You will have to boot that 11.0.0 partition (with Atmosphere, not SX) and hold Vol+ and Vol- after the sept logo comes up and changes to the Atmosphere logo, until maintenance mode comes up. Don't do anything in maintenance mode, just power down, then when you boot 11.0.0 again with sx, the games won't bug you for updates.
4) HOS home screen arrangement (last played, etc) is also a save file. Kind of. It works like desktop.ini on a Windows PC. You guessed it! On the emmc/emummc!
TL;DR: Using multiple emummcs is problematic. A nuisance at best. For now, my emummc is on 11.0.0 and I use it with both sx and Atmosphere.
[emummc]
enabled=1
sector=0x2
path=emuMMC/RAW1
id=0x0000
nintendo_path=Emutendo
[emummc]
emummc_enabled = 1
emummc_sector = 0x2
emummc_nintendo_path = Emutendo
I've seen you post this same thing several times. Stop. IT'S WRONG. There is no "emummc_" in all of those .ini entries. I have already posted the proper contents for a partition-based, directly above you.Code:[emummc] emummc_enabled = 1 emummc_sector = 0x2 emummc_nintendo_path = Emutendo
I've seen you post this same thing several times. Stop. IT'S WRONG. There is no "emummc_" in all of those .ini entries. I have already posted the proper contents for a partition-based, directly above you.
Try reading the whole thread. I know it works. Your INI is wrong. Broken records don't need respect. They need to be thrown away.It absolutely works. Did it on my setup. You have to make the ini. Just copy that in to it. And put it where i said. It's not wrong. You are misinformed. The SXOS EmuNAND is compatible. Its just on a different offset. Try it. Stop thinking know everything. It works with hidden partition based EmuNAND.
Talk to me with respect.