MX4SIO not detected

[Migsi]

I just downloaded this build (EXFAT-MX2SIO variant) and replaced my existing very old one, but after rebooting the console and replacing the usb drive with my MC2SIO, it does not get detected. I tried swapping the slots, but when I put the MC into slot 1 not even the contents of the actual MC get recognized. The MC2SIO is working otherwise and is properly recognized within OPL, so I doubt it is an issue with my SD card. Is there anything I might have overlooked or could this be some other issue?

[israpps]

MX4SIO Is recognized by the software as a new USB device due to the design of the BDM manager

Therefore. For forcing wLaunchELF to read the mx4sio you need to open the mass:/ directory

After that the program will search for multiple USB devices connected and MX4SIO.

So opening mass:/ and going back should make it show up

[Migsi]

I tried to open mass:/ but was presented with an empty directory only. Nothing changed after going back and entering again. Though, I didn't know the rename was supposed to happen after the first try to open that, you might add this info to the readme.

[israpps]

I tried to open mass:/ but was presented with an empty directory only. Nothing changed after going back and entering again. Though, I didn't know the rename was supposed to happen after the first try to open that, you might add this info to the readme.

My mod masquerades any mass#:/ device Wich corresponds to mx4sio as mx4sio:/

[Migsi]

My mod masquerades any mass#:/ device Wich corresponds to mx4sio as mx4sio:/

I've got that now, it's just not clear from the readme. Anyway, the issue still persists. I just tried using another brand new Samsung MicroSD. It is strange, as in OPL I encounter no issues at all. I don't know to what extend the driver version you are using and the one OPL ("latest" from last weekend) uses differ, as there seems to be a driver improvement WIP. Maybe that is the curlprit?

[israpps]

My mod masquerades any mass#:/ device Wich corresponds to mx4sio as mx4sio:/

I've got that now, it's just not clear from the readme. Anyway, the issue still persists. I just tried using another brand new Samsung MicroSD. It is strange, as in OPL I encounter no issues at all. I don't know to what extend the driver version you are using and the one OPL ("latest" from last weekend) uses differ, as there seems to be a driver improvement WIP. Maybe that is the curlprit?

the difference is that my wLaunchELF mod uses a relatively older mx4sio driver (1 month or so?)

Before some rushed changes were made to the BDM drivers (wich includes mx4sio)

anyway, the version of the driver used by this mod already has the compatiblity changes made by Qnox.

not sure what's going on with your setup TBH

I cant guess too much without being capable of reproducing your issue to debug it...

Are you sure the build you're using has MX4SIO Support enabled?

go to FileBrowser > MISC > BuildInfo
see if it says MX4SIO=1

[Migsi]

Sorry, was on a short holiday over the weekend.

anyway, the version of the driver used by this mod already has the compatiblity changes made by Qnox.

Ah, so they are done already? Had the impression they are still WIP. Anyway, as my SD card is otherwise working fine, I do not really suspect that to be an issue. Except if the tweaks actually broke support for my two cards >.<

not sure what's going on with your setup TBH

I cant guess too much without being capable of reproducing your issue to debug it...

As you changed the title, I was referring to the exact adapter, which is an MC2SIO from Link, hoped that might help, as I don't have any other MX4SIO adapters.

Are you sure the build you're using has MX4SIO Support enabled?

go to FileBrowser > MISC > BuildInfo see if it says MX4SIO=1

I just checked this to be sure, but yes, the BuildInfo says 'MX4SIO=1' and 'EXFAT=1' (as my SD cards are exFAT). I didn't try yet to reformat one to FAT32, could also be it's the filesystem, not the MX4SIO part. I'll report back as soon as I had time to try that. In case there is anything else I can provide you to figure this out, I'd be happy to do so.