How To Regenerate A Specific ROM Folder?



  • Hi All..

    I accidentally deleted a rom sub-folder and it's contents by mistake. Specifically the 'colecovision' sub-folder in my 4.1 version Recalbox.

    Is there a hidden feature/function that I can run that will re-generate all or specific rom folders (and their files) so that I don't have to re-install the entire Recalbox from scratch again?


  • Banned

    @tdelios you just have to recreate the folder nothing more



  • doesn't recalbox automatically create the folder if it is missing when you start it anyways? for me it's been like that if I recall correctly.
    edit: I see you're talking about recreating the deleted roms. well, you could use a file recovery tool on your PC and scan your SD Card/USB stick/HD, but I recommend to keep backups of your recalbox roms ony your PC, that you can simply copy back to your recalbox anytime, once you fuck things up. that's what I do.



  • @tdelios the automatic par depends on many things ... Regarding a rom folder : it's supposed to be recreated



  • @gmgman @voljega @Substring

    I tried rebooting the 4.1 a couple of times and still no 'colecovision' sub-folder under the rom folder is not generated.

    I manually created the 'colecovision' folder, rebooted but the 3 common system files that normally appear in each rom folder (_lisezmoi , _readme, gamelist) are not generated in my manually created 'colecovision' folder.

    I dumped all my .COL rom games into the 'colecovision' folder, rebooted and no colecovision displayed on the screen and the 3 system files are still not generated.

    Does anybody have the 3 default files (_lisezmoi , _readme, gamelist) from their 'colecovision' folder from a clean 4.1 installation?

    I don't want to go through the whole installation all over again.



  • @tdelios i made the test myself and it does regenerate. Are you running the latest unstable ?



  • @Substring yes.. I ran the update just to be sure..

    Also, to confirm, the 'colecovision' sub-folder should be located under:

    recalbox\share\roms\

    I have 45 sub-folders under 'rom' , one of which I manually created the 'colecovision'.. If I remove that manually created folder, the only sub-folders that start with the letter "C" is 'cavestory'.

    am I missing something?



  • @tdelios wait wait wait which pi are you running ? Are you sure /recalbox/share_init/roms/colecovision exists ?



  • @Substring

    Running Raspberry Pi version 3 .

    don't have a 'share_init' folder.. just a 'share' folder as you can see from one of my attached screen shots: http://www3.zippyshare.com/v/N8K5dK2x/file.html

    The second screen shot shows a 'colecovision' folder only because I put it there due to Recalbox not generating the folder (and any files within it).
    http://www3.zippyshare.com/v/ydcJAjZc/file.html



  • @Substring

    I upgraded around 2 months ago from whatever the current version release was at that time to the 4.1 unstable version and then from the 4.1 unstable. Then recently, it asked me again to update to the latest version of 4.1.. I'm guessing there was at least one release in the 4.1 version since its conception.



  • @tdelios you're not showing me /recalbox/share_init/roms. You can't rezch that folder from network, you need ssh



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

    not too familiar with ssh


  • Staff
    Developer
    Team
    Global moderator
    Translator

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



  • @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



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



  • @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



  • 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 ?



  • @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?



  • @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 ?



  • @Substring upgrade from a 4.0



Want to support us ?

341
Online

80.5k
Users

21.7k
Topics

158.4k
Posts