Try normal core.

Also try CVS build from my signature. You want ykhwong's build.

Also the cycles seem extremly low make sure your using cycles=auto.

Actually I find this game doesn't need too many cycles, I give it 25000 on normal core and it runs smooth. 😀 Albeit - I haven't played very long into the game in case certain areas slow it down.

I was using normal core, I noticed dynamic was slower.
I'll try with cycles=auto and the CVS build.

I don't know if I can increase much the cycle number though. I noticed sound problems when I tried.
25000 makes my CPU usage stuck at 100%... and I can't even walk and turn at the same time.

Thanks for the help!

Thats probably beyond your CPU's limit thats why.

heh. I keep on thinking the Athlon64 is so much faster than my XP 2800+ for some odd reason. Man I love this processor! 😀 (Soon to be dumped for a Core 2 Duo)

I have an athlon 64 too you know 😉 FX-53, and I can get well into 30000-40000 range. I would looove for something faster though to negate the use of VDMsound with build engine games.

Just to say I tried the CVS and it worked well.
With cycles=auto, there are peaks at only 20000-21000 cycles, but it's still playable.

That's the paradox with old games: I bought a PC equipped to run Oblivion, and I still have troubles to run Daggerfall 😀

Thanks again

Oblivion doesn't need the emulation layer 😉

nwart wrote:

Just to say I tried the CVS and it worked well. With cycles=auto, there are peaks at only 20000-21000 cycles, but it's still pla […]
Show full quote

Just to say I tried the CVS and it worked well.
With cycles=auto, there are peaks at only 20000-21000 cycles, but it's still playable.

That's the paradox with old games: I bought a PC equipped to run Oblivion, and I still have troubles to run Daggerfall 😀

Thanks again

Its also not a paradox, you are running an emulator. I also bet you aren't getting max details in oblivion with that CPU anyway. 😉

Sad, but true... Shadows and grass are killing my CPU 😢
Well I never said I expected it to run at full detail...

Btw, I know it's not a real "paradox" because dosBox has to emulate all the hardware of a PC with dos...
It's just hard to think that despite the always newer, faster hardware, it has become so hard to have these old programs to run again...
That's all what I mean (and I know it sounded naive 😉)

It IS a paradoxon but no contradiction.

Sorry to bother you again...

With Ykhwong's build, there are problems that didn't seem to appear in 0.63 or 0.65 releases...
The game often crashes, generally when trying to load or save a game (that results in a corrupted save). I had a few other crashes in game but I couldn't identify a cause.
I would have try a standard 0.65 CVS build to see if this comes from an experimental patch, but I couldn't find one (or hasn't been additions since 0.65 release?).

AEP builds clean cvs dosbox versions, see the development forum.

Yes, I tried it, but AEP's link is 404.

Indeed, sorry, the whole tree there seems to be down at the moment.
You could try gulikoza's build which should be rather new and only
adds selected well-tested additional stuff.
Other than that, you can compile the sources yourself.

nwart, try this fresh CVS build:

http://home.quicknet.nl/qn/prive/blankendaalr … load/dosbox.zip

Thanks, I'm trying this 😀

Edit:
No crash so far with this version.
The only small problem I have is I can't set cycles to auto, or the game never seems to start (I had this problem with the release too).