pontiac76 / 0mhz-collection Goto Github PK

Bulk downloading isn't the best due to the size of the SD cards. The archive is 30gig-ish currently, and probably will only get larger over time. There are larger SDs, but, for budget friendly builds, the size of the card shouldn't be the final determination to whether the users can be included in the download.

Personally, I'm not really an RPG player, so I'd have no interest in downloading any RPG type games. Racing games, I'm all in.

Given that, the XML file we're pulling from is already there, and we can potentially database out (CSV/TSV/independent text files) to what the users preferences are for pulling files on their MiSTer with a certain default. There's not enough detail to indicate the genre of the game, but, there's at least the name of the game. If the text file for the relevant game is present, honour the settings in that file. "Do not download" or "Refresh" or whatever. I don't know what the content would be at this point, but, at least, something to indicate that only a SELECT set of files should be grabbed.

Find a way to better and automatically locate the MGL files and the VCDs.

MiSTer can be setup several ways, and with a smaller SD card, this script will not run. Manually editing the script isn't the best of ideas as any future updates is going to hurt the users when they download/pull the repo and things are overwritten.

Several issues come up because of this flexibility.

I've had instances where I've had several USB sticks plugged in, and between reboots, the USB drive swaps positions. I'm not sure if it's because of order of operations where I'm plugging things in a different order (IE: One USB stick goes into port 2, another goes into Port 1, meaning first stick gets usb0 while the second gets usb1, but on reboot, the drives are swapped)

That is an atypical problem, but, it should be thought of.

For a minimum effort at this point;

• A configuration file (Added to .gitignore) that indicates where the files should be placed.
• The script should do the initial search, prompt users when multiple directories are found.
• If the script can't find the last defined directories, prompt the user to re-search all the mounts (Yes/Abort)
• If the directories make sense, set the required variables, validate drive availability for the VCDs, and download as needed.

If the MGL file is deleted, but the VCDs still stick around, then the storage for the unused VCD is wasted.

If the VCD is deleted or not downloaded, but, the MGL still exists, then, the user is going to be given errors.

Some kind of consistency checker needs to be put in place to validate what the user wants to do.

• If the MGL exists but the VCD doesn't, then, prompt to download or delete the MGL.
• If the VCD exists, but, the MGL doesnt, then prompt to populate the MGL file, or delete the VCD.