Re: SCO Unix 3.2.4.2 networking/licensing

It's been a long time since I've worked with SCO 3.2.4.2 and I've
encountered a remote system that I need to migrate off of and
networking is essential to the plan.

The system doesn't have networking installed and I'm worried that they
may not be licensed for it. I recall that some of what we would
consider to be standard options were extra licensed options back
then.

Does anyone remember if 3.2.4.2 included TCP/IP networking in the base
license?

I just hope I this customer has the original disks.

Products at that time included (among others) SCO Unix 3.2v4.2 and SCO
Open Desktop 3.0 / SCO Open Server 3.0. If someone bought the
standalone Unix package then they could buy TCP/IP as an addon (it would
have been SCO TCP/IP for Unix, version 1.2.1). Chances are, if they
have a TCP-less install, they bought the plain Unix package and did not
buy TCP/IP. If they bought Open Desktop / Open Server, I think it was
technically possible to run through an install of those and end up
without TCP/IP, if you told it you wanted full control over what was
installed and then deliberately omitted TCP/IP and all the things that
would have pulled it in; but it's very unlikely a user would have done
that. Why pay thousands of dollars more and then install it in a manner
which omits the extra cost options?

Why is networking essential to the plan? You could hook it up with a
serial cable to a Linux / etc. box next to it and use serial line UUCP;
you could do a hard disk transplant; you could back up to whatever tape
device they have (hopefully they have...) and then pull it in on a Linux
system -- you don't need two controllers/drives because Linux will
probably have drivers for the existing one. You could also probably
find someone to sell you a SCO TCP/IP 1.2.1 license (careful that you
get the Unix, not Xenix, version). Without knowing your reason that
networking is essential, I can't evaluate the relative merits of these
approaches...

Bela<
.

Relevant Pages