Page 1 of 1

IFL TBIView cannot open shared object file

Posted: Thu Sep 20, 2018 5:51 pm
by JSladek
I am using a Debian variant of Linux and I trying to use the Linux version of TBIView. Whenever I attempt to start the program, I get the following error message: "error while loading shared libraries: libncursesw.so.5: cannot open shared object file: No such file or directory"

The library file does indeed exist at /lib/x86_64-linux-gnu/ and I have tried placing a link in /lib, but it still fails with the same message. It also does not make any difference whether I install TBIView in root or home - same problem.

For years I have used the DOS version of TBIView under WINE with no difficulty, but since apps under WINE are slow to start up, I thought I'd give the Linux version a shot. Seems like I've been down this road before, however.

Any suggestions?

Re: IFL TBIView cannot open shared object file

Posted: Thu Sep 20, 2018 8:42 pm
by TeraByte Support
you need the 32bit library - this has more than you need but you'll get the
idea: https://www.terabyteunlimited.com/kb/article.php?id=566



"JSladek" wrote in message news:15735@public.image...

I am using a Debian variant of Linux and I trying to use the Linux version
of TBIView. Whenever I attempt to start the program, I get the following
error message: "error while loading shared libraries: libncursesw.so.5:
cannot open shared object file: No such file or directory"

The library file does indeed exist at /lib/x86_64-linux-gnu/ and I have
tried placing a link in /lib, but it still fails with the same message. It
also does not make any difference whether I install TBIView in root or
home - same problem.

For years I have used the DOS version of TBIView under WINE with no
difficulty, but since apps under WINE are slow to start up, I thought I'd
give the Linux version a shot. Seems like I've been down this road before,
however.

Any suggestions?


Re: IFL TBIView cannot open shared object file {resolved}

Posted: Thu Sep 20, 2018 10:34 pm
by JSladek
That did it, but now that I've seen it, I think I'll stay with the DOS/Windows version and continue to run it under WINE. I felt like I stepped back 20 years with the Linux version. Sure get spoiled with GUI.

Thanks.