Oh I forgot, I use 0.63, Windows XP.

Seems to work fine in the CVS as far as i understood
the gameplay. See the dev forum where to get a cvs build.

If it still doesn't work, please give more details about
what exactly does not work and how to test it easily.

I tried the latest official dev build but didn't work, worth noting is I have a patched version, more recent than the HOTU one, but I had probs with the HOTU one too.

Exactly what it does is.
There're several different exes the game uses when switching between different things, whenever DosBOX tries to access one of these exes other than the main one, it crashes, it seems that DosBOX can't access'em at all, not only ingame, but also when I try to install the game using DosBOX, it specifically tells me "Can't read xxx.exe".

To replicate this problem, just get -removed- this, and get the manual off Home Of The Underdogs(It's not cracked so you need to answer copy protection systems)

When you start your first flight in space, click S, to go to the Security screen.

There, press D to access the internal Defense screen, as this switches to another exe, in my DosBOX, this first freezes up DosBOX, then crashes it, I've tried all different cores also, such as simple, normal, full, dynamic, none solved the problem.

If you get it to work, please do tell me what CVS you used.

Please don't link/upload any games, i removed it
(used a different version for testing anyways).

Thanks for your explanation, you're right one of the
executables doesn't work (though the switching between
.exes works correctly).
They revector one interrupt (int1c) to its default bios
rom location, for whatever reason. As dosbox does not
contain a bios in that area, it'll execute rubbish.

If you can compile the dosbox sources yourself, i can
post a modification to make the game work.

Well wd, that link was to the designer, who owns all copyright to its, official website, so it ain't illegal if that's what you're implying, basically he has made it fully freeware.

I'd also really like to compile the DosBOX sources and do a modification, but sadly I have no experience with that, I guess I could always try tho, again, thanks for the help.

About that default bios rom location thing.. Is that something that you think should go in as a fix to dosbox? It seems like it should improve compatibility.

In a possibly separate issue, I've occasionally seen errors upon interrupt revectoring which I'm sometimes able to pass by running with dynamic core. This is probably a different thing, but I'll mention it just in case it's the same.

As I already wrote in one of my posts "I've tried all different cores also, such as simple, normal, full, dynamic, none solved the problem."´
Thanks for the tip anyway.😀

They set int1c to a fixed location, which has an iret on most bioses.
I'll add the iret at that place i think, as i've seen this several times now.