Tutorial How to have SEPARATE ATMOSPHERE AND SXOS EMUNAND HIDDEN PARTITIONS ON THE SAME SD TUTORIAL!

jimmmeh

Member
Newcomer
Joined
Sep 12, 2009
Messages
7
Trophies
0
XP
165
Country
1. I have Tesla/fastCFWswitch working between SXOS and Atmosphere (and vice versa). You have to approach it from the perspective of a completely new install of the stack on SXOS with just a shared config file.

2. For the config I used hekate.bin to boot everything (well, update.bin so I didn’t have to change the name between releases) and made use of the ID system so basically everything is booted by Hekate but you pass what you want Hekate to boot. I‘m adding a snippet of my config/fastCFWswitch/config.ini and my bootloade/hekate_ipl.ini so you can get the gist…there’s stuff that’s specifically for my system and you need to massage things for your setup so I don’t recommend you copy them directly.

[config]
autoboot=1
autoboot_list=0
bootwait=1
backlight=55
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
emummcforce=1
kip1=atmosphere/kip_patches/*
logopath=/graphics/splash/atmosphere.bmp
icon=/graphics/icons/current/atmosphere.bmp
id=atmo

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=/graphics/icons/current/stock.bmp
id=sysn

[SX OS]
payload=bootloader/payloads/sxos.bin
logopath=/graphics/splash/sxos.bmp
icon=/graphics/icons/current/icon_sxos.bmp
id=sxos

[CFWS]
type=section
name=CFW

[ATMOSPHERE]
name=atmosphere
path=/bootloader/update.bin
bootId=atmo

[SXOS]
name=sxos
path=/bootloader/update.bin
bootId=sxos

[LAKKA]
name=lakka
path=/bootloader/update.bin
bootId=lakk

[ANDROID]
name=android
path=/bootloader/update.bin
bootId=andr

[L4T]
name=ubuntu
path=/bootloader/update.bin
bootId=ubun

[SYSNAND]
name=sysnand
path=/bootloader/update.bin
bootId=sysn

[TOOLS]
type=section
name=TOOLS

[HEKATE]
name=hekate
path=/bootloader/update.bin

[LOCKPICKRCM]
name=lockpick
path=/bootloader/payloads/Lockpick_RCM.bin

[CPR]
name=CPR
path=/bootloader/payloads/CommonProblemResolver.bin

[UMS]
type=section
name=UMS

[SD_CARD]
name=SD
path=/bootloader/update.bin
ums = sd

[EMMC_BOOT_0]
name=EMMC BOOT 0
path=/bootloader/update.bin
ums = emmc_boot0

[EMMC_BOOT_1]
name=EMMC BOOT 1
path=/bootloader/update.bin
ums = emmc_boot1

[EMMC_GPT]
name=EMMC GPT
path=/bootloader/update.bin
ums = emmc_gpt

[EMU_BOOT_0]
name=EMU BOOT 0
path=/bootloader/update.bin
ums = emu_boot0

[EMU_BOOT_1]
name=EMU BOOT 1
path=/bootloader/update.bin
ums = emu_boot1

[EMU_GPT]
name=EMU GPT
path=/bootloader/update.bin
ums = emu_gpt

Ahh thanks so much for this - I think I know why it wasn't working on SX OS - or at least it seemed to be related to the firmware version - so initially my sys, sx os and atmosphere emunands were all running 4.0.1 - I upgraded atmosphere to 13.2 possibly before trying the overlay - it worked but SX OS one was still at 4.0.1 - I updated the SX OS emunand to 11 and now it's working - I think I was getting confused with what the payloads were for the rest - it should just be the thing that I am sending to my switch via TegraRcmSmash I guess which as you've pointed out I can just configure in hekate and link that way!

Thanks again!
 
  • Like
Reactions: binkinator

binkinator

Garfield’s Fitness Coach
Member
GBAtemp Patron
Joined
Mar 29, 2021
Messages
1,865
Trophies
1
XP
1,283
Country
United States
I see it and it's set to on... do I turn it off then?
Let’s not flip settings without understanding the full issue. I’m making an assumption that you recently upgraded Atmosphere as part of this process. By default SciresM set it up so you don’t burn your game card fuses if you were below 9.0.0. The down side to that is your game card will be disabled and you’ll get this message if you try to play a game card. Its quite possible I’ve assumed incorrectly so if this is not your scenario we have something else on our hands.
 

Sovikos

Well-Known Member
Member
Joined
Mar 17, 2018
Messages
127
Trophies
0
XP
369
Country
Canada
Let’s not flip settings without understanding the full issue. I’m making an assumption that you recently upgraded Atmosphere as part of this process. By default SciresM set it up so you don’t burn your game card fuses if you were below 9.0.0. The down side to that is your game card will be disabled and you’ll get this message if you try to play a game card. Its quite possible I’ve assumed incorrectly so if this is not your scenario we have something else on our hands.
Yeah I'm trying to migrate from SXOS SysNAND to a dual boot with Hidden SXOS EmuNAND and Hidden ATM EmuNAND.
 

Sovikos

Well-Known Member
Member
Joined
Mar 17, 2018
Messages
127
Trophies
0
XP
369
Country
Canada
I'm on 11.0.0 and both hidden emunands are supposedly copies of those, except under Launch in Hekate, none of them Launch SXOS...
nyx20211230_143450.png
All seem to be ATM except Stock.

Wasn't trying to play any game on cart, I just had a cart in there so that message would pop up anytime I went into ATM.
 

binkinator

Garfield’s Fitness Coach
Member
GBAtemp Patron
Joined
Mar 29, 2021
Messages
1,865
Trophies
1
XP
1,283
Country
United States
I'm on 11.0.0 and both hidden emunands are supposedly copies of those, except under Launch in Hekate, none of them Launch SXOS...View attachment 291980 All seem to be ATM except Stock.

Wasn't trying to play any game on cart, I just had a cart in there so that message would pop up anytime I went into ATM.

Please post your hekate_Ipl.ini.

Should probably pull the cart out to see if ATM will run clean without it.
 

Sovikos

Well-Known Member
Member
Joined
Mar 17, 2018
Messages
127
Trophies
0
XP
369
Country
Canada
Please post your hekate_Ipl.ini.

Should probably pull the cart out to see if ATM will run clean without it.
Here is my hekate_ipl.ini that is in /bootloader/

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=82
autohosoff=1
autonogc=0
updater2p=0
bootprotect=0

[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[CFW (emuMMC)]
emummcforce=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[Stock]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_switch.bmp
stock=1

[Fusee]
icon=bootloader/res/icon_payload.bmp
payload=bootloader/payloads/fusee.bin
Here is the root of my SD card. This tutorial in the OP just says copy the files I backed up back onto the hard drive, but I have a feeling it's missing a step and I need to put them under emuMMC or Emutendo as well? I am not sure??

Right now I took the card out and everything is fine. That message doesn't come up anymore

1640994539245.png
 

binkinator

Garfield’s Fitness Coach
Member
GBAtemp Patron
Joined
Mar 29, 2021
Messages
1,865
Trophies
1
XP
1,283
Country
United States
Here is my hekate_ipl.ini that is in /bootloader/

Heres mine:

I auto boot my (emmunand based) ATM (autoboot=1) after 1 second (bootwait=1) with auto No Game Card turned on (autonogc=1).

You’re missing an SXOS section pointing to the payload you would normally use to start SXOS (mine is called sxos.bin). This is the payload that will kick off your boot.dat and thus SXOS.

Dont copy paste mine as my splashscreens (logopath) and icons are specific to my setup. Just get the gist of whats going on and use what makes sense for your setup.

[config]
autoboot=1
autoboot_list=0
bootwait=1
backlight=55
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
emummcforce=1
kip1=atmosphere/kip_patches/*
logopath=/graphics/splash/atmosphere.bmp
icon=/graphics/icons/current/atmosphere.bmp
id=atmo

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=/graphics/icons/current/stock.bmp
id=sysn

[SX OS]
payload=bootloader/payloads/sxos.bin
logopath=/graphics/splash/sxos.bmp
icon=/graphics/icons/current/icon_sxos.bmp
id=sxos

Here is the root of my SD card. This tutorial in the OP just says copy the files I backed up back onto the hard drive, but I have a feeling it's missing a step and I need to put them under emuMMC or Emutendo as well? I am not sure??

Right now I took the card out and everything is fine. That message doesn't come up anymore

View attachment 291989

Off the cuff this looks like a reasonable file structure for Atmosphere. The emummc.ini will contain which directory it’s actually using and have a pointer to the disk offset where your hidden partition starts. If you’re missing any of the directories I believe it will create them for you as needed. One of them probably isn’t needed but it’s not gonna hurt anything either.

Let’s get you dual booting first and you can carefully clean things up afterwards.
 

Sovikos

Well-Known Member
Member
Joined
Mar 17, 2018
Messages
127
Trophies
0
XP
369
Country
Canada
Heres mine:

I auto boot my (emmunand based) ATM (autoboot=1) after 1 second (bootwait=1) with auto No Game Card turned on (autonogc=1).

You’re missing an SXOS section pointing to the payload you would normally use to start SXOS (mine is called sxos.bin). This is the payload that will kick off your boot.dat and thus SXOS.

Dont copy paste mine as my splashscreens (logopath) and icons are specific to my setup. Just get the gist of whats going on and use what makes sense for your setup.

[config]
autoboot=1
autoboot_list=0
bootwait=1
backlight=55
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
emummcforce=1
kip1=atmosphere/kip_patches/*
logopath=/graphics/splash/atmosphere.bmp
icon=/graphics/icons/current/atmosphere.bmp
id=atmo

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=/graphics/icons/current/stock.bmp
id=sysn

[SX OS]
payload=bootloader/payloads/sxos.bin
logopath=/graphics/splash/sxos.bmp
icon=/graphics/icons/current/icon_sxos.bmp
id=sxos



Off the cuff this looks like a reasonable file structure for Atmosphere. The emummc.ini will contain which directory it’s actually using and have a pointer to the disk offset where your hidden partition starts. If you’re missing any of the directories I believe it will create them for you as needed. One of them probably isn’t needed but it’s not gonna hurt anything either.

Let’s get you dual booting first and you can carefully clean things up afterwards.
OK I see... Had no clue about the .ini file and the settings. I will look into that when I get home here later today. Brought my Switch with me, but forgot the MicroSD reader for my laptop. As for the file structure, I should actually learn what they all are. Before I moved my files over there was EmuMMC and Emutendo... Can you tell me what these folders correspond to or are used for?

Right now I would be happy with just wiping out all the games I've installed and starting fresh... But I am not sure how I do that just yet, as they all seem to show 0 bytes in SXOS and ATM, but I might need to do some more testing here. I have all the saves backed up I believe anyway. Only thing I care about right now is getting Animal Crossing going for my kids lol. I've tried reinstalling the game and the updates (to which I believe was the last version I had), but the game doesn't seem to want to start yet on either CFW. I am guessing I don't have the update installed that I was on before I did all this. But that's something to worry about later, as I am hoping once I update to FW 13.2 in ATM that the latest Animal Crossing update will work.

I will get back to you though once I look at the ini files later. Thank for your help!
 

binkinator

Garfield’s Fitness Coach
Member
GBAtemp Patron
Joined
Mar 29, 2021
Messages
1,865
Trophies
1
XP
1,283
Country
United States
OK I see... Had no clue about the .ini file and the settings. I will look into that when I get home here later today. Brought my Switch with me, but forgot the MicroSD reader for my laptop. As for the file structure, I should actually learn what they all are. Before I moved my files over there was EmuMMC and Emutendo... Can you tell me what these folders correspond to or are used for?

Right now I would be happy with just wiping out all the games I've installed and starting fresh... But I am not sure how I do that just yet, as they all seem to show 0 bytes in SXOS and ATM, but I might need to do some more testing here. I have all the saves backed up I believe anyway. Only thing I care about right now is getting Animal Crossing going for my kids lol. I've tried reinstalling the game and the updates (to which I believe was the last version I had), but the game doesn't seem to want to start yet on either CFW. I am guessing I don't have the update installed that I was on before I did all this. But that's something to worry about later, as I am hoping once I update to FW 13.2 in ATM that the latest Animal Crossing update will work.

I will get back to you though once I look at the ini files later. Thank for your help!

Nintendo folder is where OFW stores games/screenshots/etc. Emmutendo is where SXOS stores games/screenshots/etc.

Emmumc/XXXX/ is an instance of Atmosphere where XXXX is a unique identifier. There is a corresponding Nintendo folder under that path that stores games/screenshots/etc.

You can delete the other XXXX path but like I said it won’t hurt anything. We should get everything working first.
(If/when you want to get rid of it, just move it somewhere else and make sure everything still works and only then delete it.)

The emmumc.ini file under the emummc directory will tell you which XXXX path is the active one and the sector (in hex) on the SDcard where the raw partition starts.

Here is what mine looks like. Yours will be different depending upon where your data actually sits so don’t copy mine:

[emummc]
enabled=1
sector=0x2a358000
path=emuMMC/RAW1
id=0x31574152
nintendo_path=emuMMC/RAW1/Nintendo
 

DoobyDude

Active Member
Newcomer
Joined
Feb 16, 2019
Messages
38
Trophies
0
XP
90
Country
United Kingdom
Just a quick question about keeping SXOS to be able to play games from external drives.

This will only work with games that need firmware v11.0 or lower?
Anything requiring a FW above that needs to be run using Atmosphere from the internal or sd card?
 

binkinator

Garfield’s Fitness Coach
Member
GBAtemp Patron
Joined
Mar 29, 2021
Messages
1,865
Trophies
1
XP
1,283
Country
United States
Just a quick question about keeping SXOS to be able to play games from external drives.

This will only work with games that need firmware v11.0 or lower?
Anything requiring a FW above that needs to be run using Atmosphere from the internal or sd card?
Correct. SXOS will not work above 11.0.0. Some games can be modified if they don’t require any of the new libraries but more recent games are being released with new features that cannot be downgraded.

You must use Atmosphere to install NSPs for games requiring 11.0.1 and higher.
 
  • Like
Reactions: DoobyDude

Sovikos

Well-Known Member
Member
Joined
Mar 17, 2018
Messages
127
Trophies
0
XP
369
Country
Canada
Nintendo folder is where OFW stores games/screenshots/etc. Emmutendo is where SXOS stores games/screenshots/etc.

Emmumc/XXXX/ is an instance of Atmosphere where XXXX is a unique identifier. There is a corresponding Nintendo folder under that path that stores games/screenshots/etc.

You can delete the other XXXX path but like I said it won’t hurt anything. We should get everything working first.
(If/when you want to get rid of it, just move it somewhere else and make sure everything still works and only then delete it.)

The emmumc.ini file under the emummc directory will tell you which XXXX path is the active one and the sector (in hex) on the SDcard where the raw partition starts.

Here is what mine looks like. Yours will be different depending upon where your data actually sits so don’t copy mine:

[emummc]
enabled=1
sector=0x2a358000
path=emuMMC/RAW1
id=0x31574152
nintendo_path=emuMMC/RAW1/Nintendo
Ok sorry I haven't had anytime to get on here and finish this, so I apologize, but I am very appreciative of your help so far. So anyways here is my emummc.ini file, looks similar to yours and should be fine right?
[emummc]
enabled=1
sector=0x2a3438e9
path=emuMMC/RAW1
id=0x31574152
nintendo_path=emuMMC/RAW1/Nintendo

As for my hekate_ipl.ini, I noticed 3 of them (in bold) look to be pretty much almost the exact same thing right? I've added SXOS to the bottom, not sure if I keep the id=sxos like yours has? Also noticed autohosoff=1 and updater2p=0 are different from yours. I looked up what they are, but honestly have no idea what they mean or are lol. Should I just leave them as they are? What should I remove or add to mine?

[config]
autoboot=0
autoboot_list=0
bootwait=1
backlight=82
autohosoff=1
autonogc=1
updater2p=0
bootprotect=0

[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[CFW (emuMMC)]
emummcforce=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[Stock]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_switch.bmp
stock=1


[Fusee]
icon=bootloader/res/icon_payload.bmp
payload=bootloader/payloads/fusee.bin

[SX OS]
payload=bootloader/payloads/payload.bin
icon=/graphics/icons/current/icon_payload.bmp
id=sxos


Here is my SD Card in MiniTool too just incase. It shows a weird drive name for the middle part there, and that came after I had reformatted it.
 

binkinator

Garfield’s Fitness Coach
Member
GBAtemp Patron
Joined
Mar 29, 2021
Messages
1,865
Trophies
1
XP
1,283
Country
United States
Ok sorry I haven't had anytime to get on here and finish this, so I apologize, but I am very appreciative of your help so far. So anyways here is my emummc.ini file, looks similar to yours and should be fine right?
[emummc]
enabled=1
sector=0x2a3438e9
path=emuMMC/RAW1
id=0x31574152
nintendo_path=emuMMC/RAW1/Nintendo

emmumc.ini looks good.

As for my hekate_ipl.ini, I noticed 3 of them (in bold) look to be pretty much almost the exact same thing right? I've added SXOS to the bottom, not sure if I keep the id=sxos like yours has? Also noticed autohosoff=1 and updater2p=0 are different from yours. I looked up what they are, but honestly have no idea what they mean or are lol. Should I just leave them as they are? What should I remove or add to mine?

[config]
autoboot=0
autoboot_list=0
bootwait=1
backlight=82
autohosoff=1
autonogc=1
updater2p=0
bootprotect=0

[CFW (sysMMC)]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[CFW (emuMMC)]
emummcforce=1
fss0=atmosphere/package3
icon=bootloader/res/icon_payload.bmp

[Stock]
emummc_force_disable=1
fss0=atmosphere/package3
icon=bootloader/res/icon_switch.bmp
stock=1


[Fusee]
icon=bootloader/res/icon_payload.bmp
payload=bootloader/payloads/fusee.bin

[SX OS]
payload=bootloader/payloads/payload.bin
icon=/graphics/icons/current/icon_payload.bmp
id=sxos

The highlighted ones are close looking but are very different in action.

First one runs CFW on the stock nand
Second one runs CFW on emunand
Third one runs without CFW on stock nand

You want to boot the second one.

You can make it always boot the second entry automatically by changing autoboot=0 to autoboot=2.
If you ever want to override the autoboot just hit (Vol -) when the Hekate splash screen displays.

autohosoff=1is fine. It is an edge case power-off thing. It won’t impact you so you can leave it default. Read up on this and AutoRCM at a later date.

updater2p=1 means my Hekate checks and updates my reboot2payload to be Hekate if it ever changes to anything else. I do everything through Hekate so I was being pedantic. You can leave it default of 0 for now. It won’t impact anything either.



Here is my SD Card in MiniTool too just incase. It shows a weird drive name for the middle part there, and that came after I had reformatted it.

This name is only for Windows. You might want to change ito something reasonable but I don’t think you have to for any Switch reasons.
 

Sovikos

Well-Known Member
Member
Joined
Mar 17, 2018
Messages
127
Trophies
0
XP
369
Country
Canada
The highlighted ones are close looking but are very different in action.

First one runs CFW on the stock nand
Second one runs CFW on emunand
Third one runs without CFW on stock nand

You want to boot the second one.

You can make it always boot the second entry automatically by changing autoboot=0 to autoboot=2.
If you ever want to override the autoboot just hit (Vol -) when the Hekate splash screen displays.

autohosoff=1is fine. It is an edge case power-off thing. It won’t impact you so you can leave it default. Read up on this and AutoRCM at a later date.

updater2p=1 means my Hekate checks and updates my reboot2payload to be Hekate if it ever changes to anything else. I do everything through Hekate so I was being pedantic. You can leave it default of 0 for now. It won’t impact anything either.
OK. Now those 3 all will run Atmosphere then as they point to package3? The Stock FW, is that my sysNAND then where I originally had SXOS?

Also the Fusee one, I can just delete that one right?

The SXOS one I added above, is that running off SysNAND or EmuNAND then?

My next step I guess is testing them out and then possibly updating to Firmware 13.2.0 on the ATM emuMMC correct?

Oh and what program should I use to install games and such now?
 

Sovikos

Well-Known Member
Member
Joined
Mar 17, 2018
Messages
127
Trophies
0
XP
369
Country
Canada

binkinator

Garfield’s Fitness Coach
Member
GBAtemp Patron
Joined
Mar 29, 2021
Messages
1,865
Trophies
1
XP
1,283
Country
United States
OK. Now those 3 all will run Atmosphere then as they point to package3? The Stock FW, is that my sysNAND then where I originally had SXOS?

1 and 2 are atmosphere.
3 does not do atmosphere…it’s OFW on Sysnand (stock)

For SXOS you need a copy of the sx bootloader. Rename it to match (or change the following line to point to wherever you put it):

payload=bootloader/payloads/payload.bin

Then you use Hekate to boot it and it will in turn kick off your boot.dat and reference your license.dat files…just like normal SXOS except you start it fro, the Hekate menu. One stop shopping


Also the Fusee one, I can just delete that one right?

There are so,e edge cases where it can be useful but to keep things simple you don’t need that entry.

The SXOS one I added above, is that running off SysNAND or EmuNAND then?

For SXOS you need to be sure to enable hidden partition emmunand in the boot tool. You might need to hit (Vol -) during the SXOS splash screen to get to the tools.

My next step I guess is testing them out and then possibly updating to Firmware 13.2.0 on the ATM emuMMC correct?

Make sure you set up exosphere.ini before hand.

See step #3 in this doc:
https://rentry.org/EristaSysNAND

Once set up make sure you select CFW on emunand (entry #2) and use Daybreak to upgrade your firmware.

Oh and what program should I use to install games and such now?

Any of the major installers will do. I have Tinfoil and Awoo but it‘s religion really.
 

Sovikos

Well-Known Member
Member
Joined
Mar 17, 2018
Messages
127
Trophies
0
XP
369
Country
Canada
For SXOS you need to be sure to enable hidden partition emmunand in the boot tool. You might need to hit (Vol -) during the SXOS splash screen to get to the tools.



Make sure you set up exosphere.ini before hand.

See step #3 in this doc:
https://rentry.org/EristaSysNAND

Once set up make sure you select CFW on emunand (entry #2) and use Daybreak to upgrade your firmware.



Any of the major installers will do. I have Tinfoil and Awoo but it‘s religion really.
I will have to take a look at Tinfoil again or Awoo, but I found when using Goldleaf on that option #2, that I run into this problem though:

https://gbatemp.net/threads/invalid...-a-too-low-firmware-4518.582479/#post-9542714

So I wonder if maybe I should use the Fusee one to launch?

Also the system seems to crash in ATM EmuMMC on games I installed while under the Fusee one. I am not sure if I ever got any games to install under ATM EmuMMC yet.

Another question, with all the old crap I had installed from before, how do I just delete all that stuff? I really only care about keeping my users and the Animal Crossing saves I think. I found when I went into Data Management, almost all the games showed 0 Bytes.
 

binkinator

Garfield’s Fitness Coach
Member
GBAtemp Patron
Joined
Mar 29, 2021
Messages
1,865
Trophies
1
XP
1,283
Country
United States
I will have to take a look at Tinfoil again or Awoo, but I found when using Goldleaf on that option #2, that I run into this problem though:

https://gbatemp.net/threads/invalid...-a-too-low-firmware-4518.582479/#post-9542714

if it’s exactly like that thread…you prolly need to upgrade FW daybreak and that “dark sternie firmware”.

So I wonder if maybe I should use the Fusee one to launch?

Also the system seems to crash in ATM EmuMMC on games I installed while under the Fusee one. I am not sure if I ever got any games to install under ATM EmuMMC yet.

Another question, with all the old crap I had installed from before, how do I just delete all that stuff? I really only care about keeping my users and the Animal Crossing saves I think. I found when I went into Data Management, almost all the games showed 0 Bytes.

‘You can remove them using the built in DataManage….the fact that they are showing 0 bytes means you just have the index and it cant find the actual data. Deleting them and reinstall is a quick solution.
 
Last edited by binkinator,
General chit-chat
Help Users
    Dark_Phoras @ Dark_Phoras: I think Xbox plays a bit too safe with their main IPs