Error with OpenAL.dll

[Akiran]

After downloading and saving the unzipped OpenAL32.dll file into my PlaneShift directory, I got this error message:

"Procedure entry point alcGetSTring could not be located in the dynamic library OpenAL32.dll"

I then changed the updaterinfor.xml file according to what the forum directed and tried to run the updater. After a while, I get the message that there are

"no active mirrors! Check the forum for help"

Please help me out with these 2 problems?

[Adder]

a) You can get a working version of the DLL from http://www.openal.org/ (installs into system32, copy from there into PlaneShift)

b) Or, better, you can try again to run the updater. It should work eventually if you give it a break.

DLLheaven and similar sites don't necessarily have the right versions of DLLs.

[Akiran]

I'm not very computer literate... After installing the software from the website, I still cant find the OpenAL32.dll in System32. When I run my updater, A new message appears:

"Can't open xml file '/this/updaterinfo.xml'!
Unable to get root node"

Please help

[Adder]

a) post the contents of your updaterinfo.xml file; maybe you made a mistake when editing it

b) if the file updaterinfo.xml is really gone, uninstall, re-install, and run the updater

[Akiran]

Updaterinfo.xml Before:
<config active="false">
    <mirrors>
        <mirror id="1" name="psmirror" url="http://www.psmirror.org/repo/" />
        <mirror id="2" name="xordan" url="http://www.xordan.com/psupdater/" />
    </mirrors>
    <updater version="5" md5win32="09402c47615f480ba780e490d26c1f7b" md5linux32="1d4036c392c6fef5219afd3ce85b1d41" md5linux64="63b74fcf6d69e348020208054c7a7629" md5macosx="2b1fa3d1c44f2961cd1c7d7608106810" md5macosx1039="77e81133303fea8fbe2baef456a18c44" />
    <client>
        <version name="0.4.00" md5win32="ce76fa5127532ed1aeb69921316605e7" md5linux32="3fa44e9769af561caecfc8752fa38808" md5linux64="d081fd3f95433a0eba9259b10607abd9" md5macosx="7e2105679a7f8e419038073ddb01c47e" />
        <version name="0.4.00.1" md5win32="42e1a6d8e1bb72b9f62b6fcd3fc6aeef" md5linux32="9b4c6471539d77306911ea355fc39b1a" md5linux64="16e412ddfe4c827846b50d7c9b83e3ab" md5macosx="43d11aeee2a887f60763e9d0936e6968" />
        <version name="0.4.01" md5win32="8e82bd5cd4f04897ac145021c7b1ecd8" md5linux32="ee9f1a14572760860dc0d0b6e2f21f90" md5linux64="a109a34de89cf6abca3cdcf2ff574f75" md5macosx="0a8f1b99e6fbdaabb4387946e0ee346a" md5macosx1039="ba1b5a3557bc372527777c7ccbcead37" md5generic="0e3cb53fed43d684fc33761a5f0af263" />
    </client>
</config>

Updaterinfo.xml After:
<config active="true">
    <mirrors>
        <mirror id="1" name="psmirror" url="http://www.psmirror.org/repo/" />
        <mirror id="2" name="xordan" url="http://www.xordan.com/psupdater/" />
    </mirrors>
    <updater version="5" md5win32="09402c47615f480ba780e490d26c1f7b" md5linux32="1d4036c392c6fef5219afd3ce85b1d41" md5linux64="63b74fcf6d69e348020208054c7a7629" md5macosx="2b1fa3d1c44f2961cd1c7d7608106810" md5macosx1039="77e81133303fea8fbe2baef456a18c44" />
    <client>
        <version name="0.4.00" md5win32="ce76fa5127532ed1aeb69921316605e7" md5linux32="3fa44e9769af561caecfc8752fa38808" md5linux64="d081fd3f95433a0eba9259b10607abd9" md5macosx="7e2105679a7f8e419038073ddb01c47e" />
        <version name="0.4.00.1" md5win32="42e1a6d8e1bb72b9f62b6fcd3fc6aeef" md5linux32="9b4c6471539d77306911ea355fc39b1a" md5linux64="16e412ddfe4c827846b50d7c9b83e3ab" md5macosx="43d11aeee2a887f60763e9d0936e6968" />
        <version name="0.4.01" md5win32="8e82bd5cd4f04897ac145021c7b1ecd8" md5linux32="ee9f1a14572760860dc0d0b6e2f21f90" md5linux64="a109a34de89cf6abca3cdcf2ff574f75" md5macosx="0a8f1b99e6fbdaabb4387946e0ee346a" md5macosx1039="ba1b5a3557bc372527777c7ccbcead37" md5generic="0e3cb53fed43d684fc33761a5f0af263" />
    </client>
</config>

Please advise if there is anything more to do

[Adder]

Looks like valid XML. Maybe try again - the file might have been locked by the Editor you have edited it with.

A workaround is to find C:\WINDOWS\system32\OpenAL32.dll or C:\WINNT\system32\OpenAL32.dll and copy it to the directory where updaterinfo.xml resides, but you still will want to run the Updater to fix some bugs in the release.