Page 1 of 1

Modifying GoG installs to play MUNT

Posted: Thu Jul 30, 2015 11:55 pm
by Tawmis
So the GoG installs don't look normal (and there's no "Sierra" set up to pick what sound you want for GoG) - but was curious about modifying GoG DOSBox config files?

For example for King's Quest IV:

Code: Select all

# This is the configurationfile for DOSBox 0.72.
# 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 to use for output: surface,overlay,opengl,openglnb,ddraw.
# autolock -- Mouse will automatically lock, if you click on the screen.
# sensitiviy -- Mouse sensitivity.
# waitonerror -- Wait before closing the console if DOSBox has an error.
# priority -- Priority levels for DOSBox: lowest,lower,normal,higher,highest,pause (when not focussed).
#             Second entry behind the comma is for when DOSBox is not focused/minimized.
# mapperfile -- File used to load/save the key/event mappings from.
# usescancodes -- Avoid usage of symkeys, might not work on all operating systems.

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

[DOSBox]
# language -- Select another language file.
# memsize -- Amount of memory DOSBox has in megabytes.
# machine -- The type of machine tries to emulate:hercules,cga,tandy,pcjr,vga.
# captures -- Directory where things like wave,midi,screenshot get captured.

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.
#           Supported are none,normal2x,normal3x,advmame2x,advmame3x,hq2x,hq3x,
#                         2xsai,super2xsai,supereagle,advinterp2x,advinterp3x,
#                         tv2x,tv3x,rgb2x,rgb3x,scan2x,scan3x.
#           If forced is appended (like scaler=hq2x forced), the scaler will be used
#           even if the result might not be desired.

frameskip=0
aspect=false
scaler=normal2x

[cpu]
# core -- CPU Core used in emulation: normal,simple,dynamic,auto.
#         auto switches from normal to dynamic if appropriate.
# cycles -- Amount of instructions DOSBox tries to emulate each millisecond.
#           Setting this value too high results in sound dropouts and lags.
#           You can also let DOSBox guess the correct value by setting it to max.
#           The default setting (auto) switches to max if appropriate.
# cycleup   -- Amount of cycles to increase/decrease with keycombo.
# cycledown    Setting it lower than 100 will be a percentage.

core=auto
cycles=max
cycleup=500
cycledown=20

[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.
# blocksize -- Mixer block size, larger blocks might help sound stuttering
#              but sound will also be more lagged.
# prebuffer -- How many milliseconds of data to keep on top of the blocksize.

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

[midi]
# mpu401      -- Type of MPU-401 to emulate: none, uart or intelligent.
# device      -- Device that will receive the MIDI data from MPU-401.
#                This can be default,alsa,oss,win32,coreaudio,none.
# config      -- Special configuration options for the device. In Windows put
#                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:none,sb1,sb2,sbpro1,sbpro2,sb16.
# sbbase,irq,dma,hdma -- The IO/IRQ/DMA/High DMA address of the soundblaster.
# mixer -- Allow the soundblaster mixer to modify the DOSBox mixer.
# oplmode -- Type of OPL emulation: auto,cms,opl2,dualopl2,opl3.
#            On auto the mode is determined by sblaster type.
#            All OPL modes are 'Adlib', except for CMS.
# oplrate -- Sample rate of OPL music emulation.

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

[gus]
# gus -- Enable the Gravis Ultrasound emulation.
# gusbase,irq1,irq2,dma1,dma2 -- The IO/IRQ/DMA addresses of the 
#            Gravis Ultrasound. (Same IRQ's and DMA's are OK.)
# gusrate -- Sample rate of Ultrasound emulation.
# 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=true
gusrate=22050
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.
# tandy -- Enable Tandy Sound System emulation (off,on,auto).
#          For auto Tandysound emulation is present only if machine is set to tandy.
# tandyrate -- Sample rate of the Tandy 3-Voice generation.
# disney -- Enable Disney Sound Source emulation. Covox Voice Master and Speech Thing compatible.

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

[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).
# 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=auto
timed=true
autofire=false
swap34=false
buttonwrap=true

[serial]
# serial1-4 -- 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).
#              for modem: listenport (optional).
#              for nullmodem: server, rxdelay, txdelay, telnet, usedtr,
#                             transparent, port, inhsocket (all optional).
#              Example: serial1=modem listenport:5000

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=none

[ipx]
# ipx -- Enable ipx over UDP/IP emulation.

ipx=false

[autoexec]
# Lines in this section will be run at startup.
mount C .
c:
cls
sierra
exit

There's two places where it seems logical it could be - like where the SBTYPE is and also the PCSPEAKER area maybe somehow saying MT32=TRUE or something?

Anyone know?

Re: Modifying GoG installs to play MUNT

Posted: Fri Jul 31, 2015 12:53 am
by Collector
The Munt builds of DOSBox have conf entries that are missing from stock DOSBox. Additionally for some reason GOG uses an old version of the cont file. In this case 0.72. You do not have to use a complete conf file as DOSBox will just fall back onto defaults for every missing setting. I only include the settings that deviate from defaults or ones that the user may be likely to want to change and is not in the config tool.

What I would do is to copy the conf file from one of my Munt installers and modify it for that game, such as changing the game's EXE if different. Also, you need to set the RESOURCE.CFG to use MT-32 for the sound driver.

By the way, what GOG releases are you talking about? I have Munt installers for most of the SCI games that are better with Roland sound. Is there something that you got from GOG for which you do not have the original media?

Re: Modifying GoG installs to play MUNT

Posted: Fri Jul 31, 2015 1:45 am
by Tawmis
Collector wrote: By the way, what GOG releases are you talking about? I have Munt installers for most of the SCI games that are better with Roland sound. Is there something that you got from GOG for which you do not have the original media?
I typically purchase Sierra games from GOG.com just to support adventure games. So I just got a new Windows 8.1 laptop (for my birthday) and logged into GOG.com and was just downloading and installing them from there only because my original media is boxed up in plastic bins in the garage and would require fetching them and then getting a USB CD-ROM (my laptop doesn't have a CD/DVD-ROM).

Re: Modifying GoG installs to play MUNT

Posted: Fri Jul 31, 2015 4:38 am
by Qbix
Did you install munt as midi driver ?
Then in the configuration of DOSBox, you need to change the entry "midiconfig" or "config" depending on the version of DOSBox.
(type mixer /listmidi inside DOSBox to find the MUNT number and enter that as (midi)config)

And change the game settings as Collector pointed out.

Re: Modifying GoG installs to play MUNT

Posted: Fri Jul 31, 2015 10:21 am
by envisge0ne
GOG Sierra games comes with, and installs, DOSBox .074, so he just needs to edit the DOSBox config file and add the midiconfig= with the value for the munt emulator. As stated previously, run DOSBox and type mixer /listmidi. You should then see something like "MT-32 Synth Emulator" listed as 0 or 1. So if it's 1, then you'd add the line midiconfig=1 to the DOSBox conf file.

Re: Modifying GoG installs to play MUNT

Posted: Fri Jul 31, 2015 10:37 am
by Collector
Well, if he is using the driver. I don't know if he has the driver installed or not. He did not say, but I was assuming that he was using a Munt build of DOSBox since I do know he has a Munt build of DOSBox. The Munt build of DOSBox has a number of MT-32 specific entries in the conf. You don't need to do a listmidi either since Munt is the default device.

Re: Modifying GoG installs to play MUNT

Posted: Fri Jul 31, 2015 4:11 pm
by envisge0ne
Ah, good point. I never used the Munt build of DOSBox. I've heard of it, but was just to lazy to try to get it working. Is there any advantages to that version?

Re: Modifying GoG installs to play MUNT

Posted: Fri Jul 31, 2015 6:41 pm
by Collector
It is self contained. From my end I can do installers for games with Munt and not have to install any drivers on the user's machine. You can try one of the Munt enabled installers is you want to see.

Re: Modifying GoG installs to play MUNT

Posted: Fri Jul 31, 2015 6:53 pm
by MusicallyInspired
If it's the Daum build you can change Conf settings in real time while DOSBox is running.