SelenitaDelSur
Member
When using MX4SIO (MC2SIO, actually), games cannot detect physical memory cards. With BDM3 build found in this forum, this is resolved, but, VMC doesn't seem to work in any version. Also, the creation of it takes forever on the MX4SIO. Just wanted to ask, is this normal? Is there a workaround to use VMC in MX4SIO?
If the answer to the question is "it's normal, VMC doesn't work with MC2SIO and there's nothing that can be done", then I guess my only option is to use a physical MC to load/save. Now, I have a multitap in slot one with FMCB MC on the first/A slot, and the MX4SIO device on the second slot. Since it would seem that a "normal" MC has to be on slot one to be able to load/save on most games, I guess my only option here would be to load a game, then replace FMCB MC with a normal one, right? Or is there a way to keep the three cards connected? Seems like FMCB only boots from slot 1 or 2, or first slot in multitap (not the others), and the MX4SIO device seems to only work on slot 2.
Thanks in advance!
If the answer to the question is "it's normal, VMC doesn't work with MC2SIO and there's nothing that can be done", then I guess my only option is to use a physical MC to load/save. Now, I have a multitap in slot one with FMCB MC on the first/A slot, and the MX4SIO device on the second slot. Since it would seem that a "normal" MC has to be on slot one to be able to load/save on most games, I guess my only option here would be to load a game, then replace FMCB MC with a normal one, right? Or is there a way to keep the three cards connected? Seems like FMCB only boots from slot 1 or 2, or first slot in multitap (not the others), and the MX4SIO device seems to only work on slot 2.
Thanks in advance!
