I'd love to see it implemented, is anyone willing to follow up on that. It is good that there are choices for people.
New here so might have some protocols wrong - be kind if that is the case.
While I am new here, I am not new to open source development, and as such have seen a few splits. That, with what seems to be some confusion about loaders and the TESVAL core (or maybe friction between users in various camps) I was worried that development and testing would split too far, and evaluation might be influenced by loader and not core.
Thus I started to split things out, and as there were comments about keeping the core assembler, I followed that route. Due to holiday events and such, I did not get this up earlier, and then I saw Alexander working on r3, I was thinking about not posting this, as it seemed things could be already too far along, but depending on general consensus, maybe not.
Anyhow, this is a split of the last TESVAL into the core library, and then two plugins for the loaders (borrowed some SkyBoost code, hope it’s not that much of an issue). The main issue as I see it, is to decide the structure, and what format the core should go - if Alexander is willing, I can include the latest SkyBoost code as core, or try to convert it to assembler, but at the end, the people who will maintain it will have to decide. I can give it a week or two more time, but when work starts, I cannot guarantee anything

I did not include any binaries, as it’s more about layout/naming and what direction the backend should take. To build however, you need to add the Fasm directory to "Executable files" and it’s include directory to "Include files" in Visual Studio.
Download is http://www.mediafire.com/?v13zr6iprsqdi1a
Comments are appreciated.
PS: No credits for anything I did needed.