At the end of the day, the fact that the existence of MAME, even in its infancy at the time, had encouraged people to maintain a global "redundant backup" of the data it documented, was how these companies still had their data available when they wanted to re-release it.
-
Näytä tämä ketju
-
This absolutely isn't intended to go all holier-than-thou on other projects, or other preservation teams. There are ones that are amazing, like the CD-i community, and the Internet Archive folks.
1 vastaus 0 uudelleentwiittausta 51 tykkäystäNäytä tämä ketju -
Hidden Palace as well, they do deep-dives into what they get, then release it. Amazing folks. All the same, there are many who hold things to their chest for months, even years, until they get a chance to use that data for their own self-promotion.
1 vastaus 0 uudelleentwiittausta 44 tykkäystäNäytä tämä ketju -
Ultimately, if your so-called preservation team is one bad day, one failed hard drive, one missed domain re-registration, or one cloud backup away from not having anything at all preserved, re-think what you claim to be dedicated to, because it isn't what you think.
1 vastaus 6 uudelleentwiittausta 64 tykkäystäNäytä tämä ketju -
At the end of the day, if you claim to be involved in preservation, you should ask yourself one very important question:pic.twitter.com/YngpUOMRav
1 vastaus 0 uudelleentwiittausta 46 tykkäystäNäytä tämä ketju -
Just as a final post-script, a point that I omitted: If you're just building up archives of boards, of discs, of floppies, you're not preserving anything. Bit-rot is a thing. Disc rot is a thing. Magnetic coercivity going down over time is a thing.
1 vastaus 5 uudelleentwiittausta 56 tykkäystäNäytä tämä ketju -
Unless you can be absolutely sure that your archive is documented, with wide hashes, and backed up across countless machines such that nothing short of an apocalyptic event would make it unavailable, it hasn't been preserved. Release, or become equally lost.
5 vastausta 10 uudelleentwiittausta 63 tykkäystäNäytä tämä ketju -
Vastauksena käyttäjälle @TheMogMiner
Well my archiving is a bit of a failure as there isn't any mame equivalent to contribute the data to. I would need to build some mame equivalent for emulating old home keyboard sound chips to begin with and I don't have expertise to do that. I hope I can find a solution one day
2 vastausta 0 uudelleentwiittausta 2 tykkäystä -
Vastauksena käyttäjälle @kashiokyoiku
That's not true, though. MAME has skeleton drivers for a boatload of music keyboards, even if the main CPU happens to be a microcontroller (known or not) with an internal ROM. As long as there's something dumpable, it can be included, and documented as well as possible.
1 vastaus 0 uudelleentwiittausta 2 tykkäystä -
Vastauksena käyttäjälle @TheMogMiner
Well that is the other issue, tricking the proprietary cpus into dumping the mask rom (likely from a test mode). Some of the external roms have been floating around for years on a synth rom dumping site but I feel without the mask roms the functionality won't be there.
1 vastaus 0 uudelleentwiittausta 0 tykkäystä
It's better for documentation to at least exist in a more public form, via the MAME source code, than buried away on an obscure synth-dumping site. Having the system's dumping needs front-and-center could at least inspire someone to look into it more deeply.
-
-
Vastauksena käyttäjälle @TheMogMiner
priority was 2 build full list of chips first, focus my limited resources on the ones most important 2 emulate & know which models i have to spend 10 years searching for 2 find chip. Then try 2 match instruments 2 patents so I might be able 2 interview inventors b4 they all die
2 vastausta 0 uudelleentwiittausta 0 tykkäystä -
Vastauksena käyttäjälle @kashiokyoiku
A decent plan, but in the short term, perhaps feed a MAME developer (me?) chip dumps and chip/machine info, so that skeleton drivers can be built and pull-requested in a more real-time manner.
1 vastaus 0 uudelleentwiittausta 1 tykkäys - Näytä vastaukset
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.