VOGONS


First post, by Tofystedeth

User metadata
Rank Newbie
Rank
Newbie

I'm running Win 7x64, so I have to run Ragnarok in DOSBox. It works fine, except for when I try to use the dimension travel power, it crashes with a runtime error every time.
runtime error 002 at 0435:8398

I've fiddled with basically every memory, graphics, cpu, and sound setting to no avail.

Reply 2 of 9, by Tofystedeth

User metadata
Rank Newbie
Rank
Newbie

Doesn't do anything. I've tried all the emulation core and CPU types as well.

Reply 3 of 9, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Runtime error 002 is "file not found", so if you get the error before hearing the sound effect for dimension travel then you're probably missing the associated .SND file. Maybe try installing again. You could also use a debugger build of DOSBox to see what file the game is trying to access when the error occurs.

Reply 4 of 9, by Tofystedeth

User metadata
Rank Newbie
Rank
Newbie

Huh, it didn't alert me this time when a reply was done. Sorry for the late response.
I was figuring it was either a sound or graphics issue, since the dimension travel screen contains the only actual animation. I tried installing the Valhalla version of the game, which has sound, and it works, so that would lend credence to your theory. Unfortunately you can't transfer saves between them, and the valhalla version has other problems when running on my laptop (XP Home) which has the same dimension travel problem. I wonder if they just forgot to remove the reference to the sound file in that part of the game when they stripped the sounds out of the free Ragnarok release.

I'll try copying the .snd files from Valhalla over. Failing that, I'll use the debugger build. Thanks. I'll report back if successful.

Reply 5 of 9, by Tofystedeth

User metadata
Rank Newbie
Rank
Newbie

Well, that didn't work, and after looking at the guide for debugger version I'm gonna pass that up since it's been ages since I've done anything with assembly. I'll guess I'll have to forgo the crossroads for now.

Reply 6 of 9, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

There seems to be quite a few versions of the game. Which version are you posting about?

From what I gather, the dimension travel ability is not something you start the game with, and has to be acquired. In order to reproduce the problem more easily, perhaps you can attach a zip of your save files with a character possessing the ability.

Reply 7 of 9, by Tofystedeth

User metadata
Rank Newbie
Rank
Newbie

Okay, I had ProcMon monitor DOSbox.exe for file access and the last file it tried to access before shutting down due to program failure was LEVEL.107, which doesn't exist. I think it creates a LEVEL.# file for every map screen you go to, as you need them, so I'm not sure why this is failing.
I'm running Ragnarok 2.5, which is the latest of the US version that is freely available. It's the one most places, such as here or here where I've gotten it on both computers having this issue. Should be identical. I've attached a zip with the sdata and rag_save files for a character with the Dimension Travel power, and it also has all the LEVEL.# files for him, but I don't think they're strictly necessary.

Thanks

Reply 8 of 9, by Tofystedeth

User metadata
Rank Newbie
Rank
Newbie

hah! I got it. I was misremembering the ProcMon results when I moved between ProcMon and looking in the Ragnarok install folder. The file it was looking for was not LEVEL.107 but 107.MAP and subsequently 107.UP. These are the file names the Valhalla version uses. I don't know why it randomly wants the different file, but dumping in those two from the Valhalla install seems to make everything work okay. I guess we can call this case closed for now.

Thanks for your help. Knowing it was a missing file issue really helped me know where to look.

Oh color me embarrassed. Those files, along with another pair were included in the rag25 zip, but for whatever reason I'd deleted them, probably because you used to not need any of those .map files back in the day cause it made its own. It's still strange that those few would be required in that version.

Reply 9 of 9, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Was about to write that I can't reproduce the problem, but seems you've got it sorted now. I suggested reinstalling before resorting to the debugger build, but perhaps your mindset regarding what files could safely be deleted from the distribution would have led to the same result anyway.