OT: SCO/WordPerfect

[Bill Vermillion]

On Mon, Jun 07, 2004 at 08:37:17PM -0500, Linda Hapner thus
spoke:

> A few months ago I posted a question of getting WordPerfect
> 5.1 to work on SCO OS -- it was indicated that there was not a
> problem & some of you have done it.

> The folks that sold me the computer installed wp for me -- and
> it does come up fine. Once I got the system and am attaching
> printers, I'm finding some problems. I can't print as a user,
> only as root. Best that I can figure, the license daemons are
> not running, in fact the license.dat and two user daemons
> mentioned in the manual are not on the new system. I tried just
> copying these files over, and it may have been the cause of an
> unexpected crash today....not sure.

Going back to the system after posting my other message I see
soemthings you might check.

In the shbin10 directory the program 386cons needs to be
SUID root.  The permissions should look like this -r-sr-xr-x

To get that type  chmod 4555 386cons

As I recall [and with minor searching] that is the only SUID
program there, and not having the permissions correct will
give you the exact problem you are seeing.

I suspect they didn't follow the docs when installing

You mentioned 'copying the files over'.  Over from where?
If this is from an older system then the SUID bits were most likely
stripped if you just copied then instead of using something that
keeps permissions such as BackupEdge.

As to the daemons not running see my other post about setting the
startup in the your /etc/rc?? hierarchy.

On the WP 8 I have it the startup in /etc/rc2.d and have it as the
last thing happening.

In that script it cd's to /usr/wordperf/bin and then the next
line is   
./wpexec -s

Then the next line removes stale Dataflex lockfiles.  Leftover when
they had Dataflex and there is now Progress on the system. The old
dataflex files are still there for reference.

I see that I changed the directory of the wpexec file on 
September 2, 1999.   That was when we upgraded to the OSR 5.0.5 out
of a very old Xenix system.    The rest of the script had
a January 1, 1992 date on it.  I ALWAYS date and initial all
changes, and when I change a line I dupe it, comment out the old
one and have the new one directly below.

I can always grep a tree for my initials. I let the machine do my
remembering.

Hope this gets you started.

Was it running on an SCO 5.N system before.

Bill



-- 
Bill Vermillion - bv @ wjv . com