after last upgrade with zypper dup the dosemu stop to work
first time i get:
LOWRAM mmap: Argumento inválido
This message disappear when i do:
echo 0 > /proc/sys/vm/mmap_min_addr (as root of course)
After that
Dosemu exit without any answer and without any message on /var/log/messages.
inside of ~/.dosemu/boot.log the file say exit called (of course i never call the leavedos)
Compiled with GCC version 9.2.1 -m64
WARN: vm86plus service not available in your kernel
WARN: using CPU emulation for vm86()
CONF: reserving 640Kb at 0x00000 for 'd' (Base DOS memory (first 640K))
CONF: reserving 48Kb at 0xF4000 for 'r' (Dosemu reserved area)
CONF: reserving 128Kb at 0xA0000 for 'v' (Video memory)
leavedos(47|0x2f) called - shutting down
When i activate all debugs flags i get some data:
dosemu -D +#CEMQSWZcehjmpruwADIPRTXadgiknqsvx
MAPPING: map success, cap= HMA, addr=0xffffffffffffffff
HMA: Mapping HMA to HMAAREA 0x100000 unsuccessful: Argumento inválido
leavedos(47|0x2f) called - shutting down
I have one clue, but i dont know how fix that, any help will be greatly appreciated
You should probably just submit a bug…
I’d be purely speculating that “HMA” likely references some kind of “High Memory Address” so a value may be necessary… If so and the the code doesn’t internally specify a default value, setting it to zero probably won’t work (Would have been a good try if the value was a boolean yes/no instead).
You can do an Internet search for “dosemu hma” which will return many hits but I don’t know that anything would likely be an answer to your situation.
Something to try…
First try retrieving the current value of what you’re trying to set so you know what value is there when your app fails…
cat /proc/sys/vm/mmap_min_addr
Instead of “echo 0” inserting a zero value maybe try inserting a null value with two single quotes…
eg and that’s two single quotes, not a double quote
echo '' > /proc/sys/vm/mmap_min_addr
Am assuming that forcing a null value <might> cause a default value to be used. Or, a null value could “just work”
Also FYI —
You can also implement your kernel configuration commands in a sysctl command instead of writing directly to /proc
The diff is that writing to /proc can fail and cause dire consequences whereas if implemented by a sysctl command, if the command is bad then the system will ignore the command.
I described this in the following I wrote long ago for a different use, but the methods are the same as what you are trying to do