Tried it with EmuTOS under Hatari TT & Falcon emulations. Works fine and I like the MIDI music!
(For those using Hatari on OSX or Windows instead of Linux, Latest Hatari version supports now MIDI output also on OSX & Windows.)
I had basic GEMDOS tracing enabled while starting the game ("--trace os_base"), and couldn't help noticing that the game:
- Opens & closes same files many times, although all relevant file content should fit into RAM (14+64MB)
- In the startup menu screen, does constantly this (the opened file was created by the game, and empty):
Code: Select all
GEMDOS 0x3D Fopen("SAVES\ONETIME.DAT", read-only) at PC=0xFA002A
-> FD 65 (read-only -> read-only)
GEMDOS 0x3E Fclose(65) at PC 0xFA002A
As a result, most of the cycles in the startup menu are used by File_Exists_Ex() and things that it calls (File_Open() etc).
When the actual game is running, gui/viewport.c code takes a surprising amount if cycles.
PS. I like that the binaries aren't stripped so that they can be profiled & debugged in Hatari.