# 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. If DOSBox-X aborts with error 'not enough memory for internal tables' # It is discarded when you boot into another OS.

This area contains private memory structures used by the DOS kernel. # private area size: Set DOSBox-X private memory area size. When clear, unused adapter ROM is mapped out # adapter rom is ram: Map adapter ROM as RAM (mainline DOSBox 0.74 behavior). # If your DOS game breaks under DOSBox-X but works with mainline DOSBox setting this option may help. # If cleared, these areas are allocated dynamically which may improve available memory and emulation accuracy. # mainline compatible mapping: If set, arrange private areas, UMBs, and DOS kernel structures by default in the same way the mainline branch would do it. # captures: Directory where things like wave, midi, screenshot get captured. # use triple buffering and thus won't flicker. # For build engine games, use more memory than in the list above so it can # The maximum resolution and color depth the svga_s3 will be able to display # vmemsize: Amount of video memory in megabytes. # Possible values: hercules, cga, cga_mono, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe, amstrad. # machine: The type of machine DOSBox tries to emulate. # language: Select another language file. # overscan: Width of overscan border (0 to 10). # usescancodes: Avoid usage of symkeys, might not work on all operating systems. # then the shader will be used even if the result might not be desired. # pixelshader: Pixelshader program (effect file must be in Shaders subdirectory). Resetmapper only works with the default 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, openglhq, ddraw, direct3d. # 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, desktop or a 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 comment lines and are ignored by DOSBox. (Please use the latest version of DOSBox) It really does feels like my computer should be able to play this properly.Ĭode: # This is the configuration file for DOSBox SVN-Daum. I really want to experience this game properly and the lag is really starting to grate on my nerves.Įdit: I might also add that I'm using Windows 7 (64 bit), with 4GB of RAM. If anyone have any clues on what to try, I would be extremely grateful. and nothing seems to improve the recurring bursts of lag. I've been spending the last couple of days fiddling around with the settings (different resolutions, 640x480, 800圆00, et.c), I've tested out various options in the DOSbox config file (as well as Gulikoza's custom config) - I've tried changing process priority to highest, increasing the maximum cycles to max, setting the CPU core to dynamic. I really would appreciate any help you've got, if you have any tips or clues on what could be causing this. I know it might sound like a minor issue, but it's really frustrating me and pulling me out of the experience each time it happens (and it's usually a minute or two in between these 'bursts' of lag).

The problem is that SSP launches perfectly and even runs smoothly for a while however, there will be recurring moments of extremely choppy lag that last for about 10-15 seconds, before the game sort of 'jumps back on track' and runs smoothly again. Unfortunately, it wasn't completely the smooth ride I'd hoped it would be, on the technical side. Hey guys! Being a fan of SS2, I tried to get System Shock Portable to run properly on my computer so I can experience it for the first time.

Dosbox windows 3.1 games stutter