Two open source libraries from John Miles page are needed (AIL and VFX). Go to http://www.thegleam.com/ke5fx/ to download them.
After compiling the project ARUN.EXE is created, rename it to INTERP.EXE - this is the interpreter.
How to use it:
a) Copy EOB 3 files into a directory
b) Convert EYE.RES for the AESOP/32 (using the DAESOP utilitity - see the previous posts and DAESOP README.TXT)
c) Copy files from RUNTIME.ZIP to the same directory (overwrite)
d) Copy the new INTERP.EXE to the same directory (overwrite)
e) Copy MCGA.DLL (from VFX library) and sound DLLs (from AIL library) to the same directory (overwrite)
f) Start DOSBOX
g) Configure the game
h) Run the game
Yesterday I received some nice things from John Miles. I did not check it in detail yet, but it looks like complete sources for AESOP/32 compiler and documentation.
There is no runtime interpreter (too much SSI copyrighted things), though I think that interpreters from EOB 3/Bungeon Hack *may* be usefull (I did not check)...
John Miles explicitly permitted to use it without any restrictions (he owns the copyright). See below.
Just one comment to the quote below: as far as I know 32bit version of AESOP never shipped... Or has anyone seen it? It should be recognizable by using extender (DOS4GW). John Miles made it as patch for EOB 3 (fixing slowdowns) and submitted to SSI. My guess is that it never gort further... If you know anything else I would welcome the information...
We did try to make the code as reusable as possible, with the
goal of not only shipping multiple games with the same engine,
but making the engine usable by less-technical artists and scripters.
If you reinvent the engine every game, the game
authors never get a chance to master the technology.
Here's the 32-bit compiler and manual; looking at arcmsg.h, it
appears we still called it "AESOP/16," because the bytecode
interpreter used 16-bit native words. I don't know if the
version of AESOP you have is the 32-bit DOS4GW-based one or not,
but they were very similar.
I own the copyright to the AESOP package itself, and as far as
I'm concerned, it can be considered public-domain. You can do
anything you want with it, forward it to Michael, post it online,
upload it to a warez site, whatever. Happy I did remove the
runtime interpreter code, though, because it would be way too
much work to separate my own code from the parts that are owned
by SSI's corporate heirs.