Hi, ...
 
I have the latest Version = Release Candidate 1.
 
I have DosBox = CVS Build 10 october,
 
     from = http://www.aep-emu.de/cvscompile/
------------- 
I have found a bug, ...
Maybe in D-Fend Reloaded, and/or DosBox. CVS Build 10 october.
=
(In D-Fend Reloaded) = When i change the cpu cycle, in processor value, for a game "in example 10000". And after i run that game = it dont change the value in the game window text upper. This mean it keep 3000 cpu cycle, even if i select in D-Fend Reloaded (cpu cycle), value 10000.
The bug,  must be in D-Fend Reloaded.
(In a dosbox game, after i select a game in D-Fend Reloaded.) = The F11 and F12 key, change the value and it display correctly.
----------
(Update)
Some test that i have made =
 
Ok, after some try, on some dosbox cvs build, and final version = 0.72.
It seam that it is related in the CVS build.
Even if i change in "dosbox.conf", in the dosbox directory, without run D-Fend Reloaded, it make the bug.
Please test, in "dosbox.conf"
cycles=9899
---
I will also try to recreate the file =  "dosbox.conf". 
-------------
(Update)
I have recreate the "dosbox.conf", inside the cvs build 10 october 2008. with the command line =
 
config -writeconf dosbox.conf
--------
After i see in the file "dosbox.conf", cpu section =
[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=auto
cycles=auto
cycleup=500
cycledown=20
-----
When i enter fixed 10000, in the cycles line = It work.
=
cycles=fixed 10000
-----
Then in conclusion, the cvs build have the option added "cputype= "and "cycles=fixed"
Thanks in advance, ... 
Please respond me soon as possible, ... 
---------------------------------------------------------------- 
Sylvain St-Amand