[reader50]

If you have a 2nd monitor, try this:

Leave 'top' running on the 2nd monitor. The demo does not blank the 2nd monitor (at least not when it's on a different vid card), so you can monitor what is happening while the game runs.

Note that a new process called 'wineserver' starts up after the game launches. It quits when the game quits too, so I could not get a good look at it other than what showed in 'top'. It didn't use too much CPU.

Is it possible that they ported WINE internally to ease the game port? Last time I checked a few months ago, WINE had a lot of internal endian issues that were expected to take a while to sort out. Also, an x86 emulator would need to be used for binary executable passthroughs.

This hardly seems likely, but if they did port WINE, it would be seriously interesting.

[eyadams]

Is it possible that they ported WINE internally to ease the game port?

More likely they used WineLib - a library that is part of the Wine project that lets developers of Win32 applications port their application to Unix systems. WineServer is an application used by Wine that mimics some of the functionality of the Windows kernel.

According to the WineLib documentation, support on non-i386 CPUs is spotty; it is conceivable that the developers of Indiana Jones cleaned it up just enough to run under PowerPC. This raises an interesting question: if they have used software from the Wine project, and made changes, then the license for the Wine project may require them to make the source of their changes available to anyone who asks. This is thanks to the GNU Lesser General Public License, under which Wine (and WineLib) are released. Or it may not - I'm not 100% sure what the differences between the GNU License and the Lesser GNU License are.

[reader50]

Check out the bundle contents of the demo. There are a bunch of WINE files, and two WINE license files.

Something definitely got ported.