Homebrew Dosbox .conf and .map files collection for Wiiflow

[Tetsuo Shima]

Hi, I tried to follow the steps of installing dosbox-wii onto my SD card and tried 3 different versions so I could play commander keen on my Wii.
My 3 attempts in order:

• Tantric's DOSBox.Wii.1.7.zip
  (tried installing to apps\dosbox-wii)
  
  
• Retro100's Doxbox-wii 1.7 beta 4
  (Overwrote Tantric's installation and copied files to apps\dosbox-wii)
  
  
• Wiimpathy's Dosbox_wii_r1.zip
  (Note sure I installed the last one correctly. After installing wiiflow, I unzipped these files to \wiiflow\plugins)

I copied the files from the original post for keen and was able to load Commander Keen 4 in dosbox, but it wasn't working for me with a wiimote, only a USB keyboard.

Spoiler: Contents of DOSBox\Commander Keen 4 - Secret of the Oracle.conf

#Note in this file the only thing I changed was the mounting path at the end

# This is the configurationfile for DOSBox 0.74. (Please use the latest version of DOSBox)
# Lines starting with a # are commentlines and are ignored by DOSBox.
# They are used to (briefly) document the effect of each option.

[sdl]
# fullscreen: Start dosbox directly in fullscreen. (Press ALT-Enter to go back)
# fulldouble: Use double buffering in fullscreen. It can reduce screen flickering, but it can also result in a slow DOSBox.
# fullresolution: What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).
# Using your monitor's native resolution with aspect=true might give the best results.
# If you end up with small window on a large screen, try an output different from surface.
# windowresolution: Scale the window to this size IF the output device supports hardware scaling.
# (output=surface does not!)
# output: What video system to use for output.
# Possible values: surface, overlay.
# autolock: Mouse will automatically lock, if you click on the screen. (Press CTRL-F10 to unlock)
# 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. Resetmapper only works with the defaul value.
# 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=keen.map
usescancodes=true

[dosbox]
# language: Select another language file.
# machine: The type of machine DOSBox 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.
# This value is best left at its default to avoid problems with some games,
# though few games might require a higher value.
# There is generally no speed advantage when raising this value.

language=
machine=svga_s3
captures=capture
memsize=8

[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,
# then the scaler will be used even if the result might not be desired.
# Possible values: none, normal2x, normal3x, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x.

frameskip=0
aspect=false
scaler=none

[cpu]
# core: CPU Core used in emulation. auto will switch to dynamic if available and
# appropriate.
# Possible values: auto, 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 decrease/increase with keycombos.(CTRL-F11/CTRL-F12)
# cycledown: Setting it lower than 100 will be a percentage.

core=normal
cputype=386_slow
cycles=2400
cycleup=10
cycledown=20

[mixer]
# nosound: Enable silent mode, sound is still emulated though.
# rate: Mixer sample rate, setting any device's rate higher than this will probably lower their sound quality.
# Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
# 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=22050
blocksize=512
prebuffer=20

[midi]
# mpu401: Type of MPU-401 to emulate.
# Possible values: intelligent, uart, none.
# mididevice: Device that will receive the MIDI data from MPU-401.
# Possible values: default, win32, alsa, oss, coreaudio, coremidi, none.
# midiconfig: Special configuration options for the device driver. This is usually the id of the device you want to use.
# When using a Roland MT-32 rev. 0 as midi output device, some games may require a delay in order to prevent 'buffer overflow' issues.
# In that case, add 'delaysysex', for example: midiconfig=2 delaysysex
# See the README/Manual for more details.

mpu401=intelligent
mididevice=default
midiconfig=

[sblaster]
# sbtype: Type of Soundblaster to emulate. gb is Gameblaster.
# Possible values: sb1, sb2, sbpro1, sbpro2, sb16, gb, 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.
# sbmixer: 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.
# oplemu: Provider for the OPL emulation. compat might provide better quality (see oplrate as well).
# Possible values: default, compat, fast.
# oplrate: Sample rate of OPL music emulation. Use 49716 for highest quality (set the mixer rate accordingly).
# Possible values: 22050, 49716, 44100, 48000, 32000, 16000, 11025, 8000.

sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
sbmixer=true
oplmode=opl3
oplemu=default
oplrate=22050

[gus]
# gus: Enable the Gravis Ultrasound emulation.
# gusrate: Sample rate of Ultrasound emulation.
# Possible values: 22050, 44100, 48000, 32000, 16000, 11025, 8000, 49716.
# gusbase: The IO base address of the Gravis Ultrasound.
# Possible values: 240, 220, 260, 280, 2a0, 2c0, 2e0, 300.
# gusirq: The IRQ number of the Gravis Ultrasound.
# Possible values: 5, 3, 7, 9, 10, 11, 12.
# gusdma: The DMA channel of the Gravis Ultrasound.
# Possible values: 3, 0, 1, 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=22050
gusbase=240
gusirq=5
gusdma=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, 49716.
# 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, 49716.
# 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).
# (Remember to reset dosbox's mapperfile if you saved it earlier)
# Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none.
# timed: enable timed intervals for axis. Experiment with this option, if your joystick drifts (away).
# 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=fcs
timed=true
autofire=false
swap34=false
buttonwrap=false

[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 (optional).
# 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. The default (=true) provides the best
# compatibility but certain applications may run better with
# other choices, or require EMS support to be disabled (=false)
# to work at all.
# Possible values: true, emsboard, emm386, false.
# umb: Enable UMB support.
# keyboardlayout: Language code of the keyboard layout (or none).

xms=true
ems=true
umb=true
keyboardlayout=auto

[autoexec]
# Lines in this section will be run at startup
@Echo off
mount -u c:
mount -u d:

#This line mounts your games and bat folder to the c drive

mount c: sd:/dosbox/games/keen4

c:
keen4e.exe

exit

Spoiler: Contents of DOSBox\keen.map

#This was copied verbatim from the files attached to the OP
hand_shutdown "key 290 mod1"
hand_capmouse "key 291 mod1"
hand_fullscr "key 13 mod2"
hand_restart "key 278 mod1 mod2"
hand_pause "key 19 mod2"
hand_mapper "key 282 mod1"
hand_speedlock "key 293 mod2"
hand_recwave "key 287 mod1"
hand_caprawmidi "key 289 mod1 mod2"
hand_decfskip "key 288 mod1"
hand_incfskip "key 289 mod1"
hand_cycledown "key 292 mod1"
hand_cycleup "key 293 mod1"
hand_caprawopl "key 288 mod1 mod2"
hand_swapimg "key 285 mod1"
key_esc "key 27" "stick_0 button 4" "stick_0 button 17"
key_f1 "key 282" "stick_0 button 0" "stick_0 button 15" "stick_0 button 16"
key_f2 "key 283"
key_f3 "key 284"
key_f4 "key 285"
key_f5 "key 286"
key_f6 "key 287"
key_f7 "key 288"
key_f8 "key 289"
key_f9 "key 290"
key_f10 "key 291"
key_f11 "key 292"
key_f12 "key 293"
key_grave "key 96"
key_1 "key 49"
key_2 "key 50"
key_3 "key 51"
key_4 "key 52"
key_5 "key 53"
key_6 "key 54"
key_7 "key 55"
key_8 "key 56"
key_9 "key 57"
key_0 "key 48"
key_minus "key 45"
key_equals "key 61"
key_bspace "key 8"
key_tab "key 9"
key_q "key 113"
key_w "key 119"
key_e "key 101"
key_r "key 114"
key_t "key 116"
key_y "key 121" "stick_0 button 9"
key_u "key 117"
key_i "key 105"
key_o "key 111"
key_p "key 112"
key_lbracket "key 91"
key_rbracket "key 93"
key_enter "key 13" "stick_0 button 5" "stick_0 button 18"
key_capslock "key 301"
key_a "key 97"
key_s "key 115"
key_d "key 100"
key_f "key 102"
key_g "key 103"
key_h "key 104"
key_j "key 106"
key_k "key 107"
key_l "key 108"
key_semicolon "key 59"
key_quote "key 39"
key_backslash "key 92"
key_lshift "key 304"
key_lessthan "key 60"
key_z "key 122"
key_x "key 120"
key_c "key 99"
key_v "key 118"
key_b "key 98"
key_n "key 110"
key_m "key 109"
key_comma "key 44"
key_period "key 46"
key_slash "key 47"
key_rshift "key 303"
key_lctrl "key 306" "stick_0 button 2" "stick_0 button 12"
key_lalt "key 308" "stick_0 button 1" "stick_0 button 10"
key_space "key 32" "stick_0 button 3" "stick_0 button 11"
key_ralt "key 307"
key_rctrl "key 305"
key_printscreen "key 316"
key_scrolllock "key 302"
key_pause "key 19"
key_insert "key 277"
key_home "key 278"
key_pageup "key 280"
key_delete "key 127"
key_end "key 279"
key_pagedown "key 281"
key_up "stick_0 hat 0 1" "key 273"
key_left "stick_0 hat 0 8" "key 276"
key_down "stick_0 hat 0 4" "key 274"
key_right "stick_0 hat 0 2" "key 275"
key_numlock "key 300"
key_kp_divide "key 267"
key_kp_multiply "key 268"
key_kp_minus "key 269"
key_kp_7 "key 263"
key_kp_8 "key 264"
key_kp_9 "key 265"
key_kp_plus "key 270"
key_kp_4 "key 260"
key_kp_5 "key 261"
key_kp_6 "key 262"
key_kp_1 "key 257"
key_kp_2 "key 258"
key_kp_3 "key 259"
key_kp_enter "key 271"
key_kp_0 "key 256"
key_kp_period "key 266"
jbutton_0_0
jbutton_0_1
jaxis_0_1-
jaxis_0_1+
jaxis_0_0-
jaxis_0_0+
jbutton_0_2
jbutton_0_3
jbutton_1_0
jbutton_1_1
jaxis_0_2-
jaxis_0_2+
jaxis_0_3-
jaxis_0_3+
jaxis_1_0-
jaxis_1_0+
jaxis_1_1-
jaxis_1_1+
jbutton_0_4
jbutton_0_5
jhat_0_0_0
jhat_0_0_3
jhat_0_0_2
jhat_0_0_1
mod_1 "key 305" "key 306"
mod_2 "key 307" "key 308"
mod_3

My apologies it took me a couple tries to get the formatting right.
Is there anything obvious I'm doing wrong? Will the WiiMote work without the classic controller or is the classic controller a must have here?

The .map file is already configured for wiimote and Classic Controller so it should work. All three dosbox versions you tried are working the same way with map files, they need to be placed in dosbox/games, alongside the conf files. I noticed that you use the Sd card, so check if the map files are in sd:/dosbox/games.
Another thing, have you tried launching dosbox from the Homebrew Channel as well? If it works from there the issue could be caused by your Wiiflow version. Which version are you using?
Sometime ago I tested Wiiflow versions compiled with the latest libs, and they were giving issues in dosbox with the controller not responding to any input.

 

[GumbyTheGreat]

The .map file is already configured for wiimote and Classic Controller so it should work. All three dosbox versions you tried are working the same way with map files, they need to be placed in dosbox/games, alongside the conf files. I noticed that you use the Sd card, so check if the map files are in sd:/dosbox/games.
Another thing, have you tried launching dosbox from the Homebrew Channel as well? If it works from there the issue could be caused by your Wiiflow version. Which version are you using?
Sometime ago I tested Wiiflow versions compiled with the latest libs, and they were giving issues in dosbox with the controller not responding to any input.

Hey Tetsuo
Thanks so much for the tips. It looks like I've been having a combination of problems (had some paths that were slightly off, I'm not sure if dosbox is windowsy in that it isn't case-sensitive with commands and paths, I had some paths lowercase in the dosbox.conf file (c:\games\keen1) but they were actually uppercase e.g. actual path = c:\games\KEEN1). Also I had the issue you mentioned with wiiflow, where it didn't seem to pick up on any input from the wiimote.

I tried using dosbox-wii from the homebrew app, and it seems to be receiving buttons from the wiimote and classic controller, but the dpad isn't working for me.
I did have one issue that took me a while to figure out, I'm not sure it works to unmount c, in ds:\DOSBox\dosbox.conf, then mount c sd:\DOSBox\games\KEEN1, or if that causes issues unmounting the drive that dosbox is using to load the conf file at the time).

I'll have to play with it a little bit and see if I can get it to work, or maybe I can find a slightly older release of wiiflow and will have luck with that. Thanks for your help.

One more quick question. Does anyone know of a simple text editor (like nano, or vim, yedit, or some way to get the old dos 'edit' command) that works in dosbox-wii so I can use my wireless keyboard and not have to keep plugging/unplugging the SD card between the wii and laptop while I test configs?

Do you know of a release version of wiiflow lite that works from github from this page? (I'd post a link but I don't have permission to as of yet) github /Fledge68/WiiFlow_Lite/releases

 

[Tetsuo Shima]

Hey Tetsuo
Thanks so much for the tips. It looks like I've been having a combination of problems (had some paths that were slightly off, I'm not sure if dosbox is windowsy in that it isn't case-sensitive with commands and paths, I had some paths lowercase in the dosbox.conf file (c:\games\keen1) but they were actually uppercase e.g. actual path = c:\games\KEEN1). Also I had the issue you mentioned with wiiflow, where it didn't seem to pick up on any input from the wiimote.

I tried using dosbox-wii from the homebrew app, and it seems to be receiving buttons from the wiimote and classic controller, but the dpad isn't working for me.
I did have one issue that took me a while to figure out, I'm not sure it works to unmount c, in ds:\DOSBox\dosbox.conf, then mount c sd:\DOSBox\games\KEEN1, or if that causes issues unmounting the drive that dosbox is using to load the conf file at the time).

I'll have to play with it a little bit and see if I can get it to work, or maybe I can find a slightly older release of wiiflow and will have luck with that. Thanks for your help.

One more quick question. Does anyone know of a simple text editor (like nano, or vim, yedit, or some way to get the old dos 'edit' command) that works in dosbox-wii so I can use my wireless keyboard and not have to keep plugging/unplugging the SD card between the wii and laptop while I test configs?

Do you know of a release version of wiiflow lite that works from github from this page? (I'd post a link but I don't have permission to as of yet) github /Fledge68/WiiFlow_Lite/releases

Dos commands and paths are not case sensitive. If all buttons are working except for the d-pad, it's not Wiiflow's fault. Most probably you changed something in the joystick section of the conf file. Make sure that you have joysticktype=fcs for the d-pad to work.
Wiiflow had those no input issues in some older releases, so just use the most recent version and you'll have no problems at all (5.5.3 at the moment).
To edit the .conf file I often use wiixplorer, but if you want to do it within dosbox you can use several dos txt editors, see this discussion from the Vogons forums

 

[KyleK87]

DosboxWii .conf and .map Collection​

Notice:
Since the new Dosbox Wii release with Dynrec support, some of these .conf files are now obsolete. Many games can run much better with core=dynamic and increased cycles. I will eventually update the ones in the collection.

Purpose:

• Launch dosbox games through Wiiflow, with optimized settings for each game (to achieve the best possible performance)
• Key mappings for Wiimote and (where needed) Classic Controller, so that you won't even need an usb keyboard.

​

Requirements:
Wiiflow or Wiiflow Lite (for banners)
DosboxWii .conf plugin for Wiiflow


--------------------------------------------------------------------------------------

Download game files:
Single game download

All-in-one package:
Download the pack

Installation:
Extract and copy the files to the root of your Hard Disk.
If you want to use an SD card, change usb:/ to sd:/ in the mount path at the end of the conf files (eg mount c sd:/dosbox/games)
Put your original games data in the dosbox/games/subfolders.

- Optional: -
if you're using Wiiflow Lite: install Banners with key mappings and info for each game.


If music or sfx doesn't work make sure to run the games setup in dos and set everything to Soundblaster leaving the default values. Note: some games need to have IRQ=5, others IRQ=7. To launch setups open the desired game .conf file with a text editor, scroll down to the bottom and change the name of the executable file with the name of the setup file (generally install.exe or setup.exe)

Updates:


Credits:
Many, many thanks to the team behind Wiiflow, Fledge68 for Wiiflow Lite and to Sion_Zaphod for the Dosbox .conf plugin!

@Tetsuo Shima Hey this all looks amazing thanks for your work! I can't seem to get dosbox to work through wiiflow lite or to install the banners :\ I BELIEVE I followed all the instructions...Just running all my games with one of your keen maps and running games that use pretty much the same keys and the on screen one which is a pain lol Cheers!

 

[mrmagicm]

Would it be possible to have a pack with wiiflow and dobox program with plugins and parameters all set concerning dosbox?

 

[KyleK87]

Anybody know what version of DOSbox has the "mapper" button in the actual program like in this tutorial? Thanks.

https://mundowiihack.wordpress.com/...etamente-no-wii/comment-page-1/#comment-31181

 

[Wiimpathy]

Anybody know what version of DOSbox has the "mapper" button in the actual program like in this tutorial? Thanks.

https://mundowiihack.wordpress.com/...etamente-no-wii/comment-page-1/#comment-31181

You'll find it there:
https://gbatemp.net/threads/wiiflow-lite.422685/page-76#post-8580238

 

[KyleK87]

You'll find it there:
https://gbatemp.net/threads/wiiflow-lite.422685/page-76#post-8580238

Awesome. Thank you! Is anybody running dosbox through wiiflow? I can get DOSbox to run but for some reason I can't get individual games to show up and run with mapper support if anybody could possibly help out be much appreciated

 

[KyleK87]

Would it be possible to have a pack with wiiflow and dobox program with plugins and parameters all set concerning dosbox?

This would be appreciated

 

[KyleK87]

@Tetsuo Shima thanks so much for this! Got it all working and set up wondering if you were planning on doing other games? Like hocus pocus, captain comic, the first 3 commander keen etc. I'm not sure how to map keys or banners but I would be interested in helping? Thanks for all your work.

 

[KyleK87]

@Tetsuo Shima Thank you for these! I have been playing around with them for a few days. Having an issue with dark forces it needs the CD to run and no boxart. For some reason Monster Bash is crashing on startup but most things run great! any way you could link the game files?

 

[KyleK87]

Is there anybody working on this still? I'm trying to put some games together for wiiflow

 

[rkChdrkls]

First time using dosbox in a few years on the WII. I have installed the new 1.7x beta4 r4301 dynrec but it isn't any faster than the old 2012 dosbox release for me.
Can someone post the optimum settings to use on the WII for these parts of the dosbox.conf file:

output = surface (this or overlay ? )
scaler = normal2x (I changed this to 'none' and it seems slighty faster - leave it or ??
core = auto (changed to dynamic but games then don't load, DOS just stays at command prompt after running any exe)
cputype = auto (leave as is or change ?)

[mixer]
rate = 22050 (should this be changed to 32000 to match the wii's sound spec)
same for oplrate and pcrate - leave at 22050 or change to 32000?

joysticktype = auto (what setting to use the wiimote as an analog joystick - the 2axis option? Not sure what =FCS does.


One other thing I noticed, USB drive access is very slow inside dosbox. To the point where whenever a game accesses the drive to load something the sound interrupts and lags, then goes back to normal. I'm using a fast usb2 hard drive. Is this normal dosbox behavior. (i'm assuming dosbox uses IOS58-rev-6176 to run?

 

[Tetsuo Shima]

Output: I usually set it to overlay but this doesn't seem to really affect performances. So I guess, each one is good.
Scaler: never use normal2x. Always none. This has a great impact on performances.
Core: dynamic is best 90% of the times, it allows you to greatly increase the cycles. On rare occasion, I had to set it to simple because some games didn't like it. This may be your case, try my F1GP (aka World circuit) a few pages back from here. It uses dynamic to great effect! If it doesn't work with my .conf then your dosbox plugin is not the correct one.
Cputype: it can be woth to try 386_slow or 486_slow instead of auto, depending on the game.

[mixer]
Rate: I'm not sure on this, but I believe 32000 could be better.
oplrate and pcrate I always used the default rate, but it can be worth experimenting with 32000 too.

joysticktype: believe me, everything besides FCS is worthless on the Wii. Only way to map the D-pad. You can use the Classic Controller for analog joystick controls, see the aforementioned F1GP. In that game I've even managed to assign horizontal axis (steering) on the left stick and vertical axis (accelerate/brake) on the right stick. The D-pad can be mapped with any key you like, you're not forced to map it to joystick axis. Very handy in simulators like F1GP. where you need analogue controls and a lot of keys.
Dosbox doesn't recognize motion controls, at least I've tried it too, but with no success.

One other thing I noticed, USB drive access is very slow inside dosbox. To the point where whenever a game accesses the drive to load something the sound interrupts and lags, then goes back to normal. I'm using a fast usb2 hard drive. Is this normal dosbox behavior. (i'm assuming dosbox uses IOS58-rev-6176 to run?

I've noticed that sound becomes choppy and laggy when the cycles are not set properly. Sound get better the more you get closer to the "sweet spot". However, with some games, like Alone in the Dark, I failed to eliminate the sound hiccups, most noticeably in the intro, even if the game plays great with dynamic

 

[cereal_killer]

DosboxWii .conf and .map Collection​

Notice:
Since the new Dosbox Wii release with Dynrec support, some of these .conf files are now obsolete. Many games can run much better with core=dynamic and increased cycles. I will eventually update the ones in the collection.

Purpose:

• Launch dosbox games through Wiiflow, with optimized settings for each game (to achieve the best possible performance)
• Key mappings for Wiimote and (where needed) Classic Controller, so that you won't even need an usb keyboard.

​

Requirements:
Wiiflow or Wiiflow Lite (for banners)
DosboxWii .conf plugin for Wiiflow


--------------------------------------------------------------------------------------

Download game files:
Single game download

All-in-one package:
Download the pack

Installation:
Extract and copy the files to the root of your Hard Disk.
If you want to use an SD card, change usb:/ to sd:/ in the mount path at the end of the conf files (eg mount c sd:/dosbox/games)
Put your original games data in the dosbox/games/subfolders.

- Optional: -
if you're using Wiiflow Lite: install Banners with key mappings and info for each game.


If music or sfx doesn't work make sure to run the games setup in dos and set everything to Soundblaster leaving the default values. Note: some games need to have IRQ=5, others IRQ=7. To launch setups open the desired game .conf file with a text editor, scroll down to the bottom and change the name of the executable file with the name of the setup file (generally install.exe or setup.exe)

Updates:


Credits:
Many, many thanks to the team behind Wiiflow, Fledge68 for Wiiflow Lite and to Sion_Zaphod for the Dosbox .conf plugin!

dude, I did all that couple of years ago and everything worked perfectly. Today, I updated the wiiflow plugins (just replaced 2 folders (plugins and plugins_data in the sd:/wiiflow folder) and your config files no longer work. Guide me what should do to make your config files work again.

 

[Tetsuo Shima]

dude, I did all that couple of years ago and everything worked perfectly. Today, I updated the wiiflow plugins (just replaced 2 folders (plugins and plugins_data in the sd:/wiiflow folder) and your config files no longer work. Guide me what should do to make your config files work again.

Strange, I've updated all the plugins just yesterday with the new plugins pack release and dosbox is still working as usual. Are you sure you didn't make other changes?

 

[cereal_killer]

Strange, I've updated all the plugins just yesterday with the new plugins pack release and dosbox is still working as usual. Are you sure you didn't make other changes?

got it all figured out, thanx for help though

 

[KyleK87]

Hey just trying to add some more DOS games to wiiflow could you possibly help break down the controller settings? Thanks for all your work!

 

[mrmagicm]

Can someone help me? someone old enough ^^​

I'm searching for the "infindable" dos game....A japanese vertical shoot them up dos game, with one of the best intro ever made around 1982-88, before, all shoots were all worst than the amiga's on pc.​

Also maybe the best dos shooting ever made almost no one knows, It was on one or two floppies, intro and music was marvelous, it was better than raptor,xenon2 or tyrian in some ways (speed) but graphics maybe not as good as tyrian....​

 

[alzen]

Does anyone have key ids for gamecube controllers?

Years ago i wrote down ids for wiimote and classic controller pro but never did gamecube ones. If noone have it will have to do it manually again.

EDIT:
Wait, is it even possible to use gamecube gamepad with wii dosbox? Just tried a second ago to map anything by pressing buttons on gamecube controller but dosbox mapper does not seem to recognize the controller at all. It says otherwise on wiibrew page as there is gc controller icon visible.