If you can give us link to the demo, I am sure someone will give it a try.

I got the download here.

I was directed to it by a thread on the Bethesda Software forums

1) Open Terminal, drag in the DOSBox unix exe (located in DOSBox.app/Contents/MacOS/ by right-click "show packet content").

2) Create a folder daghd (to be used as Drive c: ) anywhere at your hard disk, drag it into terminal (to see the command line as shown in daghd.png.

/Volumes/pathtodosbox/DOSBox.app/contents/MacOS/dosbox /Users/yourname/pathtodosbox/daghd/

This is the first part in the long line of Terminal command.

3) add " -c mount d "/volumes" to the line (w/o enclosed quotes, just the quote left from /volumes).

mount d "/volumes

4) drag in the unstuffed demo folder, enclose it with a quote.
-c mount d "/Users/yourname/pathto/Dag/". The command line should read like this:

/Volumes/pathtodosbox/DOSBox.app/Contents/MacOS/Dosbox /Users/yourname/pathto/daghd/ -c mount d "/volumes/Users/yourname/pathto/Dag/"

5) do not press enter, but add " -t cdrom -label \"dag\"" after the line.

/Volumes/pathtodosbox/DOSBox.app/Contents/MacOS/Dosbox "/Users/yourname/pathto/daghd/" -c "mount d /Users/yourname/pathto/Dag/ -t cdrom -label \"dag\"" -c frameskip=10

I added -c frameskip=10 here, otherwise you'll have to look the intro screen for a long time. If frameskip=10, you can install alomst immediately.

All this will mount the daghd as drive c and the downloaded and unstuffed zip file will be mounted as CD ROM drive (as drive d: in this example)
Be sure, your path to the emulated CD ROM doesn't include space bar (' ').

6) Press return to start the DOSbox

7) Type in "d:", then "install".

Since all files are stored at your hd, you can choose minimum install.

For me, it starts now.

Once installed this way, you can add the demo to your frontend.
In this case, choose /daghd/dagdemo/dagdemo.exe as drive c: and you need still the /dag folder as CD ROM drive to run the demo.

This is the point I must give up, because I don't managed to run this demo by a frontend, mostly the one i created. But for now, I found an error in it which doesn't mount any other drives than C:, when running a game from the games list. Fixed the problem in the source code, but the demo still asks for its cd (the folder "/dag"), if started from insde the frontend even the "CD" has been mounted.

Thanks IIGS_User, I got it working up to a degree. After pressing return in the terminal, DOSBox starts up fine but when I try to change from C: to D: it says that the D: drive doesn't exist. Should I have the terminal point to the daghd folder or the Arena2 folder (where the cd contents are)? Or should it point somewhere else? You refer to "path to DAG", and I can't find any files named "Dag". Did you just abbreviate it? Same for the cd label?

edit: here is what I am inputing into terminal:
/Applications/DOSBox/DOSBox.app/Contents/MacOS/DOSBox "/Users/xxxx/Games/Daggerfall/daghd/" -c "mount d /Users/xxxx/Games/Daggerfall/DAGDEMO/ -t cd rom -label\"dag\"" -c frameskip=10

xx=my user name

edit2: DOSBox reports it as an "illegal type cd"

You have an extraneous space/blank between 'cd' and 'rom'. It is '-t cdrom', not '-t cd rom'.

thanks MiniMax, I didn't see that. Ok now it is recognizing the D: drive but it won't let me install the program because it is saying that it is missing a file: data\dagger.col

The file DAGGER.COL is in the folder "data". what should I do now? Is dos case sensative?

loki23 wrote:

The file DAGGER.COL is in the folder "data". what should I do now? Is dos case sensative?

Nope, DOS don't care about case.

I can't tell you what to do on your Mac, but this configuration seemed to work for me:

1# Title:        The Elder Scrolls: Daggerfall (Demo version 1.0)
2# Developer:
3# Year:         1996
4# Publisher:
5# Status:       Demo
6# Link1:
7# DOSBox:       0.70
8#
9# By MiniMax
10
11[render]
12scaler=normal3x
13
14# I get a strange crackling sound in the game if Gravis Ultrasound is
15# chosen for digital sound effects.
16#
17# Setting gus=false prevents the games auto-detection routines from
18# choosing Gravis Ultra Sound for digital sounds.
19
20[gus]
21gus=false
22
23[autoexec]
24@   echo off
25
26rem +---------------------------------------------------------------
27rem ! Mount the virtual harddisk and the CD-drive.
28rem ! All full install of the demo requires 137 MB disk space.
29rem ! Making the virtual C-drive 200 MB makes everyone happy.
30rem +---------------------------------------------------------------
31
32    mount C "C-drive" -freesize 200
33    mount D "Unzipped\Dag" -t cdrom
34    echo.
35
36rem +---------------------------------------------------------------
37rem ! Are we ready to run the game, or should we try to install it?
38rem +---------------------------------------------------------------
39
40    if exist C:\DagDemo\Z.Cfg           goto Ready
41    if exist C:\DagDemo\DagDemo.Exe     goto Config
42    if exist D:\Install.Exe             goto Install
43    goto Done
44
45:Install
46
47rem +---------------------------------------------------------------
48rem ! Switch to the virtual CD-ROM drive with the unzipped files,
49rem ! and start the install process onto the the virtual harddisk.
50rem +---------------------------------------------------------------
51
52    D:
53    echo Installing Daggerfall demo from D: to C:\DagDemo.
54    echo.
55    echo OBS: Choose Sound Blaster 16, port 388, as the MIDI device.
56    echo.     For some reason, the MPU-401 does not work in Dagerfall Demo.
57    echo.
58    pause
59
60    Install.Exe

61    echo.
62
63:Config
64
65rem +---------------------------------------------------------------
66rem ! Switch to the harddisk, and inform the user about which
67rem ! command to use for configuring the game.
68rem +---------------------------------------------------------------
69
70    C:
71    cd \DagDemo
72
73    echo Type SETUP to configure the game,
74    echo and DAGDEMO to start the game.
75    echo.
76    echo OBS: Choose Sound Blaster 16, port 388, as the MIDI device.
77    echo.     For some reason, the MPU-401 does not work in Dagerfall Demo.
78
79    goto Done
80
81:Ready
82
83rem +---------------------------------------------------------------
84rem ! Switch to the harddisk, and inform the user about which
85rem ! command to use for running the game.
86rem +---------------------------------------------------------------
87
88    C:
89    cd \DagDemo
90
91    echo Type SETUP to configure the game,
92    echo and DAGDEMO to start the game.
93
94    goto Done
95
96:Done
97    echo on

The only thing you should need to change are the 2 lines:

1    mount C "C-drive" -freesize 200
2    mount D "Unzipped\Dag" -t cdrom

Change them to match where you want the demo to install, and where you unpacked the archive.

Have a look at the 60 seconds guide (Mac version) in my signature.

loki23 wrote:

it says that the D: drive doesn't exist. Should I have the terminal point to the daghd folder or the Arena2 folder (where the cd contents are)? Or should it point somewhere else? You refer to "path to DAG", and I can't find any files named "Dag". Did you just abbreviate it?

When I unstuff the download file, it creates a folder called "dag".
That is what I mean with "path to dag".
That one should be mounted as cd drive, in my example as d:
As mentioned before, just enter in the Terminal " -c mount d " and drag the folder after this phrase of text:

Volumes/pathtodosbox/DOSBox.app/Contents/MacOS/Dosbox "/Users/yourname/pathto/daghd/" -c "mount d /Users/yourname/pathto/Dag/ -t cdrom -label "dag"" -c frameskip=10

After dragging in, finish this part with a quote.

Btw, the \ character has to be entered with Alt-Shift-7.

A bit confusing for me, because most pathes have to start with "/volumes/...", not with "/users/...".

At least I managed to run the installed Daggerfall with a frontend.
Have to mount the installed one as drive c:, not the unstuffed (downloaded) folder as I did before. So I mounted the folder "dag" as cd rom (which is true) plus as drive c: (which was wrong). When I mounted "daghd" as drive c:, it worked also from inside a frontend for me.

How to continue at this point?

IIGS_User wrote:

How to continue at this point?

I DON'T KNOW 😒 I got stuck at the same point on my WinXP+DOSBox, so it is not a platform specific problem. I tried to click on everything(?), hit random keys on the keyboard, tried the arrow-keys, but nothing seemed to provoke any reaction except for the reroll thing.

IIGS_User, did you have the same problems that I had with choppy/crackling sound when GUS was used for digital sound? SB16 worked better for me. And I couldn't get the MPU-401 device to work for MIDI sound. Again, the SB16 worked fine.

If I set the GUS settings like set in conf before, the setup program test was done with success. if I set wrong GUS settings in the setup program, it terminated when attempt to try the setting.

MIDI plays good (in DOSBox newer seen that port adresses for MIDI are changeable), when port is set to 330.

Oh, I made this test within the setup program. 😉

IIGS_User wrote:

If I set the GUS settings like set in conf before, the setup program test was done with success. if I set wrong GUS settings in the setup program, it terminated when attempt to try the setting.

MIDI plays good (in DOSBox newer seen that port adresses for MIDI are changeable), when port is set to 330.

Oh, I made this test within the setup program. 😉

Repeated the setup with the 0.71rc1 version - same problem. GUS sound is choppy, and no sound when choosing MPU-401 for MIDI.

Also notices that the MIDI sound was louder when choosing SB and SB Pro, than when choosing SB-16.

MiniMax wrote:

Also notices that the MIDI sound was louder when choosing SB and SB Pro, than when choosing SB-16.

Not 100% sure about MIDI, but that's normal when it comes to digital sounds, and how my SB16 behaves on my 486. It always seem to be louder while working in 8bit mode. DMA have an affect on it too IIRC.

I just installed the Daggerfall demo in DOSBox 0.7 in XP and it seems to work just fine.

I put the DAG folder from the demo in the same directory where DOSBox is, and mounted it with "MOUNT D DAG -t cdrom", and installed the game to the mounted C. Set up the sound to use SB16 P220, D1 and I7. MIDI is MPU-401 port 330.

Then I edited the conf file to give me 40mb. Shouldn't be needed but Daggerfall is a relatively RAM hungry program for being a DOS game.

Then I just ran it with no problems, and could distribute my points during the character generation by clicking with my mouse on the arrows near the attributes and then start the game.

For those who wants to skip the character generation, there are some saves shipped with the demo that you can load right away.

MiniMax wrote:

Repeated the setup with the 0.71rc1 version - same problem. GUS sound is choppy, and no sound when choosing MPU-401 for MIDI.

You're right, it happens with 0.71rc1, too. The gamer have to know what are the settings, as like as in the DOS years before. 🤑

IIGS_User + Freddo - I must be doing something terrible wrong, because I get no MIDI-sound when choosing the MPU-401. I am using a standard, non-modified dosbox.conf (except fwor the gus=false), and the demo from the link in this thread. What am I doing wrong?

How do your HMISET.CFG look like?

When the setup is about to try to play a MIDI sample, it does.

The content of HMISET.CFG in my configuration:

[DIGITAL] […]
Show full quote

[DIGITAL]

DeviceName = Gravis UltraSound

DeviceIRQ = 5

DeviceDMA = 1

DevicePort = 0x240

DeviceID = 0xe024

[MIDI]

DeviceName = MPU-401

DevicePort = 0x330

DeviceID = 0xa001

I'm using the normal 0.7 release for Windows. No CVS or anything. Only change I've done with dosbox.conf is to give it 40mb of RAM. The HMISET.CFG looks like this.

[DIGITAL]
DeviceName = Sound Blaster 16/AWE32
DeviceIRQ = 7
DeviceDMA = 1
DevicePort = 0x220
DeviceID = 0xe016

[MIDI]
DeviceName = MPU-401
DevicePort = 0x330
DeviceID = 0xa001

Thanks guys, I got the MIDI sound to work - kind of 🙁

Seems like I have a weird bug on my system. Whenever I exit Windows Media Player it will turn the volume of my MIDI/Synthesizer device (in the sound volume control panel) down to zero.

When I then open an MIDI file with any of my media players (wmplayer.exe, mplayer2.exe or realplay.exe) the player will automatically adjust the Synth volume so I can hear the MIDI file. It looks like each player adjusts the volume to match its local volume slider.

But DOSBox will not adjust/raise the volume, so all I get from DOSBox is silence until I manually raises the volume.

dxdiag.exe has the same problem if I choose the emulated Microsoft MIDI Mapper or the Microsoft GS Wavetable SW Synth devices.

Could you guys try to open your volume control panel and see if your players messes around with the volume settings, and if DOSBox is - or is not - adjusting the MIDI volume on your PC's?

I don't know, but I found a freeware MIDI player called "MIDIMACH" for DOS which works fine within DOSBox:
http://209.85.135.104/search?q=cache:v81eJkyJ … clnk&cd=1&gl=de

You may check MIDI functionality with such a utility. 😉