MSET9
MSET9 copied to clipboard
WinError 234
just getting this when I try to inject MSET9 for the first time
Edit: I saw a reddit post where 2 guys where saying they had this error too and both where on W11, I am on W11 too so I'm going to try on another OS
We still don't exactly know why WinError234 happens. Sometimes reformatting the SD card works, sometimes you need a new reader, sometimes you need a new computer. I believe there are people looking on how to fix the error right now but so far we don't have a perfect fix. Sorry.
Probably my issue was something with Windows 11, just did it on Android and it worked fine.
I also got an error saying I had to delete the software data, even though I had already done so, but checking for the empty software data just fixed the issue, maybe the problem I had on W11 could be fixed the same way.
This is happening on W10 as well. Taking a quick look it looks like this is due to the ID1 filename/path being too long when trying to execute the mkdir()
on line 497.
I tried switching over to WSL2 on W10 which gave a better error message.
Traceback (most recent call last):
File "mset9.py", line 901, in <module>
injection()
File "mset9.py", line 744, in injection
fs.mkdir(hackedId1Path)
File "mset9.py", line 497, in mkdir
os.mkdir(self.abs(path))
OSError: [Errno 75] Value too large for defined data type: '/mnt/i/Nintendo 3DS/4980302b2377c5024f1ccebe4928cafc/\uffff\ufaff餑䠇䚅敩ꄈ∁䬅䞘䙨䙙ꫀᰗ䙃䰃䞠䞸退ࠊꁱࠅ칝ࠄsdmc退ࠊb9'
This is better than W10's:
OSError: [WinError 234] More data is available: 'I:\\Nintendo 3DS/4980302b2377c5024f1ccebe4928cafc/\uffff\ufaff餑䠇䚅敩
ꄈ∁䬅䞘䙨䙙ꫀᰗ䙃䰃䞠䞸退ࠊꁱࠅ칝ࠄsdmc退ࠊb9'
Ended up swapping to Mac OSX and it's dockerized(?) setup didn't have this issue.
Leave it to Windows to have an error named "More data is available"... Maybe it's hinting that the event viewer would give a better error? (I know WSL did, but it's possible that it's a different issue due to WSL being buggy)
temporary fix: disable Unicode support in administrative language settings.
for some reason this fixed my problem.
temporary fix: disable Unicode support in administrative language settings. for some reason this fixed my problem.
Como acotación, si te sucede este mismo problema y tienes Windows en Español (México o España) ve a Región en el Panel de Control, Cambiar configuración Regional del sistema y establece Configuración regional actual del sistema a Inglés (Estados Unidos)
As a note, if you have this issue and Windows are in Spanish, go to Region in Control Panel, Change system locale and then change Current system locale to English (United States)