Hi, that's what I've got switching on DM10 module.
I'm truly surprised. That file was only 233 Kbytes (which is typical of a kit program). Maybe it's just a custom splash screen? I'm sorry but 233 Kbytes isn't enough for a true firmware. Admittedly I'm very shocked your DM10 starts up that way after you installed that very small program. You may have stumbled on something with big potential. I may have to play around with this myself.
Keep in mind however you still do not have the base sound set of the REDbox. That file is 59 MB. (found at the bottom of the page in the link you posted earlier). So I still doubt you are truly 100% REDbox compliant. Still a big find however!
Thank you very much for sharing this information with the forum.
What's the deal with flashing the DM10 in respect of regression? If one was to attempt this, and it failed, could you revert back to the Alesis firmware easily?
That's the sticking point right now. I don't know if this REDbox file really changes the DM10 to think it's a REDbox and if it does I don't know how to make it a DM10 again. I'm wondering if this is a one way deal.
I hesitate to say this because I do not want to be responsible for anyone who screws up their module. If you decide to do anything that is suggested in my post about this topic, it is on you and you alone. That is the up front warning.
With that said, I'm wondering if once the small update file in uploaded to the DM10 and it now thinks it's a REDbox, if installing the 59 MB standard file would then make the DM10 truly a REDbox. That's assuming the base REDbox sound set can be recognized by the DM10.
Here's the thing, The REDbox interface looks different than the DM10. If you can make the screen look like the REDbox then I guess it's now a REDbox. Note the differences in the picture of the two screens.