VOGONS

Common searches


First post, by g0r3

User metadata
Rank Newbie
Rank
Newbie

Hello,

after upgrading my rig from a Core 2 Duo E8400 to an i5 6600k and from Windows 7 to Windows 10 i got some issues with Dosbox.

Shadow Warrior for example got flickering rows at the bottom of the Main Menu.
Quake 1 got messed up game physics, sometimes the characters and enemies are way to fast.

Already tried:
change "output" from surface to opengl, openglnb, ddraw
change "core" from auto to dynamic
change "cputype" from auto to pentium_slow
change "cycles" from auto to a fixed setting

didn't do the trick so far.
some hints would be much appreciated!

thx in advance and best regards,
g0r3

Reply 1 of 9, by Jorpho

User metadata
Rank l33t++
Rank
l33t++

There is no reason for such specific behaviors to change if you are running the same versions of the games with the same version of DOSBox. Are you still using the same old version you were using in Windows 7?

I should add that there are almost certainly better ways to run specifically Shadow Warrior and Quake 1 rather than resorting to DOSBox.

Reply 2 of 9, by g0r3

User metadata
Rank Newbie
Rank
Newbie

Thanks for your reply!
I am still using the same version of DOSBox on the new System as under Windows 7, it's standard 0.74 without a Frontend etc.

In the meantime i tried some options.
A higher resolution lessens the strange behavior on Quake a bit. Looks like it depends on the FPS.

Sure, there are better ways for these games but i like the DOSBox way. 😀
Mounting the original game CD and enjoy the music etc.

Reply 3 of 9, by g0r3

User metadata
Rank Newbie
Rank
Newbie

I found a few possible solutions in the meantime.
But a different Question came up.

When i start DOSBox and change parts of the config in the command line, they have no impact.
e.g. starting up DOSBox, in the .conf file is specified "machine=svga_s3"
i type "machine=vesa_nolfb" in the command line and check the result with typing "machine" again.
after starting up the programm in DOSBox, that needs vesa_nolfb, i have still flickering.

Changing the setting in the .conf file and starting a fresh DOSBox works.

Is there a way to change settings on the fly?

sorry for the double post!

Reply 4 of 9, by VileR

User metadata
Rank l33t
Rank
l33t

A lot of settings can be changed on the fly, but not the machine type. With 0.74 there's not much you can do, but more recent builds would at least let you type "config -r -machine=whatever" to restart DOSBox with that parameter.

[ WEB ] - [ BLOG ] - [ TUBE ] - [ CODE ]

Reply 5 of 9, by g0r3

User metadata
Rank Newbie
Rank
Newbie

Thanks for the hint, that sounds exactly what i am looking for! 😀
I tried the following SVN Builds, r3991, DAUM, DosBox-X unfortunately it didn't work on these.
DOSBox gets restarted and keeps the setting from the .conf file.

Tried also different spellings:
config -r -machine=vesa_nolfb
config -r -set "machine=vesa_nolfb"

For now i did a little workaround with a .bat File:
machine=vesa_nolfb
config -writeconf
config -r

Reply 7 of 9, by g0r3

User metadata
Rank Newbie
Rank
Newbie

Thank you, that works!

Do you know a way, to automaticaly call a specific .bat File after the restart?
Something like this:
"config -r -machine vesa_nolfb -autoexec start.bat"

Actually i try to get a workaround again according the Wiki with -writeconf (http://www.dosbox.com/wiki/CONFIG)
But i am not able to access the [autoexec] section.

Reply 8 of 9, by VileR

User metadata
Rank l33t
Rank
l33t

With "config -r" the parameters that follow the "-r" are identical to what you'd give DOSBOX.EXE when you run it from the host. So you can use "-c" to accomplish that:

config -r -machine vesa_nolfb -c start.bat

(note that "start.bat" will be executed *after* whatever appears in the [autoexec] section)

[ WEB ] - [ BLOG ] - [ TUBE ] - [ CODE ]

Reply 9 of 9, by g0r3

User metadata
Rank Newbie
Rank
Newbie

Thanks again, works like a charm now!

You are the man.gif
Filename
You are the man.gif
File size
11.61 KiB
Views
619 views
File license
Fair use/fair dealing exception

Had some troubles to get it working, because in my .conf [autoexec] section is already a .bat file:

[autoexec]
mount C E:\DOSBox\System\ -freesize 1000
mount D G:\ -t cdrom -usecd 1 -ioctl
set path=Z:\;C:\Tools\
C:
start1.bat

when i try to restart with different parameters

config -r -machine vesa_nolfb -c start2.bat

start2.bat is ignored.

after i deleted start1.bat from the [autoexec] section it worked.
i integrated the start1.bat in the desktop shortcut of dosbox for the initial start.