Alternative Daggerfall install instructions

Post » Fri Feb 18, 2011 10:32 pm

I installed the game and it runs just fine till you go outside. Then everything just goes really slow. What's the deal with this one?
User avatar
Shannon Marie Jones
 
Posts: 3391
Joined: Sun Nov 12, 2006 3:19 pm

Post » Sat Feb 19, 2011 2:20 am

Sounds like a setting in your "dosbox.conf" file. Copy/paste it here.
User avatar
des lynam
 
Posts: 3444
Joined: Thu Jul 19, 2007 4:07 pm

Post » Sat Feb 19, 2011 9:14 am

Sounds like a setting in your "dosbox.conf" file. Copy/paste it here.



# This is the configurationfile for DOSBox 0.73.
# 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=false
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.
# 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=32

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

core=auto
cputype=auto
cycles=auto
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=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).
# 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=auto
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=auto

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

ipx=false

[autoexec]
# Lines in this section will be run at startup.

mount c c:\dosgames -freesize 1000
mount d c:\dosgames\dfcd -t cdrom -label Daggerfall
c:
cd\dagger
dagger
User avatar
joseluis perez
 
Posts: 3507
Joined: Thu Nov 22, 2007 7:51 am

Post » Sat Feb 19, 2011 10:23 am

Try setting memsize to 64, and cycles to max.
User avatar
Elena Alina
 
Posts: 3415
Joined: Sun Apr 01, 2007 7:24 am

Post » Sat Feb 19, 2011 5:14 am

On some games i use with DOSBox i noticed that when i had cycles=auto it set the cycles to around 3000.
3000 is way way way too low for most DOS games, and for Daggerfall that even use 3D, it is a joke.

So as previously hinted, you should first try cycles=max instead of cycles=auto or any number.
User avatar
oliver klosoff
 
Posts: 3436
Joined: Sun Nov 25, 2007 1:02 am

Post » Sat Feb 19, 2011 1:37 am

Your memsize is fine. Change "output=surface" to "output=ddraw". Surface is pretty slow. If ddraw doesn't work well try opengl.
User avatar
Rex Help
 
Posts: 3380
Joined: Mon Jun 18, 2007 6:52 pm

Post » Fri Feb 18, 2011 11:01 pm

D'oh. I thought I had set that in the install, but I didn't save it before I closed it.
User avatar
Chris Johnston
 
Posts: 3392
Joined: Fri Jul 07, 2006 12:40 pm

Post » Sat Feb 19, 2011 5:13 am

Thanks for the instructions dude. This will work on a Macintosh, right?
User avatar
FABIAN RUIZ
 
Posts: 3495
Joined: Mon Oct 15, 2007 11:13 am

Post » Sat Feb 19, 2011 3:04 am

On some games i use with DOSBox i noticed that when i had cycles=auto it set the cycles to around 3000.
3000 is way way way too low for most DOS games, and for Daggerfall that even use 3D, it is a joke.

So as previously hinted, you should first try cycles=max instead of cycles=auto or any number.

cycles=max is the highest setting
User avatar
Oyuki Manson Lavey
 
Posts: 3438
Joined: Mon Aug 28, 2006 2:47 am

Post » Sat Feb 19, 2011 12:22 am

OK, you may not be able to help, since I'm trying to install the game from my original CD version of the game. But everything seems to be working fine until I get into the game and click on the install option. At that point the mouse locks up and nothing happens. My C: drive light is flashing, but I sit there for 5 or 10 minutes and never get any options for install size or anything else.

Is it that I'm being impatient or what?

Thanks
User avatar
u gone see
 
Posts: 3388
Joined: Tue Oct 02, 2007 2:53 pm

Post » Fri Feb 18, 2011 8:36 pm

Are you doing this on an older PC? If so, your CD could be bad (although this would be pretty obvious), or your CD or hard drive could be failing. That's a pretty generic diagnosis but that's the best I can do without more information. Anything more specific like your operating system or system specifications would be helpful.

In the case that you're doing this in DOSBox, something is definitely awry.
User avatar
Haley Cooper
 
Posts: 3490
Joined: Wed Jun 14, 2006 11:30 am

Post » Fri Feb 18, 2011 11:33 pm

OK, you may not be able to help, since I'm trying to install the game from my original CD version of the game. But everything seems to be working fine until I get into the game and click on the install option. At that point the mouse locks up and nothing happens. My C: drive light is flashing, but I sit there for 5 or 10 minutes and never get any options for install size or anything else.

Is it that I'm being impatient or what?

Thanks

Try copying the entire contents of the CD to a folder on your hard drive called "dfcd", then following the instructions should be easy.
User avatar
мistrєss
 
Posts: 3168
Joined: Thu Dec 14, 2006 3:13 am

Post » Sat Feb 19, 2011 8:44 am

Thanks for the tips--gave up on the CD and downloaded the free version. I've got it working late last night. Now I'm going to dig around to see where I put my original manual.

It's kind of amazing. I haven't played this game in at least 5 years and, while the graphics aren't state of the art, it's still addictive.
User avatar
CxvIII
 
Posts: 3329
Joined: Wed Sep 06, 2006 10:35 pm

Post » Fri Feb 18, 2011 10:36 pm

5.) Actually launching the game is where most people seem to get tripped up, so I'm going to offer an alternative solution. Instead of mounting the Daggerfall CD, we're going to change one character in the "z.cfg" file to point Daggerfall to its own directory. Close DOSBox and go to the directory where Daggerfall is installed; assuming you followed this guide, that directory would be "C:\dosgames\dagger\"

Double-click "z.cfg". If it asks you what program to open this file with, choose Notepad.

Find where it says pathcd d:\dagger\arena2 and change it to pathcd c:\dagger\arena2

This is a cheap but effective way of getting the game to run. DOSBox has come a long way but Daggerfall is a finicky game and CD emulation is still not perfect. This will not display movies. To get movie output, you'll have to copy the contents of the "dfcd\dagger\arena2" folder to the "c:\dosgames\dagger\arena2" folder. You'll probably get a prompt saying that the original files are about to be overwritten; this is fine.


I have done this step exactly as written here, after trying the original way. In both cases (and on two seperate PCs), I am getting an error saying that it is still unable to locate the Daggerfall CD. Any suggestions?

Edit:
Copy all the files from DFCD\Arena2 to Dagger\Arena2 then change the autoexec of your Daggerfall.conf file to below,changing drives/folders for where you installed your game:

[autoexec]
mount c "c:\"
mount d "c:\dagger\arena2" -t cdrom -label Daggerfall
C:
cd/
cd dagger
FALL.EXE Z.cfg
exit

This seems to have worked to fix the problem. I don't know why, but I thought I would mention it in case it helps anyone else. If someone knows why this worked when the first two ways didn't, I'd appreciate knowing. Thanks!
User avatar
Laura
 
Posts: 3456
Joined: Sun Sep 10, 2006 7:11 am

Post » Sat Feb 19, 2011 1:59 am

Minor update and a bump for new people who might be having problems.
User avatar
Karl harris
 
Posts: 3423
Joined: Thu May 17, 2007 3:17 pm

Post » Sat Feb 19, 2011 10:02 am

Fantastic! thx man, couldn't have done it without your entries. I didn't config sound when I installed, is there any way I can do it now that I am playing? or do I have to re-install?
Thanks again for your guidance.
User avatar
Bethany Watkin
 
Posts: 3445
Joined: Sun Jul 23, 2006 4:13 pm

Post » Sat Feb 19, 2011 5:32 am

Sure. All you have to do is get to "c:\dagger" and type "setup". That will take you to the sound configuration utility. From there:

Select "Auto Detect". If it gives you a SCSI-drive warning, ignore it and proceed (unless you are using an actual SCSI drive, which I highly doubt; if you are, you know what it is and how to proceed). It will probably come up with Soundblaster 16; this is fine as long as your IRQ is 7 and DMA is 1. These are default DOSBox settings and they shouldn't be anything else unless you've tampered with the configuration file. Soundblaster 16 is also fine for the MIDI settings. Daggerfall has different music output depending on what MIDI card you have selected; once you feel comfortable with editing this then you can come back and find the one you like the best. Personally, I prefer ESS AudioDrive for MIDI output, but it is ultimately up to you.

User avatar
Margarita Diaz
 
Posts: 3511
Joined: Sun Aug 12, 2007 2:01 pm

Post » Fri Feb 18, 2011 8:19 pm

I installed daggerfall correctly to the instructions posted here along with the patch but when i attempt to run the game through dosbox everything runs properly no errors till i type in the final line of
mount c c:\dosgames -freesize 1000
c:
cd dagger
fall z.cfg

after i type in that i press enter dosbox screen goes black like its starting the game and then this pops up

box title: microsoft visual c++ runtime library

this application has requested the runtime to terminate in an unusual way. please contact the application's support team for more information.

i am currently running windows 7
User avatar
Captian Caveman
 
Posts: 3410
Joined: Thu Sep 20, 2007 5:36 am

Post » Fri Feb 18, 2011 10:32 pm

ok this is totally not working for me. idk if it's my [censored] or my pc. but ill work harder.
User avatar
yessenia hermosillo
 
Posts: 3545
Joined: Sat Aug 18, 2007 1:31 pm

Post » Sat Feb 19, 2011 3:19 am

I have a weird problem, whatever version of DOSBox I use, when I am trying to use DAG213.exe DOSBox crashes with a Microsoft error either just before or just after the update ties to access the .bsa to make changes!

Any help would be appreciated!

SOLVED!

Just installed VDMSOund and opened DAG213 with it and a CMD box opened and the patch installed correctly!
User avatar
roxxii lenaghan
 
Posts: 3388
Joined: Wed Jul 05, 2006 11:53 am

Previous

Return to The Elder Scrolls Series Discussion