Page 1 of 2

ISSUE #08 - running IBMPCjr & CD Games

Posted: 13 Jan 2010, 15:00
by Phoenix
Hi All,

Can someone already post some pieces here about how to run a IBMPCjr & CD Game properly with commandlines/configs for dosbox (te_lanus?)

*edit: it seems that majorborcarl already posted something here, i have to examine this also ;) http://ecc.phoenixinteractive.nl/viewto ... 888#p13888

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 13 Jan 2010, 16:34
by te_lanus
I know the IBM PCjr
Needs a config file as command line doesn't work changing the machine.
see http://vogons.zetafleet.com/viewtopic.p ... 755#176755

in the conf file The following needs to be done: (I included Mine)
Spoiler: show
# This is the configurationfile for DOSBox .
# 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 video system to use for output.
# Possible values: surface, overlay, opengl, openglnb, ddraw.
# autolock: Mouse will automatically lock, if you click on the screen.
# 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.
# usescancodes: Avoid usage of symkeys, might not work on all operating systems.

fullscreen=true
fulldouble=false
fullresolution=original
windowresolution=original
output=ddraw
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper.txt
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=pcjr
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,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=none

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

core=auto
cputype=auto
cycles=fixed 500
cycleup=500
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=2048
prebuffer=10

[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 README for details.

mpu401=intelligent
mididevice=default
midiconfig=

[sblaster]
# sbtype: Type of sblaster to emulate.
# Possible values: sb1, sb2, sbpro1, sbpro2, sb16, 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 or old might provide better quality (see oplrate as well).
# Possible values: default, compat, fast, old.
# 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=auto
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=false

[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).
# Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none.
# 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=none
timed=true
autofire=false
swap34=false
buttonwrap=true

[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.
# 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=none

[autoexec]
# Lines in this section will be run at startup.
Then Commandline needs to look like this:

Code: Select all

param = "-c boot " %rom%" -l a"
This work. I've tested It :smartass: :detective:

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 13 Jan 2010, 20:10
by Phoenix
Great work te_lanus :thumb: , can you post some 'test' roms in the platform hunting section please, so i can also test this...

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 18 Jan 2010, 18:18
by Phoenix
@te_lanus

1. Is this config (above) also for CD games?

2. I tried to start an IMG file...WORKS, command:

Code: Select all

dosbox.exe -c boot MOONPAT.IMG -l a
ecc_dosbox_IMG.png
ecc_dosbox_IMG.png (15.65 KiB) Viewed 2585 times
3. I tried to start an JRC file...FAILED, command:

Code: Select all

dosbox.exe -c boot PITFALL2.JRC -l a
ecc_dosbox_JRC.png
ecc_dosbox_JRC.png (22.54 KiB) Viewed 2585 times
any help with this would be nice :D

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 18 Jan 2010, 18:55
by te_lanus
No. It is only for IBM PCjr. For CD's One would Change

Code: Select all

[list][*]machine=svga_s3
[*]memsize=32
[*]cycles=max
[/list]
But one need a script(?) as the following needs to be added, but is game-specific:
For Iso's

Code: Select all

mount c H:\Emu\dos\dosroot\hd
imgmount d G:\Iso's\Carmageddon.iso -t cdrom -f iso


for cd's

Code: Select all

mount c c:\dosgames -freesize 1000
mount d d:\ -t cdrom -label Daggerfall

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 18 Jan 2010, 20:42
by Phoenix
Ok thanks!,

But how do i start a JRC file then, example: PITFALL2.JRC :-k

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 18 Jan 2010, 21:06
by te_lanus
Hi Phoenix

According to the guys at Dosbox, IBM PCjr's "Support is still limited"

Thus I went and searched for something better. Found that MESS 0.136 support it.

Code: Select all

mess.exe ibmpcjr -cart1 %ROM%
It's the code to run *.jrc files

Code to run *.img in MESS is:

Code: Select all

ibmpcjr -flop1 %ROM%

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 18 Jan 2010, 22:17
by Phoenix
So actually a JRC rom cannot be run in dosbox for the moment?

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 18 Jan 2010, 23:15
by te_lanus
Phoenix wrote:So actually a JRC rom cannot be run in dosbox for the moment?
:no:

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 19 Jan 2010, 22:08
by Phoenix
Yahooo! :multi:

Improved the script to run IMG files too :yes_head: , ZIP the IMG files (one img per zip) and import into ECC , it will run perfectly, i'll add this script tomorrow, because i have very little time now, and this needs an ECC Live! update ;), stay tuned!

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 20 Jan 2010, 10:10
by Phoenix
@te_lanus,

Where did you get that dosbox.conf file with all those comments you made for PCjr?

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 20 Jan 2010, 13:21
by te_lanus
Phoenix wrote:@te_lanus,

Where did you get that dosbox.conf file with all those comments you made for PCjr?
It's the normal Dosbox config file that I modified to suit my needs

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 20 Jan 2010, 20:12
by Phoenix
When i install a clean version of dosbox, there isn't any dosbox.conf file :no: .....can you attatch (zip) an unmodified file here please?

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 20 Jan 2010, 20:57
by te_lanus
Hi Phoenix

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 21 Jan 2010, 01:33
by Phoenix
Thank you!

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 21 Jan 2010, 22:39
by Phoenix
Ok, i have change some iece of the code to let the code be 'rom type' running, so it runs subroutines on wich rom type is being detected

Code: Select all

; === DETERMINE ROM TYPE ===
ToolTip("Determing ROM type...", $ClientRes[0]/2, $ClientRes[1]/2, "ECC DOSBox", 1, 2)
RecursiveFileSearch($GameOutputFolder, "(?i)\.(img)", "", 1, true, 0) ;Search only for .IMG files.
If Ubound($RFSarray) = 2 Then ;When there is only 1 IMG file found (+1) = 2.
	$RomType = "img"
Else
	$RomType = "dos"
EndIf

Code: Select all

; === CONFIGURATION ===
If $RomType = "dos" Then ;Start configuration for plain dosgame.
	ConfigStartup()
	ConfigDosbox()
EndIf
If $RomType = "img" Then ;Start configuration PCjr IMG dosgame.
	If IniRead($GameSettingsINI, "STARTUPDATA", "dosboxconf", "") <> "yes" Then
		FileCopy($ConfTemplatePCjrIMG, $GameConfFile, 1) ;Copy PCjr IMG template.
		IniWrite($GameSettingsINI, "STARTUPDATA", "dosboxconf", "yes")
		$GameStartIMG = StringSplit($RFSarray[1], $eccFileRomCrc32 & "\", 1) ;Get only the filename from $RFSarray[1]
		IniWrite($GameSettingsINI, "STARTUPDATA", "gamestart", $GameStartIMG[2])
	EndIf
EndIf

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 24 Jan 2010, 21:23
by Vicman
Hi Phoenix,

how to add CD-Games in eCC ? (meaning CD-image-mounting)

'cause i can't find a "menue" yet in eCC/dosbox-script, i make it this way :

1. I put the pre-Installed game & the CD-ISO-Image in one Folder, and zip them.
2. I parse this zip in eCC
3. I start the game in ecc, select the start-extension & the dos-config.
4. I go to the "ecc-script\dosbox\configs" - Folder and add the [autoexec] manually into the *.conf-file

This works !

So, is mounting CD-Images still in developement ? or did i missed something ? 8-[

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 25 Jan 2010, 13:21
by Phoenix
Vicman,

The script is not ready yet to support ISO images, please post a sample ISO in the Platform hunting section so i can experiment with it ;)

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 25 Jan 2010, 17:55
by Vicman

Re: ISSUE #08 - running IBMPCjr & CD Games

Posted: 28 Jan 2010, 20:25
by Phoenix
Hi Vicman,

I've got it running :clap: , a question though....why have you packed the rootfiles inside the iso to the same folder the iso resides?, whas this nessesary?, can this ISO also be started if it is alone (single packed?)