VOGONS


First post, by TeaRex

User metadata
Rank Member
Rank
Member

Hello all,

I compile DOSBox from CVS fairly regularly. My local copy of the CVS is unmodified except for the VGA font bitmaps in src/ints/int10_memory.cpp and I compile without any options to configure. My system is a 64-bit openSUSE 10.3 with Nvidia 7600GS card and 169.09 drivers (though I doubt that this has to do with the problem).

Anyway, the problem manifests in several ways. First, the dosbox.conf created with "config -writeconf dosbox.conf" is missing all the explanatory messages. I've attached the file so you can see it, but basically it goes like this throughout:

[render]
# Message not Found!

frameskip=0
aspect=false
scaler=none

[cpu]
# Message not Found!

core=dynamic
cycles=80000
cycleup=500
cycledown=500

[mixer]
# Message not Found!

nosound=false
rate=48000
blocksize=2048
prebuffer=5

Secondly, DOSBox acts strangely on startup; I get this message which seems to be related to the "cycles=" line:

DOSBox version 0.72
Copyright 2002-2007 DOSBox Team, published under GNU GPL.
---
CONFIG:Loading primary settings from config file dosbox.conf
"80000" is not a valid value for variable: type.
It might now be reset it to default value: auto
MIDI:Opened device:none
Using joystick Analog 2-axis 4-button joystick with 2 axes, 4 buttons and 0 hat(s)

thirdly, I can't get stuff with config -get. For example if I say:

config -get "cpu core"

I get the answer:

There is no property core in section cpu.

However, when there REALLY is no property of that name, like in:

config -get "cpu corx"

Then the answer is instead:

PROP_NOT_EXIST

All of this seems to have started at the time of the recent setup patches. Is this simply expected behavior at this point that will be fixed later, or have I hit a hitherto-unknown bug?

I should add that all the normal emulation functionality of DOSBox is there and works very well.

I'll give the result of "ldd $(which dosbox)" here if that helps with library versions. Thanks you for your consideration!

        libSDL_sound-1.0.so.1 => /usr/lib64/libSDL_sound-1.0.so.1 (0x00002ac4bd80a000)
libasound.so.2 => /usr/lib64/libasound.so.2 (0x00002ac4bda51000)
libdl.so.2 => /lib64/libdl.so.2 (0x00002ac4bdd24000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00002ac4bdf29000)
libSDL-1.2.so.0 => /usr/lib64/libSDL-1.2.so.0 (0x00002ac4be144000)
libpng12.so.0 => /usr/lib64/libpng12.so.0 (0x00002ac4be3dd000)
libz.so.1 => /lib64/libz.so.1 (0x00002ac4be604000)
libSDL_net-1.2.so.0 => /usr/lib64/libSDL_net-1.2.so.0 (0x00002ac4be819000)
libGL.so.1 => /usr/lib64/libGL.so.1 (0x00002ac4bea1e000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002ac4bebed000)
libm.so.6 => /lib64/libm.so.6 (0x00002ac4beef5000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002ac4bf148000)
libc.so.6 => /lib64/libc.so.6 (0x00002ac4bf357000)
libaa.so.1 => /usr/lib64/libaa.so.1 (0x00002ac4bf69c000)
libncurses.so.5 => /lib64/libncurses.so.5 (0x00002ac4bf8bb000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00002ac4bfb00000)
libxcb-xlib.so.0 => /usr/lib64/libxcb-xlib.so.0 (0x00002ac4bfe36000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00002ac4c0038000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00002ac4c0255000)
libgpm.so.1 => /usr/lib64/libgpm.so.1 (0x00002ac4c0458000)
libsmpeg-0.4.so.0 => /usr/lib64/libsmpeg-0.4.so.0 (0x00002ac4c065e000)
libmikmod.so.2 => /usr/lib64/libmikmod.so.2 (0x00002ac4c08bb000)
libaudiofile.so.0 => /usr/lib64/libaudiofile.so.0 (0x00002ac4c0b09000)
libvorbis.so.0 => /usr/lib64/libvorbis.so.0 (0x00002ac4c0d31000)
libvorbisfile.so.3 => /usr/lib64/libvorbisfile.so.3 (0x00002ac4c0f60000)
libvorbisenc.so.2 => /usr/lib64/libvorbisenc.so.2 (0x00002ac4c1168000)
/lib64/ld-linux-x86-64.so.2 (0x00002ac4bd5ed000)
libGLcore.so.1 => /usr/lib64/libGLcore.so.1 (0x00002ac4c1543000)
libnvidia-tls.so.1 => /usr/lib64/tls/libnvidia-tls.so.1 (0x00002ac4c20fb000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00002ac4c21fc000)
libogg.so.0 => /usr/lib64/libogg.so.0 (0x00002ac4c240e000)

tearex

Reply 1 of 9, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

don't use the cvs then

Reply 2 of 9, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

the options got changed.
create a new configuration file. (fixed 3000)
the messages will be restored oneday

The Prop_not_exist is a funny one. I thought I had hidden that message

Water flows down the stream
How to ask questions the smart way!

Reply 3 of 9, by TeaRex

User metadata
Rank Member
Rank
Member
wd wrote:

don't use the cvs then

I wasn't complaining at all wd, just reporting it in case it could be helpful for you. I'm aware that CVS stuff is work in progress. Boy are you touchy.

Last edited by TeaRex on 2008-03-01, 15:33. Edited 1 time in total.

tearex

Reply 4 of 9, by TeaRex

User metadata
Rank Member
Rank
Member

Thanks a lot Qbix, I will try recreating the file.

Qbix wrote:

(fixed 3000)

I'm a bit dense here, what do you mean by that?

tearex

Reply 5 of 9, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

that is the line you want on the cycles part.

Water flows down the stream
How to ask questions the smart way!

Reply 6 of 9, by TeaRex

User metadata
Rank Member
Rank
Member

Ok, thanks.

tearex

Reply 7 of 9, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Boy are you touchy.

Yeah!

Reply 8 of 9, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author
thirdly, I can't get stuff with config -get. For example if I say: […]
Show full quote

thirdly, I can't get stuff with config -get. For example if I say:

config -get "cpu core"

I get the answer:

There is no property core in section cpu.

However, when there REALLY is no property of that name, like in:

config -get "cpu corx"

Then the answer is instead:

PROP_NOT_EXIST

Probably a real bug. Specifying it out to make that clear.

Water flows down the stream
How to ask questions the smart way!