Sorry I do not have this game but I do find your question quite funny! 😁

What exactly is the problem with the game?

Sounds like it dun run, DosFreak. 😜

I get "not enough EMS available to run".

If I increase EMS on the shortcut Memory properties, I get "needs 590k base memory to run", an error that persists no matter what I choose for the Conventional Memory value.

Any help would be appreciated.

TIA,
Binary

Is it an old game ? (I think so as this is VOGONS)

And uses it protected mode ?

You can find out if it has dosgw in its directory.
But I don't think so as it uses EMS
That wouldn't be logical. 🙄

So actually I'm asking to tell some more information about the game.

Yeah, this is an old game, from 1994:

http://www.the-underdogs.org/game.php?name=Goal%21

Doesn't use dos4gw, obviously 😀

Any help you could give me would be tremendously appreciated

TIA
Binary

Not a whole lot of testing so far, but I was able to start it up by simply right-clicking on CDGO.BAT with "Run with VDMS" (with or without the musical note). With this hacked version, I can't seem to get to the actual point of playing as it (apparently) is waiting for a joystick fire button to be pressed (none hooked up to my PC). Trying to access "ACTION REPLAYS" crashed with the following error:
Ex:9001H

Memory allocation error
Cannot load COMMAND, system halted,
so I suspect there may be other "issues" with this title.

If that's not working for you, I would suspect that it's related to your motherboard's hardware, as in these threads:

showthread.php?threadid=513
showthread.php?threadid=162

You might also try DosBox at http://dosbox.zophar.net/
as a way of getting around the EMS problem.

In v0.56, I was able to get as far into GOAL as with VDMSound (and ACTION REPLAYS didn't cause a crash). One thing I did notice however, no audio (v0.55 had fine audio, but no mouse).

BTW, it's easier to help troubleshoot these things when you follow the posting guidelines (at the top of each forum) and give us the tech info on your system. For example, if you had a motherboard that had been previously identified as an "EMS memory eater", we would've known the source of the problem on your first post.