How To Regenerate A Specific ROM Folder?

[tdelios]

@Substring
how do I do that with winscp and the terminal window?

not too familiar with ssh

[paradadf]

@tdelios just log in with winscp and navigate to recalbox/share_init/roms

[tdelios]

@paradadf
I tried to do that using terminal, but it gives me an error that no such file or directory when I try to "cd share_init" folder

here is a screen shot when I run the 'ls' command to show you what I see on the screen: http://www102.zippyshare.com/v/214FNZjH/file.html

[Substring]

@tdelios just ls -la /recalbox/share_init/roms

[tdelios]

@Substring @paradadf

recalbox's response:

/boot$ ls -la /recalbox/share_init/roms
total 184
drwxr-xr-x 46 root root 4096 Feb 20 04:58 .
drwxr-xr-x 12 root root 4096 Feb 8 18:36 ..
drwxr-xr-x 2 root root 4096 Jan 1 1970 amstradcpc
drwxr-xr-x 2 root root 4096 Jan 1 1970 atari2600
drwxr-xr-x 2 root root 4096 Jan 1 1970 atari7800
drwxr-xr-x 2 root root 4096 Jan 1 1970 atarist
drwxr-xr-x 2 root root 4096 Jan 1 1970 cavestory
drwxr-xr-x 3 root root 4096 Jan 1 1970 fba
drwxr-xr-x 2 root root 4096 Jan 1 1970 fba_libretro
drwxr-xr-x 2 root root 4096 Jan 1 1970 fds
drwxr-xr-x 2 root root 4096 Jan 1 1970 gamegear
drwxr-xr-x 2 root root 4096 Jan 1 1970 gb
drwxr-xr-x 2 root root 4096 Jan 1 1970 gba
drwxr-xr-x 2 root root 4096 Jan 1 1970 gbc
drwxr-xr-x 2 root root 4096 Jan 1 1970 gw
drwxr-xr-x 2 root root 4096 Jan 1 1970 lutro
drwxr-xr-x 2 root root 4096 Jan 1 1970 lynx
drwxr-xr-x 4 root root 4096 Jan 1 1970 mame
drwxr-xr-x 4 root root 4096 Jan 1 1970 mastersystem
drwxr-xr-x 2 root root 4096 Jan 1 1970 megadrive
drwxr-xr-x 2 root root 4096 Jan 1 1970 moonlight
drwxr-xr-x 2 root root 4096 Jan 1 1970 msx
drwxr-xr-x 2 root root 4096 Jan 1 1970 msx1
drwxr-xr-x 2 root root 4096 Jan 1 1970 msx2
drwxr-xr-x 2 root root 4096 Jan 1 1970 n64
drwxr-xr-x 2 root root 4096 Jan 1 1970 neogeo
drwxr-xr-x 8 root root 4096 Jan 1 1970 nes
drwxr-xr-x 2 root root 4096 Jan 1 1970 ngp
drwxr-xr-x 2 root root 4096 Jan 1 1970 ngpc
drwxr-xr-x 2 root root 4096 Jan 1 1970 o2em
drwxr-xr-x 2 root root 4096 Jan 1 1970 pcengine
drwxr-xr-x 2 root root 4096 Jan 1 1970 pcenginecd
drwxr-xr-x 3 root root 4096 Jan 1 1970 prboom
drwxr-xr-x 2 root root 4096 Jan 1 1970 psx
drwxr-xr-x 2 root root 4096 Jan 1 1970 scummvm
drwxr-xr-x 2 root root 4096 Jan 1 1970 sega32x
drwxr-xr-x 2 root root 4096 Jan 1 1970 segacd
drwxr-xr-x 2 root root 4096 Jan 1 1970 sg1000
drwxr-xr-x 2 root root 4096 Jan 1 1970 snes
drwxr-xr-x 2 root root 4096 Jan 1 1970 supergrafx
drwxr-xr-x 2 root root 4096 Jan 1 1970 vectrex
drwxr-xr-x 2 root root 4096 Jan 1 1970 virtualboy
drwxr-xr-x 2 root root 4096 Jan 1 1970 wswan
drwxr-xr-x 2 root root 4096 Jan 1 1970 wswanc
drwxr-xr-x 2 root root 4096 Jan 1 1970 zx81
drwxr-xr-x 2 root root 4096 Jan 1 1970 zxspectrum

[Substring]

No colecovision ... So of course the folder can't be recreated !
So i'd say you're either running a pi for which colecovision is.not compiled, either you removed the colecovision from the share_init folder.

So once again : which pi are you running ?

[tdelios]

@Substring @paradadf

I'm running Raspberry Pi version 3 ..

I did not remove the 'colecovision' from the share_init folder as you can see I am not that articulate to do so.. I simply connect to my windows pc to the \roms folder that is available to me.

As I mentioned before.. the 'colecovision' sub-folder was in the recalbox\share\roms\ folder once during the initial upgrade to 4.1.. but once I deleted it, it never came back.
So it must be a bug.. not sure if it can be producable, but it is..

either way, how can I get my 'colecovision' folder back with all the findings presented to you so far?

[Substring]

@tdelios gotta check few things before I tell you how to proceed. Are you running a 4.1 img or an upgrade from 4.0 ?

[tdelios]

@Substring upgrade from a 4.0

[Substring]

@tdelios the way the share_init/roms folder is generated was totally remade in 4.1. I may have missed a system but no : colecovision IS there. Get the files from https://github.com/recalbox/recalbox-buildroot/tree/master/board/recalbox/fsoverlay/recalbox/share_init/roms/colecovision

[tdelios]

@Substring so what are the steps\commands to dump them into the 'colecovision' sub-folder assuming I have to create it under the share_init/roms folder using terminal in WinSCP?

[Substring]

@tdelios So, through SSH :

mount -o remount, rw /
mkdir /recalbox/share_init/roms/colecovision
cd /recalbox/share_init/roms/colecovision
wget https://raw.githubusercontent.com/recalbox/recalbox-buildroot/master/board/recalbox/fsoverlay/recalbox/share_init/roms/colecovision/_lisezmoi.txt
wget https://raw.githubusercontent.com/recalbox/recalbox-buildroot/master/board/recalbox/fsoverlay/recalbox/share_init/roms/colecovision/_readme.txt
reboot

Tadaaa should work as expected

[tdelios]

@Substring the commands worked, but once I rebooted the Raspberry Pi, the 'colecovision' sub-folder was not automatically created in the share\roms

I'm basically tapping out for a manual fix..

Do you know when the 'stable' version of 4.1 may come out roughly or at least do you have a link for me to download the image file of the 'unstable' 4.1 so that I can redo a full build on that version to start.

thanks for all your help
tom

[paradadf]

@tdelios are you sure you are on (the latest) 4.1 unstable? If so, have you try updating again?

[Substring]

@tdelios we never give any ETA. And I do believe your 4.1 is totally broken

Get the .img here : http://archive.recalbox.com/updates/v1.0/unstable/

remember, this is unstable, expect some changes, even in an img, oe day or another. That's why i will never stress enough to put roms on a USB key. This way you are safe of experimenting on the SD without fearing anything for your roms

[tdelios]

@Substring thanks for the link... I've worked in software and hi-tech my whole life.. so taking your comments to hear.. lol...

cheers
tom

[tdelios]

@Substring @paradadf
Interesting experience.. from the link you provided: http://archive.recalbox.com/updates/v1.0/unstable/

in which I downloaded the Raspberry Pi 3 image recalbox.img (sha1) using link: http://archive.recalbox.com/updates/v1.0/unstable/rpi3/recalbox.img.xz.sha1

I loaded the image on a fresh new Micro SD card and rebooted the system.

When I used my Windows computer to \recalbox\share\roms
I noticed that the 'colecovision' folder is not in there as well !!!

when I used WinSCP and terminal into the system, I ran the
ls -la /recalbox/share_init/roms command and 'colecovision' appears in there.

I rebooted my recalbox a couple of times to see if it would self-generate the 'colecovision' sub-folder in the \recalbox\share\roms but it didn't...

And this is a fresh new install using your image file on virgin Micro SD card with nothing on it.

[Substring]

@tdelios the share part is created by a script on boot if it's missing. The same goes for every folder in the share_init/roms folder. When I told you that it should be created, i tested it myself on my pi. So i'm very sceptical about what you're saying, although i'll try

[tdelios]

@Substring give it a try using your Pi3 and the link I provided to you.. clean micro SD memory card. Use Win32DiskImager or whatever you use to load the image file from the link I gave you. Put it in the Pi3 and then let it go through.. Reboot once or twice if you want for good measure and then use your windows computer to \recalbox\share\roms
and you tell me if you see the 'colecovision' folder. It probably won't be there as I am going to do the steps one more time..
And then check the share_init using
ls -la /recalbox/share_init/roms
command and 'colecovision' should appears in there but not in \recalbox\share\roms

[tdelios]

@Substring

so I tried it again on a brand new Micro SD card on my Pi3 with the same steps downloading the 4.1 unstable img file file and loading it and rebooting.
Same result. The 'colecovision' sub-folder does not get created in the \recalbox\share\roms
but the 'colecovision' sub-folder does exist in the \recalbox\share_init\roms .
Not sure why it is not re-generating after reboot.

I even tried to install a fresh install of 4.0.1 and then perform the upgrade to 4.0.2 and then change the updates.type=unstable in the recalbox.conf file with a reboot after, but for some reason it does not detect an update to jump to 4.1 from 4.0.2