Yeah. Is that the issue lolDo you use filezilla?
Yeah. Is that the issue lolDo you use filezilla?
Yeah. Is that the issue lol
Which FTP clients are you guys using?
Thats a error from your PC, not the Switch.
It's not relaying errors. Or does it actually say that on the console output?
Thats normal, the app does not access timestamps
That might cause some problems for some FTP clients tho
I redownloaded your build but I still get the same error.I think there isnt a non existent file (that would be a issue on your pc, not switch), but it cancels the transfer, then tries to retransfer, thus having a old failed transfer file.
This is the expected behavious on the old version, not my build.
Could you redownload it to make sure?
Tbh that sounds like your wlan kicks the switchI get the error on the console specifically. The PC just says it couldn't populate the directory.
I'm pretty sure this error is related to how I have my network setup at this point though.

Yes, I just quoted him when I posted my message.Are you using mx4ws build?
FileZilla obviously. v3.20.1Which FTP clients are you guys using?
sorry i missed that. does his build corrupt sd as well?Yes, I just quoted him when I posted my message.
FileZilla obviously. v3.20.1
Testing your build now. Will report back soon.I think there isnt a non existent file (that would be a issue on your pc, not switch), but it cancels the transfer, then tries to retransfer, thus having a old failed transfer file.
This is the expected behavious on the old version, not my build.
Could you redownload it to make sure?

I've checked, no I don't think so.sorry i missed that. does his build corrupt sd as well?
sorry i missed that. does his build corrupt sd as well?
--------------------- MERGED ---------------------------
Testing your build now. Will report back soon.
Edit: seems to be working fine now. I tried overwriting files etc as well and everything seemed to work flawlessly

"Very nice"? I have a problem that needs fixing.very nice
Hmm. Very nice that it's no longer corrupting sd cards. What you on about?"Very nice"? I have a problem that needs fixing.
Don't mean to be rude or anything.
He said very nice to the not corrupting sd part, not your issue"Very nice"? I have a problem that needs fixing.
Don't mean to be rude or anything.

I know.He said very nice to the not corrupting sd part, not your issue![]()
Using FileZilla v3.20.1, Switch 4.1.0 firmware and m4xw's build.Uploading a 2MB .nro file fails.
The Switch only goes up to literally 1,024 KB (1 MB) straight before it crashes.
Well you made it seem like a bad thing. I get you have an issue but maybe reduce your frustration. What firmware you on? His fix to FTPD seems to be working great on 5.1.0, not having any of the previous issues that people were having.I know.

4.1.0Well you made iit seem like a bad thing. I get you have an issue but maybe reduce your frustration. What firmware you on? His fix to FTPD seems to be working great on 5.1.0, not having any of the previous issues that people were having.
So my opinion is that you should upgrade to the latest firmware. Being on 4.1.0 is a bad spot to be right now for development. No one is really focusing on it and also seems to be having the most issues with apps. 2ndly, If you are hoping for a cold boot solution, you missed that train ride back in 3.0.0. 4.1.0 is extremely unlikely to get a untethered coldboot exploit. Your best bet is to use the latest hekate firmware like most of us that fixes sleep mode. I honestly havent had to power off my switch in 4 days now and have been just using cfw just fine. The only time you'll have to pull your jig out is basically if you crash. Most of the retroarch stuff has been solid lately (even while docked). I would highly recommend joining everyone else and updating to 5.1.0. If you were on 3.0.0, id pretty much say wait but you're just on a crappy firmware that not many people really are doing work for.4.1.0
Also, I just requoted my issue with my statistics on display.

Crap.So my opinion is that you should upgrade to the latest firmware. Being on 4.1.0 is a bad spot to be right now for development. No one is really focusing on it and also seems to be having the most issues with apps. 2ndly, If you are hoping for a cold boot solution, you missed that train ride back in 3.0.0. 4.1.0 is extremely unlikely to get a untethered coldboot exploit. Your best bet is to use the latest hekate firmware like most of us that fixes sleep mode. I honestly havent had to power off my switch in 4 days now and have been just using cfw just fine. The only time you'll have to pull your jig out is basically if you crash. Most of the retroarch stuff has been solid lately (even while docked). I would highly recommend joining everyone else and updating to 5.1.0. If you were on 3.0.0, id pretty much say wait but you're just on a crappy firmware that not many people really are doing work for.
Ya i know its sucks to have to keep powering off taking your sd card out and joycon off and loading the payload everytime. Im glad that we no longer have to do that with m4xw's fix to ftpd on 5.1.0 and hekates recent update that allows sleep mode. I also use that file manager too NXloader i think its called? Very helpful.Crap.
Also, you also may need to pull your jig out if you want to do any SD card management if you don't have FTP, which is what I do, and it's getting depressing and repetitive.

But I'm paranoid (mostly because of the "rumor" that "coldboot would be 0% possible on 5.x and above"), and that's my only Switch.Ya i know its sucks to have to keep powering off taking your sd card out and joycon off and loading the payload everytime. Im glad that we no longer have to do that with m4xw's fix to ftpd on 5.1.0 and hekates recent update that allows sleep mode. I also use that file manager too NXloader i think its called? Very helpful.
Honestly it's worth upgrading, its the next best thing to coldboot imo. Today is my 5th day without having to use my jig and still on CFW. I can also still use eShop etc. I think its a win win situation in your case to upgrade

