Eaglebeak54

I guess it matters not our profession. We all have unbelievable stories we can tell. 😆

On a more somber note, short of using an EverSD, which I do not own. I would hate to be an owner of what is now a legacy cart and have it fail on me. With no hope of replacement--Oh, the pain!!! 😧

Tell that to Microsoft, Apple, and Linux. 😉 And while I definitely agree with your sentiment, if you only store updates on the console, users will lose the ability to move their saved game states and high scores to other Evercade Consoles. Yes, doing so will definitely prevent such corruption, but you may upset a really large number of the client base who really like that feature. That's a war I'm not prepared to start. 😃

There have been a lot of posts (elsewhere) creating FUD regarding Blaze. The fact is, however, that many people including myself have updated their carts without issue; so the process works. Therefore the followup question with a couple of qualifiers is, "If the consoles and the carts are all of the same build quality and there has been no power outage or a cart/console is not on the brink of failure, what else is left to cause failure? The answer has to be on some level, "user error." When the screen goes black and a user thinks the update is done and pulls his cart, you have file corruption. When the update takes longer than expected and the user is in a hurry and pulls the cart to start over without a proper shutdown, you will likely have file corruption. Just because users can hot swap their carts on an Evercade (although it is still recommended to "Quit Game" first), does not mean it is safe to pull the cart when it is being written to. Sometimes we don't know and sometimes we don't think because we do things out of habit, but blaming Blaze as some have rushed to do should be reconsidering, as again "the process works." The only thing I could possibly find fault with Blaze on is that they need to assume that everyone knows nothing about updating software/firmware. A video showing how the process is done with all the other caveats about not turning off the device during updates, proper shutdown procedures, power requirements, etc., along with written instructions should be made available with a link. If a user fails to avail themselves of this information and the fault turns out to be theirs, I don't think they should be pointing a finger at Blaze. From a former PC tech's perspective this is just too obvious. I actually had a couple of clients who were just powering down their PCs by pressing the power button and then wondering why their PCs were acting up. For the well-initiated I could tell you a number of unbelievable stories and yet they'd all be true. I'm not being critical here at all. I'm simply pointing out that everyone is a novice about something and they need information and sometimes a bit of hand holding.

What John Champeau does for the Atari 2600 is nothing short of amazing. I started with Champ's Galagon, Wizard of Wor, and have now added Elevator Agent. These samples are enough to tell me that he is the Wizard of Atari 2600. Currently I play them on a 7800, but right now I can only dream that he or another genius will make it possible to also emulate them on the 2600+ and even the VCS-800. Yes, I'm one of those who'd like to have it all. But for today as Frankie Valli might sing it: 🎶 ...So close, so close, and yet so far. 🎶 😀