You can change what path all that is stored in in the emulator settings last I knew. Change the path for the "Emulated System Storage Folder" to be where you want em saved. That being said you don't actually play the ROM files you have in Vita. It takes the data from them and installs them to storage and then plays from there. You don't actually need the ROM files once installed to the emulator unless they've really changed it all up since I last looked into it.
Bezel Project recently changed how a lot of their configuration works that we haven't changed on our side so the output of running BP independently vs us running it the process for you at this point can be quite a bit different. Honestly I'd just let LB grab em for you and turn on the settings as it tends to be a bit more full proof. That being said @dragon57 may be able to better help you understand what you need to be checking for.
Fan running at high speed almost never has anything to do with RAM. Just means your computer is getting hot. Fans may also pre-emptively be cranked up when your CPU (or sometimes GPU) is working close to full capacity. Given that Beelinks are small PCs their airflow in general is pretty lacking and so their fans have to be running pretty hard all the time. That being said overall your symptoms point more to a CPU or drive issue than it does a memory one. 16gb on a Windows machine unfortunately is pretty slim these days given how wasteful the OS is, so I'm sure the RAM update wouldn't hurt but I'm not sure it'd solve all the issues you're seeing.
We haven't changed any OS requirements. I personally still run Win10 and can run LB just fine. I DO believe we require 64bit OS but it's been like that for a WHILE now. I'd run command prompt as admin and run "sfc /scannow" (without quotes) and if it detects anything restart your computer then try again.
This is a known issue with WMP, especially in multi-monitor environments. If you're using an Nvidia GPU you can go into their control panel and enable full range color range for the monitor in question and it'll correct this.
He's rebuilt cache records in order to help with the solution but I haven't gotten word of anything since. May be best to reach out via their website. I'll reach out and see if they have a preferred place to report things like this in the future so they have better visibility on what is all affected.
Don't do it here, this is being kept alive just so we can go back and look through it if we want, otherwise this website is no longer in use and feedback should be used for reporting any issues or requesting features.
Fix has been put in for MAME importer that will be in next beta. Currently the issue that was reported with the Next button being disabled happens if there is an error thrown trying to get versions for MAME that we can auto-download. The fix will make it possible to still manually assign MAME as an emulator when that happens. If you're referring to anything else you'll need to be more specific.
Cool. The emulator you're leaving on may have a leak or is delaying it's resource release and is likely choking Big Box because of it. Glad you have a work around.