Problem with exult.cfg and path setting

[Beni]

I have a problem... when I install any Snapshot version above the latest beta (I think it was 0.96 beta 1 or so) Exult messes up my path setting automatically. Using long directory names makes it impossible to run Exult.

For Example my exult.cfg looks like this before I install the snapshot(s):






d:\ultima series\ultima vii - the black gate


(default)


jmsfx.flx




d:\ultima series\ultima vii - the serpent isle


(default)


jmsisfx.flx





But after I apply the snapshot it get's changed into following and if I replace the cfg with my old one, it get's "converted" as well... *frowns*


config>




d:\ultima
series\ultima
vii
-
the
black
gate


(default)


jmsfx.flx




d:\ultima
series\ultima
vii
-
the
serpent
isle


(default)


jmsisfx.flx





Sometimes even when I use short directory names (e.g. D:\Ultima\Serpent\) it won't initialize... what's wrong? Anyone out there who might be able to help me out? Thank you... only the snapshots above the latest beta (as mentioned before) ... and besides, I use WinXP Professional... ... ... *sighs*

[nadir]

Spaces in paths ??? Bad idea...
I don't think we suport that

[co]

you could try the short names in the cfg, eg. c:\ultima~1\...

[Beni]

Nadir, that "spaces in path" were working with the 0.96 beta 3 (think that's the version) .... but not with snapshots... *frowns*

[fliptw]

use the short names, or get rid of the spaces. spaces are just a bad idea in filenames.

[nadir]

Darke has been doing some work on our XML parser, so it might be that things have changed slightly.

[Colourless]

Just checking this myself, it does appear to be a bug. Untill it is fixed, dont use a space in your paths

-Colourless Dragon

[Natas]

Hi I have a similar problem when I try to install exult with Ultima7/SI in other directories in my IBM Aptiva '99 (Windows 95). But with my newer computer (Windows ME) seems to be alright...

Keep up the incredible work

Edgar Kausel
Chile, South America

[Natas]

I forgot saying that the path is setted when I install Exult, as I'm not very expert editing the exult.cfg. Is it alright?

[Beni]

My paths were set both ways ... during installation and by editing the exult.cfg ... so you think it's rather a bug than just a change in something "internal" ? ...

[Colourless]

This problem should now be fixed.

-Colourless Dragon

[Beni]

Hell yeah, it works now! Thanks a lot! Good work mate! *smirks*

[Colourless]

Heh, I didn't actually fix the problem. I was just announcing that it had been fixed.

-Colourless Dragon

[Beni]

Read it in the changelog.txt but still, I'm happy as f*** (erm... *coughs* ... not well selected language, I s'pose but still...) and that's why I thank everyone who's around ... Heh!

[Natas]

When you say "This problem should now be fixed" is that if I download again the beta 0.96 version should be OK. Why don't you change the version name, then?

[XxVenomxX]

Nope, it means if you download the current snapshot, it'll be fixed. Each snapshot is not an official release, thats why the version name doesn't change. Cuz it's not the snapshot

[Cory]

I had a similar problem, whereas Exult would quit on me as soon as I tried starting a new game. Like you, I had full path names in my exult.cfg file, just as they appear in my File Manager (with spaces, running Windows ME - i.e. c:\Program Files\Ultima VII Complete\ultima7). After changing the paths to DOS friendly names (i.e. c:\progra~1\ultima~1\ultima7), the game runs fine now. That's probably it.