Probably you dont have the latest MENU and firmware.
Here is a pic of my sd card (menu 04-01):
![]()
![]()
Probably you dont have the latest MENU and firmware.
Here is a pic of my sd card (menu 04-01):
![]()
![]()
Yeah, the other side doesn't have them so I was worried they are meant to go inside to make the risers a little bit taller?They are not really needed but just put one on each screw you removed.
^THIS!@SmokeMonster @Darksoft @Mitsurugi-w - have you considered changing the rollup pack into an image instead of bare files?
I see no advantage to bare files as you can't add individual games to the card it needs to be reformatted when you want to do so.
If you were to make an image (preferably .img for compatibility) then you can use Win32DiskImager on Windows or Etcher on Mac and you would remove a lot of the issues you're having now with microsd cards because the physical data on the card would be a mirror image every time.
It also means you can write the card on any version of any operating system and would also remove the issues of people adding in bootlegs/hacks/other stuff from MAME that aren't yet supported.
I clearly see pros in the img approach, but, at the same time, I see controversial aspects.I love this idea.
Yeah I see; problem is one of the methods is… highly problematic!The idea is to offer both so that everyone can use their preferred method.
I think offering a utility would be more complicated. One would have to start catching roms, learn to use the utility, someone would have to use time to design/develop/test the utility, what about those who (like me) do not use Windows nor macOS...even more variables than writing the files yourself to the microSD. I do agree, however, that the kits should have a more resilient microSD access, the mere fact of finding an unexpected file should not make them act crazy, it simply should be ignored...Yeah I see; problem is one of the methods is… highly problematic!IMHO a Smoke Monster Pack with an added utility, like the NeoSD one, for building ROMs from a local MAME romset should be the only options available here (leaving the other "options" to the interwebz). This is something that should be addressed sooner or later.The idea is to offer both so that everyone can use their preferred method.
Regards.
Locutus73
^THAT^I think offering a utility would be more complicated. One would have to start catching roms, learn to use the utility, someone would have to use time to design/develop/test the utility, what about those who (like me) do not use Windows nor macOS...even more variables than writing the files yourself to the microSD. I do agree, however, that the kits should have a more resilient microSD access, the mere fact of finding an unexpected file should not make them act crazy, it simply should be ignored...Yeah I see; problem is one of the methods is… highly problematic!IMHO a Smoke Monster Pack with an added utility, like the NeoSD one, for building ROMs from a local MAME romset should be the only options available here (leaving the other "options" to the interwebz). This is something that should be addressed sooner or later.The idea is to offer both so that everyone can use their preferred method.
Regards.
Locutus73
Yep, I do agree that current methods are easier and more effective for debbuging and all; I’ve stated that as a pro. Problem is they present a big, fat, huge con which cannot be ignored. We all know it's there, we cannot pretend it's not there.I think offering a utility would be more complicated. One would have to start catching roms, learn to use the utility, someone would have to use time to design/develop/test the utility, what about those who (like me) do not use Windows nor macOS...even more variables than writing the files yourself to the microSD.
I do agree, however, that the kits should have a more resilient microSD access, the mere fact of finding an unexpected file should not make them act crazy, it simply should be ignored...
Everything was done on a pc, format and menu installation, and same issues again.Aghhhh you're using a MAC. Those computers give a lot of trouble with hidden files and other kinds of stuff. See here:
Best bios to use with the multigame cart? Problems with Unibios 2.3?
Basically you need to run:
dot_clean /Volumes/sdcardvolumenamehere
Which gets rid of the stupid hidden ._ folders MacOSX creates
If you'd like I could make you an image to rule things out. Are you using a 16GB card?Everything was done on a pc, format and menu installation, and same issues again.So, maybe I will buy another slot later.Aghhhh you're using a MAC. Those computers give a lot of trouble with hidden files and other kinds of stuff. See here:
Best bios to use with the multigame cart? Problems with Unibios 2.3?
Basically you need to run:
dot_clean /Volumes/sdcardvolumenamehere
Which gets rid of the stupid hidden ._ folders MacOSX creates