Team [WAIN] is back with a quick update to their SX Autoloader release!

We have not heard from Team [WAIN] for a while, and today they dropped a bomb-shell of an add-on to SX OS, a simple little file that adds a much needed feature, 'auto-loading' of all your backup cartridges, no more hunting thru lots of icons to find a game and mounting it just click on the Game Icon you want to play right now and magically the cartridge will be inserted for you, its like having a multi-CD-changer attached to your Switch console!

Thanks to their friends at Team [WAIN] they have released an small 'add-on' to their SX OS v2.9.2 which allows you to 'auto-load', what that means now you just find the game you have previously played on your Horizon Home Screen, click on it, and even if it is a dumped cartridge in XCI format, as long as you still have the files on your Micro SD-Card and/or USB HDD, it will now auto-mount the cartridge backup for you and launch it, no more getting upset seeing the 'insert the game card' message, then having to go to Album, launch via their SX OS menu, scroll-over and find the game, and mount it and go back.

As long as you have at least mounted your XCI image once via their SX OS menu, now you can just simply click on a XCI Game Icon and it will Auto-Mount and Launch for you directly from the Horizon Home Screen. Is that not amazing!

NEW RELEASE: (Nov. 2th, 2019)

Changelog v1.1

• Added USB HDD Support
• Improved XCI detection
• Database caching for speed

NOTE: If you have large XCI collection on your USB HDD, first time usage may take a couple of minutes for the database to be built.
IMPORTANT: If you get an Error Code on boot-up, then it means your SD Card has corruption on it, please re-format it and start fresh.

As usual, you can find their latest version of SX Autoloader in the TX Community Resources section, just unpack the new version overwriting the previous files.

To see it in action check out this video below:

—< Team-Xecuter - Rocking the Switch in 2019 and beyond! >—​

Source: MaxConsole

 

[CaptainCPS-X]

...
exfat = corruption
Fat32 = no corruption
...

Since this topic seems to be important for many, please allow me to clear something regarding that small quoted text:

Data corruption can happen on any filesystem, as data flows from/to RAM and storage, if there is a power loss, or some other external issue (hardware / software / OS related) make it impossible for this active data to reach completely, then we get data loss / corruption. But there is no 100% corruption-free device or storage, the filesystems have evolved to provide better protection for this, but won't completely remove the possibility of corruption.

Now a note to everyone: You are free to use whatever filesystem you like, for whatever reason, the fact that you use it won't make it better or worse.

PS: It would be a good time now to keep this thread on track, talking about "Autoloader v1.10" ^___^u

SeeYa!

 

[EmulateLife]

Since this topic seems to be important for many, please allow me to clear something regarding that small quoted text:

Data corruption can happen on any filesystem, as data flows from/to RAM and storage, if there is a power loss, or some other external issue (hardware / software / OS related) make it impossible for this active data to reach completely, then we get data loss / corruption. But there is no 100% corruption-free device or storage, the filesystems have evolved to provide better protection for this, but won't completely remove the possibility of corruption.

Now a note to everyone: You are free to use whatever filesystem you like, for whatever reason, the fact that you use it won't make it better or worse.

PS: It would be a good time now to keep this thread on track, talking about "Autoloader v1.10" ^___^u

SeeYa!

You can't have it both ways you want to "keep this thread on track" but then you talk nonsense. Search gbatemp you won't find one thread where someone says "Fat32 corrupted my sd card" you will find literally hundreds from exfat. That's not a coincidence regardless of what you think. Devs like m4xw say use Fat32, Retroarch devs says use Fat32. These are devs that have spent hundreds if not thousands of hours on the inner workings of the Nintendo Switch, they know more than you.

There's a bug when they made the system in exfat file system, it's been said for over a year now.

 

[Deleted User]

You can't have it both ways you want to "keep this thread on track" but then you talk nonsense. Search gbatemp you won't find one thread where someone says "Fat32 corrupted my sd card" you will find literally hundreds from exfat. That's not a coincidence regardless of what you think. Devs like m4xw say use Fat32, Retroarch devs says use Fat32, they know more than you.

There's a bug when they made the system in exfat file system, it's been said for over a year now.

That's old news and not the case anymore

Exfat here with emunands / emuMMCs - 600+ Mods later not a single corruption

Exfat it prone to corruption on PC side by not ejecting media etc (Can be fixed in seconds in most cases)

 

[EmulateLife]

That's old news and not the case anymore

Exfat here with emunands / emuMMCs - 600+ Mods later not a single corruption

Exfat it prone to corruption on PC side by not ejecting media etc (Can be fixed in seconds in most cases)

Nope you're wrong, I had corruption on the Switch itself from an error. I always eject properly.

I don't care how many mods you've done I'll take the word of m4xw and countless threads of people saying "I'm on exfat and my sd card is corrupted" as well as my own personal experience.

There is no "old news" when it comes to Switch's file system nothing at all has changed Nintendo hasn't improved the file system at all so you made that up. The only way they can improve it is with a new Switch model. Nintendo has zero reasons to improve it though because the corruption happens on homebrew on hacked consoles not on real Switch games.

Exfat users always have an excuse why they have corruption funny how Fat32 needs no excuses. It's just the logical file system to use to avoid all corruption, that's a fact.

 

[CaptainCPS-X]

You can't have it both ways you want to "keep this thread on track" but then you talk nonsense. Search gbatemp you won't find one thread where someone says "Fat32 corrupted my sd card" you will find literally hundreds from exfat. That's not a coincidence regardless of what you think. Devs like m4xw say use Fat32, Retroarch devs says use Fat32, they know more than you.

There's a bug when they made the system in exfat file system, it's been said for over a year now.

Have I expressed disrespect to you in some way for you to say I talk "nonsense"?

What I wrote, is not a thought, I am talking about a technological fact of universal filesystems, not about the "Nintendo Switch" only. And you just met me in a couple of posts and already know if somebody else have knowledge than me? What I wrote is the reality of data, there is no perfect filesystem / storage, it hasn't been created yet.

I thought I would be able to collaborate in this scene, maybe share some tools, like I did for the PS3 scene, but if people will be like this, I better spend my time doing something else.

Take care!

SeeYa!

 

[EmulateLife]

Have I expressed disrespect to you in some way for you to say I talk "nonsense"?

What I wrote, is not a thought, I am talking about a technological fact of universal filesystems, not about the "Nintendo Switch" only. And you just met me in a couple of posts and already know if somebody else have knowledge than me? What I wrote is the reality of data, there is no perfect filesystem / storage, it hasn't been created yet.

I thought I would be able to collaborate in this scene, maybe share some tools, like I did for the PS3 scene, but if people will be like this, I better spend my time doing something else.

Take care!

SeeYa!

Bye

 

[anhminh]

Man, I wish Atmostphere CFW have cool shit like this.

 

[EmulateLife]

If someone really cares about it here's a google search for you, there's tons of places talking about exfat corruption.

https://www.google.com/search?q=exf...rome..69i57.2996j0j4&sourceid=chrome&ie=UTF-8

Here's CTCaer (maker of Hekate)

I guess he doesn't know what he's talking about though, he's only one of the biggest reasons why Nintendo Switch is hacked, and nothing has changed since 2018 it's not possible with a system update to improve the file system.

 

[Deleted User]

Nope you're wrong, I had corruption on the Switch itself from an error. I always eject properly.

I don't care how many mods you've done I'll take the word of m4xw and countless threads of people saying "I'm on exfat and my sd card is corrupted" as well as my own personal experience.

There is no "old news" when it comes to Switch's file system nothing at all has changed Nintendo hasn't improved the file system at all so you made that up. The only way they can improve it is with a new Switch model. Nintendo has zero reasons to improve it though because the corruption happens on homebrew on hacked consoles not on real Switch games.

Exfat users always have an excuse why they have corruption funny how Fat32 needs no excuses. It's just the logical file system to use to avoid all corruption, that's a fact.

Yeah I made that up, hombrew software(S) have never been updated since hack was released?

Exfat users always have an excuse? Well my excuse is it works 100% for me and my clients

It really comes down to user error in 99% of cases

The choice is there and I go with the better option exfat with no issues

--------------------- MERGED ---------------------------

If someone really cares about it here's a google search for you, there's tons of places talking about exfat corruption.

https://www.google.com/search?q=exf...rome..69i57.2996j0j4&sourceid=chrome&ie=UTF-8

Here's CTCaer (maker of Hekate)

Thats over a year old

fws have changed
hombrews have been updated
exfat running flawless here

 

[EmulateLife]

Yeah I made that up, hombrew software(S) have never been updated since hack was released?

Exfat users always have an excuse? Well my excuse is it works 100% for me and my clients

It really comes down to user error in 99% of cases

The choice is there and I go with the better option exfat with no issues

--------------------- MERGED ---------------------------




Thats over a year old

fws have changed
hombrews have been updated
exfat running flawless here

I don't believe you've modded any systems because you just don't know what you're talking about. I could say I've modded 601 systems it doesn't mean anything. Firmware updates cannot improve the file systems. Why would Nintendo need to improve it? It's a homebrew issue on hacked consoles not legit Switch games.

CTCaer and m4xw on my side, so I win by a landslide.

 

[Deleted User]

I don't believe you've modded any systems because you just don't know what you're talking about. I could say I've modded 601 systems it doesn't mean anything. Firmware updates cannot improve the file systems. Why would Nintendo need to improve it? It's a homebrew issue on hacked consoles not legit Switch games.

Sorry you don't know what you are talking about.

I don't care if you believe me or not.

We already know exfat issues are a thing of the past so stop spreading old info.

Reminds of the oh no don't cut the back plate to fit trinket or else switch will overheat.

 

[EmulateLife]

Exfat on micro sd is an absolute nightmare if u use Retroarch. I had to reformat repeatedly ad nauseam (a real pain with a 512GB micro sd) until I switched to fat32 which has no probs at all. File size for installs is irrelevant if u use an exfat usb/hard drive for installs/xci booting which works great.... Exfat on microSD though ... dreadful!

But it's not possible corruption on Exfat doesn't exist, you must not have updated since 2018!

This happened one page ago, yeah really old.

 

[Deleted User]

But it's not possible corruption on Exfat doesn't exist, you must not have updated since 2018!

This happened one page ago, yeah really old.

Exfat on micro sd is awesome if u use Retroarch. I had to never reformat repeatedly with no probs at all. File size for installs is irrelevant if u use an exfat usb/hard drive for installs/xci booting which works great.... Exfat on microSD though ... awesome!

Says over 600+ modded happy exfat customers - And yeah a few of those exfatters are from gbatemp

Exfat gang 4 life

Now this is more recent than yours so case closed

User erros, bad card, fake card, not ejecting, power failures etc - Will cause corruption

 

[EmulateLife]

You should go crawl back in whatever hole you came from because I keep making the arguments that you keep changing "exfat corruption doesn't exist "exfat corruption was fixed a long time ago" look silly.

--------------------- MERGED ---------------------------

Thank you that's good advice, and no it hasn't changed there's not one bit of proof it's changed at all except one person saying it.

 

[Deleted User]

You should go crawl back in whatever hole you came from because I keep making the arguments that you keep changing "exfat corruption doesn't exist "exfat corruption was fixed a long time ago" look silly.

My job here is done

You should go crawl back in whatever hole you came from because I keep making the arguments that you keep changing "exfat corruption doesn't exist "exfat corruption was fixed a long time ago" look silly.

--------------------- MERGED ---------------------------

Thank you that's good advice, and no it hasn't changed there's not one bit of proof it's changed at all except one person saying it.

LOL 2018 called, they want their exfats back

I use retroarch daily on exfat with 0 issues

Like I said, old news , the CFW veterans know whats up

Since you dont know how to count, it's 2 people telling you =1+1

 

[frostii]

I'm confused, I thought this was a forum on the SX Autoloader.....

 

[KongsNutz]

I hope everyone using exfat and homebrew corrupts and loses 100+GB because they deserve it.

 

[asper]

2011-0301 error solution (if your card is NOT corrupted): if you have MANY MANY files on your microSD (ex. more than 50.000 including cover arts, screenshots, etc) you will get that error on boot even if your microSD is perfectly working (FAT32/exFat). I suppose a new version avoiding the scans of those "file-rich" folders will be released soon.

 

[KingMuk]

this works flawless on my micro sd card and HDD! Fucking amazing

 

[mrdude]

But it's not possible corruption on Exfat doesn't exist, you must not have updated since 2018!

This happened one page ago, yeah really old.

Exfat corruption does exist, If you are using an app (atmosphere for example), and the app writes logs or data such as a save to the micro sd card, and the switch crashes - the file allocation table an become corrupted.

Horizon OS Fat32 driver doesn't suffer from this, however the EXfat driver does - there's a write up on the Switch wiki about this - and a few posts on this forum explaining that already.

Even with the latest Firmware, this problem persists - but it's down to Nintendo's firmware (exfat driver). I have had corruption happen quite a few times on exfat while 'testing/modding/making' software for the Switch, (using original Sandisk microsd). If you want to test yourself - load a dodgy module or old amiiswap nro file (on on the github) and make your switch crash a couple of times, then go to your games and do a data check - I'll bet some of them are corrupted.

This doesn't happen on fat32 though, as the file allocation table has a backup created, so if your device crashes, it gets restored upon reboot (as far as I know).