VOGONS

Search

Common searches

A Weird Memory Problem

Topic actions

First post, by SieBoi

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Hello there fellow.. people,

first of all i gotta say im quite new with dosbox and i got this weird problem.
im using "DOSBox SVN Daum 2015 build(not sure which one)" and i was trying few gui and ui programs. When i try to open a gui program named "GEM" i get an error that says "GEM 3.0 needs 512k or more memory. Execution terminated."

so i look up for ways to expand my memory (all of those ems,xms thingys) but noting helped. After a while checking memory come to my mind(finally) and i see that i actually had more free memory than the program needs yet it didn't work

And i realy don't think this problem is about the program.

5amAbMp.png

My configure is this (i deleted # parts because its out of sites character limit)

[sdl]
fullscreen=true
fulldouble=false
fullresolution=1920x1080
windowresolution=original
output=direct3d
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper-SVN-Daum.map
pixelshader=none
usescancodes=false
overscan=0

[log]
logfile=
vga=true
vgagfx=true
vgamisc=true
int10=true
sblaster=true
dma_control=true
fpu=true
cpu=true
paging=true
fcb=true
files=true
ioctl=true
exec=true
dosmisc=true
pit=true
keyboard=true
pic=true
mouse=true
bios=true
gui=true
misc=true
io=true
pci=true
sst=true

[dosbox]
language=
machine=svga_s3
vmemsize=8
vmemsizekb=0
captures=capture
mainline compatible mapping=true
mainline compatible bios mapping=true
adapter rom is ram=false
shell environment size=0
private area size=32768
a20=fast
isa bus clock=std8.3
pci bus clock=std33.3
rom bios allocation max=0
rom bios minimum size=0
memsize=1024
memsizekb=0
…Show last 441 lines
dos mem limit=0
isa memory hole at 512kb=false
memalias=0
vga bios size override=0
video bios dont duplicate cga first half rom font=false
video bios always offer 14-pixel high rom font=true
video bios always offer 16-pixel high rom font=true
video bios enable cga second half rom font=true
forcerate=
sierra ramdac=true
sierra ramdac lock 565=false
page flip debug line=false
vertical retrace poll debug line=false
cgasnow=true
allow port 92 reset=true
enable port 92=true
enable 1st dma controller=true
enable 2nd dma controller=true
allow dma address decrement=true
enable dma extra page registers=true
dma page registers write-only=false
enable slave pic=true
enable pc nmi mask=true
rom bios 8x8 CGA font=true
rom bios video parameter table=true
allow more than 640kb base memory=false
vesa lfb base scanline adjust=0
allow hpel effects=false
allow hretrace effects=false
hretrace effect weight=4.00
vesa vbe 1.2 modes are 32bpp=true
allow low resolution vesa modes=true
allow 32bpp vesa modes=true
allow 24bpp vesa modes=true
allow 16bpp vesa modes=true
allow 15bpp vesa modes=true
allow 8bpp vesa modes=true
allow 4bpp vesa modes=true
allow tty vesa modes=true
enable vga resize delay=false
resize only on vga active display width increase=false
enable pci bus=true
pit hack=

[render]
frameskip=0
aspect=false
linewise=false
char9=false
doublescan=false
scaler=hardware2x
autofit=true

[vsync]
vsyncmode=off
vsyncrate=75

[cpu]
core=auto
enable msr=true
ignore undefined msr=false
dynamic core cache block size=32
cputype=auto
cycles=auto
cycleup=10
cycledown=20
non-recursive page fault=false
ignore opcode 63=true
apmbios=false
apmbios allow realmode=true
apmbios allow 16-bit protected mode=true
apmbios allow 32-bit protected mode=true
integration device=false
isapnpbios=false
realbig16=false

[keyboard]
aux=false
allow output port reset=true
auxdevice=intellimouse

[pci]
voodoo=auto
voodoomem=standard

[mixer]
nosound=false
swapstereo=false
rate=44100
blocksize=1024
prebuffer=20

[midi]
mpu401=intelligent
mididevice=default
midiconfig=
mt32.reverse.stereo=off
mt32.verbose=off
mt32.thread=off
mt32.dac=auto
mt32.reverb.mode=auto
mt32.reverb.time=5
mt32.reverb.level=3
mt32.partials=32

[sblaster]
sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
sbmixer=true
oplmode=auto
adlib force timer overflow on detect=true
oplemu=default
oplrate=44100
hardwarebase=220
force dsp auto-init=false
force goldplay=false
goldplay=false
goldplay stereo=true
dsp require interrupt acknowledge=auto
dsp write busy delay=-1
blaster environment variable=true
sample rate limits=true
instant direct dac=false
stereo control with sbpro only=true
dsp busy cycle rate=-1
dsp busy cycle duty=-1
io port aliasing=true

[gus]
gus=false
gusrate=44100
gusbase=240
gusirq=5
gusdma=3
ultradir=C:\ULTRASND

[innova]
innova=false
samplerate=22050
sidbase=280
quality=0

[speaker]
pcspeaker=true
pcrate=44100
tandy=auto
tandyrate=44100
disney=false
ps1audio=off
ps1audiorate=22050

[joystick]
joysticktype=auto
timed=true
autofire=false
swap34=false
buttonwrap=false

[serial]
serial1=dummy
serial2=dummy
serial3=disabled
serial4=disabled

[printer]
printer=true
dpi=360
width=85
height=110
printoutput=png
multipage=false
docpath=.
timeout=0

[parallel]
parallel1=disabled
parallel2=disabled
parallel3=disabled
dongle=false

[glide]
glide=true
lfb=full
splash=true

[dos]
xms=true
enable a20 on windows init=true
zero memory on xms memory allocation=false
ems=true
zero memory on ems memory allocation=false
ems system handle memory size=384
umb=true
umb start=0
umb end=0
kernel allocation in umb=false
dynamic kernel allocation=false
keep umb on boot=false
keep private area on boot=false
private area in umb=true
automount=true
int33=true
int 13 extensions=true
biosps2=true
int15 mouse callback does not preserve registers=false
keyboardlayout=auto
dbcs=true
filenamechar=true
collating and uppercase=true
files=127
con device use int 16h to detect keyboard input=true
zero memory on int 21h memory allocation=false

[ipx]
ipx=false

[ne2000]
ne2000=true
nicbase=300
nicirq=3
macaddr=AC:DE:48:88:99:AA
realnic=list

[fdc, primary]
enable=false
pnp=true
irq=0
io=0
dma=-1
int13fakev86io=false
instant mode=false
auto-attach to int 13h=true
mode=ps2
chip=82077aa

[fdc, secondary]
enable=false
pnp=true
irq=0
io=0
dma=-1
int13fakev86io=false
instant mode=false
auto-attach to int 13h=true
mode=ps2
chip=82077aa

[fdc, tertiary]
enable=false
pnp=true
irq=0
io=0
dma=-1
int13fakev86io=false
instant mode=false
auto-attach to int 13h=true
mode=ps2
chip=82077aa

[fdc, quaternary]
enable=false
pnp=true
irq=0
io=0
dma=-1
int13fakev86io=false
instant mode=false
auto-attach to int 13h=true
mode=ps2
chip=82077aa

[fdc, quinternary]
enable=false
pnp=true
irq=0
io=0
dma=-1
int13fakev86io=false
instant mode=false
auto-attach to int 13h=true
mode=ps2
chip=82077aa

[fdc, sexternary]
enable=false
pnp=true
irq=0
io=0
dma=-1
int13fakev86io=false
instant mode=false
auto-attach to int 13h=true
mode=ps2
chip=82077aa

[fdc, septernary]
enable=false
pnp=true
irq=0
io=0
dma=-1
int13fakev86io=false
instant mode=false
auto-attach to int 13h=true
mode=ps2
chip=82077aa

[fdc, octernary]
enable=false
pnp=true
irq=0
io=0
dma=-1
int13fakev86io=false
instant mode=false
auto-attach to int 13h=true
mode=ps2
chip=82077aa

[ide, primary]
enable=true
pnp=true
irq=0
io=0
altio=0
int13fakeio=false
int13fakev86io=false
enable pio32=false
ignore pio32=false
cd-rom spinup time=0
cd-rom spindown timeout=0
cd-rom insertion delay=0

[ide, secondary]
enable=true
pnp=true
irq=0
io=0
altio=0
int13fakeio=false
int13fakev86io=false
enable pio32=false
ignore pio32=false
cd-rom spinup time=0
cd-rom spindown timeout=0
cd-rom insertion delay=0

[ide, tertiary]
enable=false
pnp=true
irq=0
io=0
altio=0
int13fakeio=false
int13fakev86io=false
enable pio32=false
ignore pio32=false
cd-rom spinup time=0
cd-rom spindown timeout=0
cd-rom insertion delay=0

[ide, quaternary]
enable=false
pnp=true
irq=0
io=0
altio=0
int13fakeio=false
int13fakev86io=false
enable pio32=false
ignore pio32=false
cd-rom spinup time=0
cd-rom spindown timeout=0
cd-rom insertion delay=0

[ide, quinternary]
enable=false
pnp=true
irq=0
io=0
altio=0
int13fakeio=false
int13fakev86io=false
enable pio32=false
ignore pio32=false
cd-rom spinup time=0
cd-rom spindown timeout=0
cd-rom insertion delay=0

[ide, sexternary]
enable=false
pnp=true
irq=0
io=0
altio=0
int13fakeio=false
int13fakev86io=false
enable pio32=false
ignore pio32=false
cd-rom spinup time=0
cd-rom spindown timeout=0
cd-rom insertion delay=0

[ide, septernary]
enable=false
pnp=true
irq=0
io=0
altio=0
int13fakeio=false
int13fakev86io=false
enable pio32=false
ignore pio32=false
cd-rom spinup time=0
cd-rom spindown timeout=0
cd-rom insertion delay=0

[ide, octernary]
enable=false
pnp=true
irq=0
io=0
altio=0
int13fakeio=false
int13fakev86io=false
enable pio32=false
ignore pio32=false
cd-rom spinup time=0
cd-rom spindown timeout=0
cd-rom insertion delay=0

[autoexec]

fullscreen false
mount c D:\Games\0RETRO\DOS\C -freesize 1024
C:
cls
@command.com

So what did i do wrong or what's the problem?

If this is completely normal and i just didn't realize, i am so so sorry for wasting your time and thanks a lot.

Reply 1 of 14, by Osprey

Posted on 
User metadata
Rank Member
Rank
Member

Try renaming your .conf so that it's not loaded and you're using the defaults, instead. If it works, then it's something in your .conf file. Just from a quick glance, I see that your memsize is way too high. I believe that it shouldn't be higher than 31. If that's not it, but it's definitely something in the .conf file, try replacing it with the attached one, which is a pretty vanilla one without many unnecessary settings.

If it doesn't work when your .conf file isn't loaded, then try a different DOSBox build, since Daum has some issues. Try the official v0.74 and, if that doesn't work, try one of the latest vanilla SVN builds, like the one at emucr.com. I wouldn't use your old .conf file with those, though, since yours has so many Daum-specific settings. Use my attached one, instead, which I believe has only settings that any DOSBox build would recognize.

Attachments

  • Filename
    dosbox.conf
    File size
    10.23 KiB
    Downloads
    48 downloads
    File license
    Fair use/fair dealing exception

Reply 2 of 14, by SieBoi

Posted on 
User metadata
Rank Newbie
Rank
Newbie

First of all, Osprey thank you for your response.

My .conf file actually works fine (for example) the autoexec does everything i write or the resolution i set etc. and when i make memsize 31 it actualy get lesser.

QYsy9zq.png

And i tried with original v0.74 too, it did the same thing.

j42fS9Z.png

i really don't get it why that's happening.

Reply 4 of 14, by ripsaw8080

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

Judging by directory names, you appear to be using FreeGEM/XM 3.0beta4, but so many reworked variants of the old GEM desktop GUI were made that it's hard to be sure. If this is indeed what you're trying to run in DOSBox, I was able to get it working by doing things differently than what you tried.

First, the sub-directories GEMAPPS, GEMBOOT, GEMDESK, GEMSCRAP, and GEMSYS *must* be off the root directory of the emulated drive. Perhaps this would not be necessary if the app is installed properly (i.e. not just extracted from a zip file), but I don't see a way around it.

Second, start the program with GEMVDI.EXE, which then executes GEM.EXE as a child process. Example commands that I used:

mount c c:\dos
c:
cd gemsys
gemvdi

Reply 5 of 14, by SieBoi

Posted on 
User metadata
Rank Newbie
Rank
Newbie
IIGS_User wrote:

try
lh gem.exe

("Load High").

Thank you very much but sadly that didn't work yet can you explain me or refer me a link about what "Load High" does? Looks interesting.

ripsaw8080 wrote:
Judging by directory names, you appear to be using FreeGEM/XM 3.0beta4, but so many reworked variants of the old GEM desktop GUI […]
Show full quote

Judging by directory names, you appear to be using FreeGEM/XM 3.0beta4, but so many reworked variants of the old GEM desktop GUI were made that it's hard to be sure. If this is indeed what you're trying to run in DOSBox, I was able to get it working by doing things differently than what you tried.

First, the sub-directories GEMAPPS, GEMBOOT, GEMDESK, GEMSCRAP, and GEMSYS *must* be off the root directory of the emulated drive. Perhaps this would not be necessary if the app is installed properly (i.e. not just extracted from a zip file), but I don't see a way around it.

Second, start the program with GEMVDI.EXE, which then executes GEM.EXE as a child process. Example commands that I used:

mount c c:\dos
c:
cd gemsys
gemvdi

Oh my god thank you! That worked! Also can you tell me why these must be off the root directory? You see im quite a ordinate person so those folders on root kind of irritating me.

Another thing i didn't seem to give SVN Daum more than 523,264k memory doesn't matter what i do, there is no problem with the original 0.74 when i type memsize=16 in original it gave me 15168kb which is perfect but when i type memsize=16 in Daum it gave me just 16,384k should i make a new topic for that or do you guys know the answer?

Also thank you all again!

Reply 6 of 14, by Dominus

Posted on 
User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Daum is broken and not supported here! But neither does the „author“ of Daum support it anymore.

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 7 of 14, by SieBoi

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Oh, then do you have another version/svn you can suggest me besides 0.74 that still getting supported? My main reasons to use daum was easier use, build in graphic and sound cards(simulations i might call them) and of course 1920x1080 resalution

Reply 8 of 14, by IIGS_User

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie
SieBoi wrote:

Thank you very much but sadly that didn't work yet can you explain me or refer me a link about what "Load High" does? Looks interesting.

Nice to see another hint works perfectly.

About the Loadhigh command, I found the following link:
http://www.abandonia.com/vbullet/showthread.php?t=6991

On MS-DOS, it loads drivers and commands prefixed with lh to the upper memory to let the base DOS memory (below 640k) free for DOS applications that rely on it.

Klimawandel.

Reply 9 of 14, by Osprey

Posted on 
User metadata
Rank Member
Rank
Member
SieBoi wrote:

Oh, then do you have another version/svn you can suggest me besides 0.74 that still getting supported? My main reasons to use daum was easier use, build in graphic and sound cards(simulations i might call them) and of course 1920x1080 resalution

I gave you a link above to a frequently updated plain version of DOSBox. If you want something fancier, though, google DOSBox ECE.

Reply 10 of 14, by SieBoi

Posted on 
User metadata
Rank Newbie
Rank
Newbie
IIGS_User wrote:
Nice to see another hint works perfectly. […]
Show full quote
SieBoi wrote:

Thank you very much but sadly that didn't work yet can you explain me or refer me a link about what "Load High" does? Looks interesting.

Nice to see another hint works perfectly.

About the Loadhigh command, I found the following link:
http://www.abandonia.com/vbullet/showthread.php?t=6991

On MS-DOS, it loads drivers and commands prefixed with lh to the upper memory to let the base DOS memory (below 640k) free for DOS applications that rely on it.

Gotcha thank you.

Osprey wrote:
SieBoi wrote:

Oh, then do you have another version/svn you can suggest me besides 0.74 that still getting supported? My main reasons to use daum was easier use, build in graphic and sound cards(simulations i might call them) and of course 1920x1080 resalution

I gave you a link above to a frequently updated plain version of DOSBox. If you want something fancier, though, google DOSBox ECE.

Trying DOSBox ECE i hope it goes well. Also does it get support from this site?

Also another question hit me when i was looking at web, some people says "PCEM is better" and they mostly talk about windows/opengl games/graphical stuff, im quite happy with dosbox because i only use dos with basic managers (like Norton Commander) and play some older games like dave, mario & luigi so is there actualy an advantage for using PCEM (so far i didnt saw any)?

Reply 11 of 14, by SieBoi

Posted on 
User metadata
Rank Newbie
Rank
Newbie
SieBoi wrote:

Also another question hit me when i was looking at web, some people says "PCEM is better" and they mostly talk about windows/opengl games/graphical stuff, im quite happy with dosbox because i only use dos with basic managers (like Norton Commander) and play some older games like dave, mario & luigi so is there actualy an advantage for using PCEM (so far i didnt saw any)?

Did i asked a realy taboo question?

Osprey wrote:
SieBoi wrote:

Oh, then do you have another version/svn you can suggest me besides 0.74 that still getting supported? My main reasons to use daum was easier use, build in graphic and sound cards(simulations i might call them) and of course 1920x1080 resalution

I gave you a link above to a frequently updated plain version of DOSBox. If you want something fancier, though, google DOSBox ECE.

Sadly ECE also doesnt support 1920x1080 and i have quite an obsession with empty black parts on my screen.

Reply 12 of 14, by SieBoi

Posted on 
User metadata
Rank Newbie
Rank
Newbie
Dominus wrote:

Daum is broken and not supported here! But neither does the „author“ of Daum support it anymore.

Can you tell me what is broken with daum? So far i only get this memory thing but i want to know if its extremely broken if not i think i can deal with it.

Reply 13 of 14, by Osprey

Posted on 
User metadata
Rank Member
Rank
Member
SieBoi wrote:

Sadly ECE also doesnt support 1920x1080 and i have quite an obsession with empty black parts on my screen.

I'm not sure what you mean. As far as I know, DOSBox (any build) "supports" any resolution, at least in fullscreen and if you're using an output mode that scales (anything but "surface"). Have you changed your output mode from "direct3d" to something else? That mode is not recognized by most DOSBox builds, which could be your problem. Change it to overlay, ddraw or opengl. Also, if your desktop resolution is 1920x1080, you can simply set "fullresolution=desktop".

Reply 14 of 14, by SieBoi

Posted on 
User metadata
Rank Newbie
Rank
Newbie
Osprey wrote:
SieBoi wrote:

Sadly ECE also doesnt support 1920x1080 and i have quite an obsession with empty black parts on my screen.

I'm not sure what you mean. As far as I know, DOSBox (any build) "supports" any resolution, at least in fullscreen and if you're using an output mode that scales (anything but "surface"). Have you changed your output mode from "direct3d" to something else? That mode is not recognized by most DOSBox builds, which could be your problem. Change it to overlay, ddraw or opengl. Also, if your desktop resolution is 1920x1080, you can simply set "fullresolution=desktop".

Yyep i allready tried every solition on internet (yours as well) but noting is working. So wait you saying this isnt the normal case? Because to many people get this problem as well on web.

Go to top of page Go to top of page
Back to DOSBox General
Close window
Close window