LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 10-24-2012, 07:00 PM   #1
dwmolyneux
Member
 
Registered: Feb 2012
Location: United States of America
Distribution: "First Time Gentoo user",Debian, Fedora, LinuxMint
Posts: 124

Rep: Reputation: Disabled
Question custom run script for dosbox?


OS: Linux Mint 13
Emu: DosBox ver. 0.74

My question is how am I able to create a custom script for launching DosBox?

The scenario: I have The Elder Scrolls II Daggerfall installed to 2 different dir.

Code:
path1= ~/.PlayOnLinux//wineprefix/ElderScrolls_Daggerfall/dosdevices/../drive_c

path2= ~/dosprogs
I need to use 2 separate config files that hold the auto-mount param.

I am looking at wanting to have something like:
example
Code:
var x=0
if x=1 use config1
else use config2
with dosbox output giving an option to enter 1 or 2 to select which one to run.

I'm not very good at scripting and only search results I was able to find dealt with Windows XP and newer plus none addressed what I am wanting to do.

The reason for having this type of config is because I have my normal game play under one & doing video with the other as a tutorial type thing. I want the 2 kept separate because I use all save slots for a single character as game progresses.
 
Old 10-25-2012, 12:38 AM   #2
nugat
Member
 
Registered: Sep 2012
Posts: 122

Rep: Reputation: 31
Post

try this simple script:
Code:
#!/bin/bash
case $1 in
  config1)
echo running config one..
dosbox -c config1 etc
  ;;
  config2)
echo running config two...
dosbox -c config2 etc
  ;;
  *)
    echo "Usage: $0 {config1|config2}"
    exit 1
esac
make it executable (call it "dosrunner.sh" or something). then call it like this:
Code:
./dosrunner.sh config1
./dosrunner.sh config2
 
Old 10-25-2012, 05:57 PM   #3
dwmolyneux
Member
 
Registered: Feb 2012
Location: United States of America
Distribution: "First Time Gentoo user",Debian, Fedora, LinuxMint
Posts: 124

Original Poster
Rep: Reputation: Disabled
thank you. I'll give it a try and see if the works for me.
 
Old 10-26-2012, 07:34 AM   #4
dwmolyneux
Member
 
Registered: Feb 2012
Location: United States of America
Distribution: "First Time Gentoo user",Debian, Fedora, LinuxMint
Posts: 124

Original Poster
Rep: Reputation: Disabled
Thanks for the help. I couldn't get the shell script to work for me with dosbox but I found an easier & less complicated work around using the autoexec.bat

dosbox-0.74.conf
Code:
# 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, opengl, openglnb.
#         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=false
fulldouble=false
fullresolution=original
windowresolution=original
output=surface
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper-0.74.map
usescancodes=true

[dosbox]
# language: Select another language file.
#  machine: The type of machine 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=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.
#              If 'forced' is appended, then the scaler will be used even if the result might not be desired.
#            Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x.

frameskip=0
aspect=false
scaler=normal2x

[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 decrease/increase with keycombo.(CTRL-F11/CTRL-F12)
# cycledown: Setting it lower than 100 will be a percentage.

core=auto
cputype=auto
cycles=auto
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: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
# blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged.
#            Possible values: 1024, 2048, 4096, 8192, 512, 256.
# prebuffer: How many milliseconds of data to keep on top of the blocksize.

nosound=false
rate=44100
blocksize=1024
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.
#               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: 44100, 49716, 48000, 32000, 22050, 16000, 11025, 8000.

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

[gus]
#      gus: Enable the Gravis Ultrasound emulation.
#  gusrate: Sample rate of Ultrasound emulation.
#           Possible values: 44100, 48000, 32000, 22050, 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=44100
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: 44100, 48000, 32000, 22050, 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: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716.
#    disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible).

pcspeaker=true
pcrate=44100
tandy=auto
tandyrate=44100
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=auto
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.
#            umb: Enable UMB support.
# keyboardlayout: Language code of the keyboard layout (or none).

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

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

ipx=false

[autoexec]
# Lines in this section will be run at startup.
# You can put your MOUNT lines here.
and then creating
autoexec.bat
Code:
@echo off
MOUNT c /home/****/.PlayOnLinux/wineprefix/ElderScrolls_Daggerfall/dosdevices/../drive_c
PATH=Z:;Y:
mount W "/home/****/.PlayOnLinux//wineprefix/ElderScrolls_Daggerfall/drive_c/DFCD" -t cdrom -label Daggerfall
C:
cd C:\DAGGER
DAGGER
and create another autoexec.bat using the desired path for the "MOUNT C /..."

For me I have found it best to place the autoexec.bat files inside the desired dir to be mounted as the C:\ drive.

then to launch
Code:
/usr/bin/dosbox /path/to/autoexect.bat
I created a different launcher for each using the correct path. It also works in teminal as well.

I hope this helps anyone else that may have the same issue. There may be an easier method but this is what worked for me.
 
Old 06-24-2018, 12:40 AM   #5
gdmellott
LQ Newbie
 
Registered: Jan 2006
Location: Paonia, Colorado USA
Distribution: Red Hat, Debian, trying others.
Posts: 17

Rep: Reputation: 0
A reply to agree: its works somewhat like stated.

In using DOS for very basic records keeping using self made program that works multiple data files in lockstep to assure things are not getting corrupted. So getting this to work on a computer with a secure environment for it is nice.

This simple method worked:

1) Put a shell script in the /home/<user>/.dosbox directory to "Run". (I've yet to note how to add it to the KDE desktop's Menu system)

My script simply contains 1 line:

dosbox "<path to directory containing the DOS program +>/autoexec.bat"

(Quotes were not necessary if the are no spaces or other odd characters in the path and name.)

Note: DOSBox at one time, while trying to work this up, seem to take this to also be the mount point for C:

The 'autoexec.bat' file states:

REM Setting drive C's mount point:
mount c "<repeat of path above: directory for program and autoexec.bat>"

REM Change Drive to C:
C:

REM Run the program (adding any commands it needs to run files, etc.)
multi-ed.exe <file to work>

REM One can add here things to do after closing program
REM like backup the data someplace else.

#end of file "autoexec.bat"

Last edited by gdmellott; 06-24-2018 at 12:50 AM. Reason: code errors
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
How 2 run DOSBOX or TurboC3 in Ubuntu 10.04 LTS Abhishek Rockzzz Ubuntu 1 10-04-2011 04:19 PM
[Please] Run Dosbox on network fakecyborg Linux - Newbie 5 08-11-2010 07:55 PM
Run custom boot script from a network server? cantab Ubuntu 1 06-16-2010 10:26 AM
run custom script at boot time on IPcop lothario Linux - Networking 1 06-24-2008 08:54 PM
to run dos programs --> dosbox, wine, or...? efm Linux - Newbie 2 05-26-2005 03:20 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 06:40 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration