your configfile please

The dosbox.conf is attached.

Try increasing the memsize
leave core on auto btw else it will be slow.

Ok, now the error has changed to:

Daggerfall has detected the error 0.
Press RETURN TO quit...

Pressing return won't do anything.

So, I've got it to work now, by using an unofficial patch.
Still, thanks for your help.

Can anybody reproduce this error? Related to mounting a directory as cdrom??

No, the directory mounting as cdrom is per the Bethesda guidelines and works fine. Not sure what's wrong here. cpytype=normal is incorrect, but I doubt that could cause any problems? FWIW, my DBGL gamepack is also made using the steps from Bethesda, and works without problems on Fedora.

longdouble wrote:

Daggerfall has detected the error 0.
Press RETURN TO quit...

Error 0 means that the paths in Z.CFG are wrong, which means you didn't install the game correctly.

Thanks, and the causeway error is related to the memory size only? Reproducable that way on a real system?

cpytype=normal is incorrect

I noticed that too.
It was because some guide said, that you should "set the cpu to normal" so I just assumed, it would be this option...

Thanks, and the causeway error is related to the memory size only? Reproducable that way on a real system?

I don't think so, it might have something to do with dagger.exe not recognizing the config file, because when just executing dagger.exe, it outputs the causeway error, but when executing fall.exe z.cfg, it outputs the error 0.

longdouble wrote:

It was because some guide said, that you should "set the cpu to normal" so I just assumed, it would be this option...

The normal core works fine. The reason why older guides recommend the normal core, is because back in the DOSBox 0.65 days (or whenever it was), the dynamic core didn't work well with Daggerfall and caused graphical glitches.

wd wrote:

Thanks, and the causeway error is related to the memory size only? Reproducable that way on a real system?

I don't think it's reproducible on a real system, not even in DOSBox. I just installed Daggerfall 1.0.165 in DOSBox 0.74 and ran with memsize 16 and the game launched just fine. I've also played Daggerfall on a real 16MB DOS system for hundreds of hours and don't recall of ever getting any "CauseWay error 01". While error 0 is fairly common.

I have absolutely no idea what longdouble may have done to get the CauseWay error. There is an "UNABLE TO ALLOCATE OBJECT MEMORY", but it's obviously not the same, and was fixed in a patch anyway.

Unpatched Daggerfall should be very much avoided, as it's buggy as hell. The first thing anyone should do is to install the latest 1.07.213 patch, although I didn't do that now to see if the CauseWay error would appear in the unpatched Daggerfall, but it didn't.

Thanks for checking this out.

Freddo wrote:

The normal core works fine.

cputype was set to normal (not core), which is an invalid value for this entry.