@invincible There's an issue with the scrapper (saving the images causes it to crash I think). Not really a fix but more of a workaround, while importing the library I just deselect the options that causes it to reach out for images and renaming.
So what you're left with is just a readout of filenames from the server. It's kind of lame but works for the time being.
Latest posts made by GrinningMoon
-
RE: Testers wanted: major system upgrade (Pi3b+, KODI 17 and much more ...)
-
RE: Testers wanted: major system upgrade (Pi3b+, KODI 17 and much more ...)
Hi, new to the forum but I've been using RecalBox for about ~4 years. Appreciate all the hard work the devs put in!
My comment pertains to creating backup copies of the beta OS. I've tried using Win32 Disk Imager, HDD Raw Copy, and Roadkill's Disk Image on a Win7 x64 machine.
Flashing a SD card with the backup copy (both with Etcher and the other imagers) results in an OS that has none of the saved roms and doesn't save configuration options across reboots (e.g., toogling overscan or saving a wifi network is reverted back to it's default state after a reboot). This is the same with editing through the GUI or through terminal (recalbox.conf).
The only successful flashing I've had is taking the base img.xz file and using Etcher. This is driving me insane as it means the only way to make copies for another device is to redo all the work I did.I'm not sure if this is intentional as it's a beta version so the devs don't want misc copies spread everywhere or I'm doing something wrong. If you could, please let me know the recommended process for making backup copies. Is there a known method for Windows to make img.xz backups or is that only native to Linux?