OK, read the article. Any Windows coder worth their salt and a belt full of tools would be able to identify the problems easily. I still think GOG could make it work without having to eat hexadecimal code and spit out the bits.
...and by the way, the assembly language *is* the source code, if you know the language of the machine. ;)
LOL! If it were really that easy, it would have been done by now. Do you really think no coder "worth their salt" has ever tried? Some of those fixes in the article were created by coders that developed some of the same tools GOG themselves use all the time. Are they not "worth their salt"?
I don't know, you tell me. What I can tell you, after reading the article, is that they were fighting not only the code itself but the different 3rd party libraries involved. I would start by looking at what people did to resolve the issue and why it resolved the issues to get the game working. (i.e. "what changed").
After assessing what it took to get the game working, I'd look at what the game was expecting, probably dynamic link libraries directly along with probably some COM interfaces.
All in all, I don't think it's rocket science, any good developer worth their salt who knows how to solve problems could figure it out. So ask them.
Edit: I should add, some of this forensic development work takes hours, if not days. I've actually spent 16 hours trying to find a GDI handle leak only because a person returned from a function prematurely before then end of the function cleaned up resources. Now how fun is that for development work, when you could be writing something new?