> Thank you for your reply and thank you for trying to help, but in many ways your > reply and especially the reply from BIOS-D sums up the problem. What is easy for you > to understand is not obvious or easy to follow for a layman. I understand completely > that to you, this is easy stuff, and you more than likely think I am a bit thick, but > I was only pointing out that if MAME is to become popular again it might like to make > things simpler for all the other thick people out there who want to use it.
So basically you blame others for solutions that are given to you in a easy to digest manner because you don't try them? I don't see that as a MAME developer problem.
However I can see being a problem MAME doesn't handle ROMs on their own and you have to depend fully on external ROM managers. MAME already knows where your files could be located, the content it expects and its missing files. We even have two standards everyone follows (split and merged). There should be a way to drag a compressed file ("mame.exe %1"), fill the missing content into a merged file in the roms directory and then prompt the user how to select it from the menu or how to run it using command line with the available clones if necessary.
Also I know it's important files are correct and available. But is it really necessary to stop a system functioning when you include a BIOS file you are not even willing to use? This is the reason people believe you update ROMs very often. What is so wrong about disabling the BIOS/device not found and let the game run with the BIOS/devices already selected and available? Why would a dump from a keyboard you won't even use or don't default select makes updating MAME versions a hassle for new users?
I wish I could invest solutions to these to the Github if only I had the time for it. That and turning the next CHD revision into a lossless kind of torrentzip format. Here is when R.Belmont will come and say "it is" when it isn't. There's no problem when inputing a hard drive or DVD ISO. But as soon as you input bin/cue files it creates a different "bad (formatted)" dump when extracted. The CHD could extract exactly what was inputted first given the popularity it is receiving from other emulator authors and scenes looking for ways to keep information compressed and usable.
|