# There is generally no speed advantage when raising this value. # though few games might require a higher value. # This value is best left at its default to avoid problems with some games, # memsize: Amount of memory DOSBox has in megabytes.
# captures: Directory where things like wave, midi, screenshot get captured. # Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe. # machine: The type of machine tries to emulate. # language: Select another language file. # usescancodes: Avoid usage of symkeys, might not work on all operating systems. Resetmapper only works with the defaul value. # mapperfile: File used to load/save the key/event mappings from. # Possible values: lowest, lower, normal, higher, highest, pause. # pause is only valid for the second entry. Second entry behind the comma is for when dosbox is not focused/minimized. # waitonerror: Wait before closing the console if dosbox has an error. # autolock: Mouse will automatically lock, if you click on the screen. # Possible values: surface, overlay, opengl, openglnb. # output: What video system to use for output. # windowresolution: Scale the window to this size IF the output device supports hardware scaling. # If you end up with small window on a large screen, try an output different from surface. # Using your monitor's native resolution with aspect=true might give the best results. # fullresolution: What resolution to use for fullscreen: original or fixed size (e.g. It can reduce screen flickering, but it can also result in a slow DOSBox. # fulldouble: Use double buffering in fullscreen. # fullscreen: Start dosbox directly in fullscreen. # They are used to (briefly) document the effect of each option. # Lines starting with a # are commentlines and are ignored by DOSBox. (Please use the latest version of DOSBox) On PCs you can go quite a bit higher than that default without hitting the sound problem.# This is the configurationfile for DOSBox 0.74. On PCs I think the default is something like 3000 or 6000, which is quite low but the game still runs fine even on such a setting. Nevertheless, if your configuration has CPU Cycle set to a high value, maybe try lowering it and see if it might help. I don't think that's the problem here though since you said the same nf file doesn't repro the problem depending on the setup. One thing worth mentioning is that even on DOSBox on PCs, IIRC at least on some versions (not sure about current versions), setting the CPU Cycle setting too high or to "max" could interfere with the game's sound hardware detection programming resulting in no sound. It makes sense that there could be emulation bugs affecting one but not the other. It makes sense that there would be a difference between Lemmings 2 and pre-Lemmings 2, as the pre-Lemmings 2 DOS games only uses the OPL2 FM synthesis features for sound and music, whereas Lemmings 2 uses other, more advanced SoundBlaster features for sound and music IIRC, at least on the default settings. Based on what you've said it sounds like a DOSBox emulation bug specific to that hardware/platform/port. Hmm, first time we've even heard anyone here trying to run DOSBox on Raspberry Pi, IIRC.
0 kommentar(er)
