Issues with placing ROMs in boot

[Kev_S]

Hi all I thought I resolved the problem with roms being placed in the /boot directory, but the system doesn't like what I have done.
first I executed the following commands

mv ~/mame172/roms ~/mame172/roms_old
mkdir ~/mame172/roms
chmod 777 ~/mame172/roms

I modified /home/pi/.attract/emulators/mame172.cfg
I remarked out
#rompath /boot/romsArcade/mame-172
and replaced it with
rompath /home/pi/mame172/roms

I copied roms to the new location, and I get an empty list of roms in attract mode.
do I need to manually modify attract mode in the app?

The reason why I am changing the directory is because /boot is too small, and feel it's bad mojo to have non-boot related files in /boot.

[dee2eR]

You would also need to adjust the rom scanning script as well as the Attract-Mode config for any emulators you're moving the rom directory for and also possibly the launcher script. Check out /boot/lauchers/ and /home/pi/.attract/

Honestly, you're probably better off just adjusting the partitions using the Idaho Garagecade guide: http://aha-forums.com/wp/2018/02/02/how ... ory-cards/ It's probably quicker and easier to fire up GParted rather than edit all the scripts and configs, especially if you are using more than one emulator.

I realise having the roms stored on boot is non standard but as far as I know it hasn't caused an issue for anyone in over 5 years of having it set up this way. Ideally Windows wouldn't be gimped in regards to SD card partitions (or everyone would use Linux....) and the roms could be in /home/ and I could just set it up like most RPi distros. As it is, the roms are only on /boot/ so Windows users can easily copy roms onto the SD card.

[Kev_S]

Thank you. To simplify the ability to copy ROMs wouldn't it be more simple to use windows sharing (SAMBA) in linux?

I have a significant number of ROMs which I have collected and updated since the early 2000's. Extending Fat32 beyond 64G is not advisable and is prone to a high level of corruption. I realise I might be in the minority in the experience I am after. I am happy to make mods to suit my needs. Also, I am happy to assist people once I have more experience with the build you've constructed. I have supported Linux since the late '90s

after a number of failed attempts, I found what I need to do.

1. modify .attract/emulators/*.cfg files
2. modify the rom variable in mame.ini
3. updated the ScanRoms_V007.sh (not sure if this is valid.)

if you want Windows sharing I can supply the smb.conf file.

[NeoSurfer]

Questions:

Finally upgrading to 3.9, from 3.84? My build takes a while to scan Roms, and RomS are in Arcade or Console folders.

- Do I need to ensure any files carry over... or is 3.9 a clean build? Maybe a high scores file?

- I transferred my Rom files to 3.9 into the same file folders they were in 3.84. Yet, after I boot up I see the file names in attract but they do not load in emulator? Actually, only my roms Files from FBA will load in emulator.

- Last, looked at 4.1 and saw an Atomiswave/Naomi and Dreamcast emulator!!! Can these be thrown into my 3.9 build or are they exclusively for 4.1?

Thanks....Amazing Software!!!
J