Mac OS

Ask something
Discussion Locked

Application Launch Failure

0 helpful
6 replies

by tilsharic

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Trying to launch Omnis 7 in OS 10.2.6 returns the message:
The application "(null)" could not be launched because of a shared library error: **<>"

Anyone have suggestions on how to get this working?

6 replies

by lyon_bleu

First of all, check with the support:

http://www.omnis.net/support/programs/uk7info.html

"ObjectSupportLib" is an artefact of OS 9.x [actually, it goes
back to System 7, but that's another story 8^) ]. Reveal the file
in Finder and get info [cmd-I] on it and verify that the app is
_not_ flagged for launch as a "Classic" application. [Under OS X,
"Classic" means emulated OS 9.x]

Standard Operating Procedure [SOP] under mac OS X is to run
Disk Utility and "Repair Disk Permissions" under the "First Aid"
tab after every installation or upgrade. Do it and be glad.

HTH

by tilsharic

The support site (which I had already looked at) didn't have any information that I could find. Very poor site.

We have a custom permissions script that we use. "Repair Disk Permissions" breaks programs on us for our normal non-admin users.

by lyon_bleu

I need to correct an error I made above: Omnis 7 _must_ run as
a Classic app.

From the error message it would seem that Omnis 7 is looking
for ObjectSupportLib as a separate file at the root of its
containing folder. [ObjectSupportLib has been part of the
System file since OS 8.]

To get a copy of this file and test this solution, you'll need to
download a part of the System 7.6.1 update

then extract the file from the archive using the utility
TomeViewer

HTH.

by tilsharic

Much more polite answer.

The answer above led me to run as a classic app already. Every one of our other classic apps automaticly started classic we overlooked that checkbox. Checking it off solved the problem.

This discussion is closed to new replies.