VOGONS


First post, by versus

User metadata
Rank Newbie
Rank
Newbie

hi!

i'm having a little problem with freddy pharkas. it seems that the "ingame time" is running too fast, which makes timed puzzles like the "horse flatulence" thing a little difficult.

i already know how to solve the horse puzzle so i was basically pretty quick in collecting the stuff i needed. when i was about to light the test sample i took, the old guy appreared telling me how i was too slow and everybody in town suffocated. i can't remember exactly how this behaved in "real dos" back then but i'm pretty sure you should have SOME time to actually solve the puzzle.

i tried it with 0.72 and the latest cvs which gave the same results. messing with the cycles also seems to have little impact.

does anybody have the same problem or even better found a workaround?

my specs:

amd athlon 64 x2 4400+
2gb ram
sb x-fi xtreme music
win xp sp2

here is my dosbox.conf

# This is the configurationfile for DOSBox . # Lines starting with a # are commentlines. # They are used to (briefly) document t […]
Show full quote

# This is the configurationfile for DOSBox .
# Lines starting with a # are commentlines.
# They are used to (briefly) document the effect of each option.

[sdl]
# fullscreen: Start dosbox directly in fullscreen.
# fulldouble: Use double buffering in fullscreen.
# fullresolution: What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
# windowresolution: Scale the window to this size IF the output device supports hardware scaling.
# output: What video system to use for output.
# Possible values: surface, overlay, opengl, openglnb, ddraw
# autolock: Mouse will automatically lock, if you click on the screen.
# sensitivity: Mouse sensitivity.
# waitonerror: Wait before closing the console if dosbox has an error.
# priority: Priority levels for dosbox. Second entry behind the comma is for when dosbox is not focused/minimized. (pause is only valid for the second entry)
# Possible values: lowest, lower, normal, higher, highest, pause
# mapperfile: File used to load/save the key/event mappings from.
# usescancodes: Avoid usage of symkeys, might not work on all operating systems.

fullscreen=false
fulldouble=true
fullresolution=desktop
windowresolution=original
output=overlay
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper.txt
usescancodes=true

[dosbox]
# language: Select another language file.
# machine: The type of machine tries to emulate.
# Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe
# captures: Directory where things like wave, midi, screenshot get captured.
# memsize: Amount of memory DOSBox has in megabytes.

language=
machine=svga_s3
captures=capture
memsize=16

[render]
# frameskip: How many frames DOSBox skips before drawing one.
# aspect: Do aspect correction, if your output method doesn't support scaling this can slow things down!.
# scaler: Scaler used to enlarge/enhance low resolution modes. If 'forced' is appended,the scaler will be used even if the result might not be desired.
# Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x

frameskip=0
aspect=true
scaler=normal3x

[cpu]
# core: CPU Core used in emulation. auto will switch to dynamic if available and appropriate.
# Possible values: auto, dynamic, normal, simple
# cputype: CPU Type used in emulation. auto is the fastest choice.
# Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch
# cycles: Amount of instructions DOSBox tries to emulate each millisecond. Setting this value too high results in sound dropouts and lags. Cycles can be set in 3 ways:
# 'auto' tries to guess what a game needs.
# It usually works, but can fail for certain games.
# 'fixed #number' will set a fixed amount of cycles. This is what you usually need if 'auto' fails.
# (Example: fixed 4000)
# 'max' will allocate as much cycles as your computer is able to handle
#
# Possible values: auto, fixed, max
# cycleup: Amount of cycles to increase/decrease with keycombo.
# cycledown: Setting it lower than 100 will be a percentage.

core=auto
cputype=386
cycles=auto
cycleup=1000
cycledown=500

[mixer]
# nosound: Enable silent mode, sound is still emulated though.
# rate: Mixer sample rate, setting any devices higher than this will probably lower their sound quality.
# Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000
# blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged.
# Possible values: 2048, 4096, 8192, 1024, 512, 256
# prebuffer: How many milliseconds of data to keep on top of the blocksize.

nosound=false
rate=44100
blocksize=2048
prebuffer=10

[midi]
# mpu401: Type of MPU-401 to emulate.
# Possible values: intelligent, uart, none
# device: Device that will receive the MIDI data from MPU-401.
# Possible values: default, win32, alsa, oss, coreaudio, coremidi, none
# config: Special configuration options for the device driver. This is usually the id of the device you want to use. See README for details.

mpu401=intelligent
device=default
config=

[sblaster]
# sbtype: Type of sblaster to emulate.
# Possible values: sb1, sb2, sbpro1, sbpro2, sb16, none
# sbbase: The IO address of the soundblaster.
# Possible values: 220, 240, 260, 280, 2a0, 2c0, 2e0, 300
# irq: The IRQ number of the soundblaster.
# Possible values: 7, 5, 3, 9, 10, 11, 12
# dma: The DMA number of the soundblaster.
# Possible values: 1, 5, 0, 3, 6, 7
# hdma: The High DMA number of the soundblaster.
# Possible values: 1, 5, 0, 3, 6, 7
# mixer: Allow the soundblaster mixer to modify the DOSBox mixer.
# oplmode: Type of OPL emulation. On 'auto' the mode is determined by sblaster type. All OPL modes are Adlib-compatible, except for 'cms'.
# Possible values: auto, cms, opl2, dualopl2, opl3, none
# oplrate: Sample rate of OPL music emulation.
# Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000

sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
mixer=true
oplmode=auto
oplrate=44100

[gus]
# gus: Enable the Gravis Ultrasound emulation.
# gusrate: Sample rate of Ultrasound emulation.
# Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000
# gusbase: The IO addresses of the Gravis Ultrasound.
# Possible values: 220, 240, 260, 280, 2a0, 2c0, 2e0, 300
# irq1: The first IRQ number of the Gravis Ultrasound. (Same IRQs are OK.)
# Possible values: 3, 5, 7, 9, 10, 11, 12
# irq2: The second IRQ number of the Gravis Ultrasound. (Same IRQs are OK.)
# Possible values: 3, 5, 7, 9, 10, 11, 12
# dma1: The first DMA addresses of the Gravis Ultrasound. (Same DMAs are OK.)
# Possible values: 0, 1, 3, 5, 6, 7
# dma2: The second DMA addresses of the Gravis Ultrasound. (Same DMAs are OK.)
# Possible values: 0, 1, 3, 5, 6, 7
# ultradir: Path to Ultrasound directory. In this directory
# there should be a MIDI directory that contains
# the patch files for GUS playback. Patch sets used
# with Timidity should work fine.

gus=false
gusrate=44100
gusbase=240
irq1=5
irq2=5
dma1=3
dma2=3
ultradir=C:\ULTRASND

[speaker]
# pcspeaker: Enable PC-Speaker emulation.
# pcrate: Sample rate of the PC-Speaker sound generation.
# Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000
# tandy: Enable Tandy Sound System emulation. For 'auto', emulation is present only if machine is set to 'tandy'.
# Possible values: auto, on, off
# tandyrate: Sample rate of the Tandy 3-Voice generation.
# Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000
# disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible).

pcspeaker=true
pcrate=22050
tandy=auto
tandyrate=22050
disney=false

[joystick]
# joysticktype: Type of joystick to emulate: auto (default), none,
# 2axis (supports two joysticks),
# 4axis (supports one joystick, first joystick used),
# 4axis_2 (supports one joystick, second joystick used),
# fcs (Thrustmaster), ch (CH Flightstick).
# none disables joystick emulation.
# auto chooses emulation depending on real joystick(s).
# Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none
# timed: enable timed intervals for axis. (false is old style behaviour).
# autofire: continuously fires as long as you keep the button pressed.
# swap34: swap the 3rd and the 4th axis. can be useful for certain joysticks.
# buttonwrap: enable button wrapping at the number of emulated buttons.

joysticktype=2axis
timed=true
autofire=false
swap34=false
buttonwrap=true

[serial]
# serial1: set type of device connected to com port.
# Can be disabled, dummy, modem, nullmodem, directserial.
# Additional parameters must be in the same line in the form of
# parameter:value. Parameter for all types is irq.
# for directserial: realport (required), rxdelay (optional).
# (realport:COM1 realport:ttyS0).
# for modem: listenport (optional).
# for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
# transparent, port, inhsocket (all optional).
# Example: serial1=modem listenport:5000
# Possible values: dummy, disabled, modem, nullmodem, directserial
# serial2: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial
# serial3: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial
# serial4: see serial1
# Possible values: dummy, disabled, modem, nullmodem, directserial

serial1=dummy
serial2=dummy
serial3=disabled
serial4=disabled

[dos]
# xms: Enable XMS support.
# ems: Enable EMS support.
# umb: Enable UMB support.
# keyboardlayout: Language code of the keyboard layout (or none).

xms=true
ems=true
umb=true
keyboardlayout=gr

[autoexec]
# Lines in this section will be run at startup.

@echo off
mount c d:\games\dos -freesize 1024
mount d f:\ -t cdrom
mount e g:\ -t cdrom
mount f h:\ -t cdrom
c:

Reply 2 of 16, by Sephiroth

User metadata
Rank Member
Rank
Member

Whenever you use automatic core or cycles, older games tend to run too fast or have odd problems. Same thing happens with some really old games and max cycles. I normally run either a normal or dynamic core, and a set number of cycles for the older games. About 1000 cycles is an 8086/8088, and once you're up to around 10k cycles you're around the speed of a mid-range 486.

486 Launcher v2.0 is now under development!

Reply 4 of 16, by Sephiroth

User metadata
Rank Member
Rank
Member

You know for a mod, you sure as hell seem to have to reply to every last message I post and in some negative way. I did read the post and posted a valid response in enough detail so that anybody should be able to get it working right. The automatic core is most-likely his problem, as collector posted a normal core as well. You may personally not want to admit that it's problematic with a hefty number of games, but it is and the core and/or cycles is most-likely his problem, hence the detailed reply.

core=auto cputype=386 cycles=auto cycleup=1000 cycledown=500 […]
Show full quote

core=auto
cputype=386
cycles=auto
cycleup=1000
cycledown=500

Again, auto cycles and auto core, setting them manually as suggested should fix the problem. I don't know how else to say this.

486 Launcher v2.0 is now under development!

Reply 5 of 16, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

setting them manually as suggested should fix the problem

No it doesn't.
If you had read the original posting (why don't you?) it's obvious that it is
a problem with the emulated time not the emulated speed.
But well, guess i have to live with you posting the same over and over for
any nonrelated thing.

Reply 6 of 16, by Sephiroth

User metadata
Rank Member
Rank
Member

He had his cycles on auto, so "adjusting" the "automatic" cycles does have little impact. I noted that months ago myself. Had he used a set number of cycles and then had little difference, say between 1000 and 10000, I'd tend to agree.

486 Launcher v2.0 is now under development!

Reply 8 of 16, by versus

User metadata
Rank Newbie
Rank
Newbie

thanks for your replies, i appreciate it.

i'm afraid my problem isn't solved by setting core and cycles manually...i had the same problem with FP some time ago and tried a lot of different settings. (also in 0.72)

also, the game is actually running pretty slow with my current settings. dosbox reports a cycle rate of "3000" and the way the game is running i'd say that's accurate. (long screen loading times etc.)
it's not speeding like it would be with cylces=max

i'm not really sure what dosbox does when cycles are set to auto...i never noticed the cycle rate actually changing with this on.

Reply 10 of 16, by MiniMax

User metadata
Rank Moderator
Rank
Moderator

If DOSBox reports 3000, then you obviously 1) Didn't follow collectors advice of setting it to 8000, or 2) Made a mistake while doing it.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 12 of 16, by versus

User metadata
Rank Newbie
Rank
Newbie

minimax,

i was refering to the cycle rate dosbox displays when i set cycles to auto...

like i said in my original post i tried numerous settings for cycles and core already. (i had them set even lower, to 5000 if i remember correctly)

on an unrelated side note:

there seems to be a bug in the latest cvs build that makes dosbox start with 3000 cycles no matter what number you enter in the config. adjusting cycles on the fly within dosbox works fine though. (setting it to max also works)

EDIT: silly me, totaly missed that the syntax has been changed. 😖
please ignore my moronic side note.

Last edited by versus on 2008-08-08, 06:35. Edited 1 time in total.

Reply 13 of 16, by MiniMax

User metadata
Rank Moderator
Rank
Moderator
versus wrote:

there seems to be a bug in the latest cvs build that makes dosbox start with 3000 cycles no matter what number you enter in the config. adjusting cycles on the fly within dosbox works fine though. (setting it to max also works)

MiniMax wrote:

If DOSBox reports 3000, then you obviously 1) Didn't follow collectors advice of setting it to 8000, or 2) Made a mistake while doing it.

DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32

Reply 14 of 16, by collector

User metadata
Rank l33t
Rank
l33t

Are you sure that it is using the dosbox.conf that you edited? Start DOSBox with the -conf "path_to_your.dosbox.conf" switch.

The Sierra Help Pages -- New Sierra Game Installers -- Sierra Game Patches -- New Non-Sierra Game Installers

Reply 15 of 16, by Sephiroth

User metadata
Rank Member
Rank
Member

You're saying you set "cycles=8000" and it still reported 3000? If that's the case either it isn't finding your configuration file and using defaults, or something else is up. Have you tried starting it from the "Run..." box in Windows and specified the full path for the configuration file? If that fails you got me.

486 Launcher v2.0 is now under development!

Reply 16 of 16, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

cycles=8000 doesn't work in the cvs currently
collector gave the correct syntax.

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