It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hi,

I'm at the mirror fight, right at the end of the game. The first time I got to the fight, I could fight normally, but an invisible enemy with a garbled name was present in the fight. As I lost, I tried fighting again, but the game crashes immediately as the fight starts, with the error "memory allocation of a -251658136 Byte bloc failed! file:p:\riva\source\cpp\face2.cpp, line 241".

Has anyone run into similar problems? Does anyone know a fix or a workaround (avoiding the fight, etc.?
This question / problem has been solved by patricklibudaimage
avatar
Bakusson: Hi,

I'm at the mirror fight, right at the end of the game. The first time I got to the fight, I could fight normally, but an invisible enemy with a garbled name was present in the fight. As I lost, I tried fighting again, but the game crashes immediately as the fight starts, with the error "memory allocation of a -251658136 Byte bloc failed! file:p:\riva\source\cpp\face2.cpp, line 241".

Has anyone run into similar problems? Does anyone know a fix or a workaround (avoiding the fight, etc.?
I have similar error and same problem. I wasn't even able to fight and got error immediately.
ERROR:
memory allocation of a -268431256 Byte block failed!
file:p:\riva\source\cpp\face2.cpp, line 241
Post edited January 28, 2014 by Martymer
avatar
Bakusson: Hi,

I'm at the mirror fight, right at the end of the game. The first time I got to the fight, I could fight normally, but an invisible enemy with a garbled name was present in the fight. As I lost, I tried fighting again, but the game crashes immediately as the fight starts, with the error "memory allocation of a -251658136 Byte bloc failed! file:p:\riva\source\cpp\face2.cpp, line 241".

Has anyone run into similar problems? Does anyone know a fix or a workaround (avoiding the fight, etc.?
Hi,

This is a classic - RoA3 has the impertinence to use DPMI that (and apparently only that !!!) particular moment, which DOSBox does not support out of the box so-to-speak. One way to get round it is to use JEMMEX (http://www.freedos.org/software/?prog=jemm386 - click on: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/emm386/jemm386 - download JEMM578B.ZIP - and unpack the archive to a directory of your choice) copy the file JEMMEX.EXE to the RoA3 directory and incorporate it into your RoA3 DOSBox config file.

file "dosbox_realms3_single.conf"

cls
jemmex load noems
RIVA
exit

instead of

cls
RIVA
exit

Apart from that, also change the following lines as well in your file "dosbox_realms3.conf":

xms=false
ems=false
umb=false
keyboardlayout=gr (important if you happen to be using the German version of RoA3!)

Then it should work.


Cheers
Patrick

P.S.:

The aforementioned link no longer works and the following appears to be a backup:

http://ftp.lyx.org/pub/freedos/files/dos/himem/jemm386/
Post edited May 01, 2015 by patricklibuda
Thanks you o saviour!

I thought I will have to watch the ending on youtube but your tips worked like a charm!!
Almost 4 years later and it still saves people's games :)

Thank you for sharing!
Post edited November 26, 2017 by Fishman
avatar
Fishman: Thanks you o saviour!

I thought I will have to watch the ending on youtube but your tips worked like a charm!!
Almost 4 years later and it still saves people's games :)

Thank you for sharing!
Hi,

Apparently, these days the GOG version has alternative shortcuts that include an according configuration.


Cheers
avatar
Fishman: Thanks you o saviour!

I thought I will have to watch the ending on youtube but your tips worked like a charm!!
Almost 4 years later and it still saves people's games :)

Thank you for sharing!
avatar
patricklibuda: Hi,

Apparently, these days the GOG version has alternative shortcuts that include an according configuration.

Cheers
You seems to be right, I just checked on WIndows and the JEMM exec is included in it.
The problem seems to be that I was playing the game on macOS and this wasn't the case! A bit of an overlooking from Gog.com team I guess....

Thanks