>>I have recently upgraded our IPC from OW 2.0 to OW 3.0 so that I might run SunPHIGS 2.0. However, someone is still using SUNVISION 1.0 which ran under OW 2.0. Now, when he runs any of the SUNVISION software, the message :
>
>>Waiting for database program to start
>
>>is printed continously and nothing else happens. Does anyone have a clue on how to rectify this problem - I can possibly get hold of SUNVISION 1.2 if it will help.
>
>>Thank you for your attention !
>
>>Jeremy Bennett
>--------------------
>I have been facing the same problem and has contacted SUN support in that
>regard. They responded that SunVision 1.0 doesn't run under OpenWindows 3.0 and
>that an update to version 1.2 is needed. That what we are going to do.
>
>Many SunVision users out there in net-land? Time for a news group?
Well, from my experience the above is only mostly true. Sunvision 1.0 really
only needs the OpenWindows 2.0 libraries to run so if you set your environment
variable LD_LIBRARY_PATH to point to the 2.0 libs instead of the 3.0 libs you
are fine. You should be able to get rid of the rest of 2.0 and just keep the
libs around.
As for the error you are experiencing, that is a different matter. According
to Sun, SunVision 1.1 (and likely 1.0) will fail to start up the database
if the machine name is longer than 20 characters (which it normally is when
consider the whole name, i.e. name.whatever.whatever.etc). It seems they hard
coded the name string and it only has room for 20 characters. I had a working
copy of both 1.0 and 1.1 which broke in this manner after an upgrade. Why the
upgrade made SunVision start using the whole name and having this problem I
don't know. It is fixed in 1.2 as are many of the other bugs.
