Shared Library Error---explanation?

Question

Shared Library Error---explanation?

I have a new 8-core MP with a clean install, no migration. Permissions repaired and disk checks out fine.
There is an OSX port of an "old" game: Unreal Tournament 99, which had run just fine on my old G4, and seems to run fine on Intel Macs owned by friends, but (fresh install) when I try to launch the app I get this error message:

The application "Unreal Tournament" could not be launched because of a shared library error: "<Unreal Tournament OS X><OpenALLibraryCarbon><StdCLib>"

Any thoughts/interpretation?
Thanks.

MacPro 2x3.0 GHz Quad-Core/4GB RAM/Radeon X1900, Mac OS X (10.4.10)

Posted on Aug 16, 2007 9:33 AM

Reply

Answer 1

The hatter

Level 9

61,031 points

Aug 16, 2007 9:40 AM in response to Joseph Wiedermann

Is it a Universal Binary program? probably not.
Is there an option to open it under Rosetta (Get Info) if it was UB.
Does it require any drivers or extensions?
Does it need or use an Install?

Was it a "Classic OS 9" application? Classic doesn't exist, and while there is "Sheep Saver" I've never run across any comments about it.
http://www.uneasysilence.com/archive/2006/08/7352/

Reply

Answer 2

Aug 16, 2007 9:47 AM in response to The hatter

It's an old OS9 program with an OSX port, no installer. The files have to be manually placed in the app's folder. All of this done according to instruction, and had previously worked fine under OSX on my G4, as well as on Intel machines owned by others. That's why I don't get the failure to launch, and the particular error message strikes me as ominous, though perhaps I'm just anxious about my new baby.

Reply

Answer 3

Aug 16, 2007 9:52 AM in response to Joseph Wiedermann

Mac OS 9 applications are not supported, at least by Apple, on Intel systems. To get these applications to work you need an environment, such as is provided by SheepShaver…

http://gwenole.beauchesne.info/projects/sheepshaver/

…, for them to work.

Reply

Answer 4

Aug 16, 2007 10:04 AM in response to infinite vortex

Nah, this thing ran fine on OSX through the port. It doesn't need Sheepshaver (which I have used for other things). The thing that troubles me is the particular error message. Should it worry me about the machine itself?

Reply

Answer 5

Kappy

Level 10

362,007 points

Aug 16, 2007 10:14 AM in response to Joseph Wiedermann

Visit The XLab FAQs and read the FAQ on resolving shared library errors. These usually arise with older Carbon-based programs.

Reply

Answer 6

Aug 16, 2007 1:00 PM in response to Kappy

Hmm. The FAQ above seems to suggest that Archive&Install might fix the problem, at least it does so for some applications that fail to launch and generate this error message. I'm a bit reluctant to do this with a 2 week old computer where the install was clean--what do you folks think?

Reply

Answer 7

Fredrokk

Level 1

8 points

Aug 23, 2007 1:48 PM in response to Joseph Wiedermann

sorry, a double reply..

Message was edited by: Fredrokk

Reply

Answer 8

Fredrokk

Level 1

8 points

Aug 23, 2007 1:44 PM in response to Joseph Wiedermann

Nah, can't be. Just want to add that I have the same problem on my new mini. Same thing fresh install of both os and UT. The thing is that I can run exactly the same installation of UT on my G5 1,8, but on my intel mini I got the same error as Joseph.
Just a note: I had problems playing the PC version on my bootcamp XP on the same mini, it turned out that I had to disable one of the cores in my duo-processor to make it work... Will the same problem occure with os x?

Reply

Answer 9

Aug 25, 2007 3:57 PM in response to Joseph Wiedermann

Yeah, I'm getting this error too on a C2D MacBook, fresh OS install, fresh UT install. Any thoughts?

Reply

Answer 10

Zevlag

Level 1

10 points

Sep 28, 2007 3:59 PM in response to Joseph Wiedermann

1 week ago UT was also working on my Macbook. Due to a hard drive that was getting full, and just randomness I decided to do a fresh install of OS X, not I receive the same error that you do trying to run UT.

I'm guessing that some program that I had installed prveiously had installed an updated version of a library of framework that supported UT. From here I don't know where to go. My hunches point towards fink, maybe a new verison of OpenAL or something.

Reply

Answer 11

Nov 1, 2007 4:54 AM in response to Joseph Wiedermann

Joseph, I have the same problem on my Core2Duo Macbook, clean OS. It's definitely not a problem with OS X - at least, I don't think reinstalling the OS will fix it.

Hopefully they get some info about this out soon, because I want to play some UT.

Reply

Answer 12

The hatter

Level 9

61,031 points

Nov 1, 2007 6:01 AM in response to Fredrokk

If it isn't a UB, and it worked on PPC, then it probably needs Rosetta, no?

OS X shouldn't care, nor should a program... but you are looking a dual-cpu, octo-core.

Reply

Answer 13

Nov 14, 2007 4:51 AM in response to Joseph Wiedermann

I also had this error.
I had used Migration Assistant originally, so I clean installed 10.4.10 - still errored.

On migrating (or clean installing) to Leopard, the programs worked perfectly.

Unfortunately, I need to stay in Tiger for the present time, so I Googled "StdCLib," and found this page:

http://www.wide-screen.com/sunPATH/MacOSXfix.shtml

"StdCLib Bug"
"A bug has been discovered in some MacOS X 10.4.10 Intel systems.
It appears in some new computers sold after June 1st 2007"

.. and the page has a link to an Applescript which corrects the bug - all my programs are now working.

Reply

Answer 14

Nov 14, 2007 6:19 AM in response to John Palmer

Thanks John, that DID fix the shared library error - however I'm now getting a new error.

The UT splash screen appears, along with what is loading ("linking objects", etc), but then I get a dialog box saying "Unable to find Draw Sprocket context:", and after clicking 'ok' I get a crash to desktop.

Any ideas?

Reply

Answer 15

Nov 14, 2007 6:31 AM in response to John Palmer

UPDATE:

Found a solution to the DrawSprocket problem - it's caused by UT trying to use an unsupported resolution. The full solution is here:

http://forums.beyondunreal.com/showthread.php?t=40134

It basically just involves editing your UnrealTournament.ini file.

I can now play the game, anyway. However, the music doesn't work.... :S

Reply