SCO

Dear jgt,

i thank you for sharing the iso with me.
After some problems with the blc driver (which is needed for the VMWare-SCSI controller), I did an successfull update on the 5.0.2 system to 5.0.6 and it seems to work, even with the right date.

Tomorrow, i can test the users test the entire parts of the 3rd-party software which has to run on the Server.

One more question do i have.
Do i really need the rs506a?
After installing it, some parts of the Software which is installed on the server does not work anymore.

Bevor the installation of rs506a i taked a snapshot. Reverting to it, the software works again.

Check here SCO Knowledge Center
Enter 'rs506a' in the search field, 'Open Server 5' in the product field and 'release 5.0.6' in the sub-product field.
There are 68 results. You might find a solution there, or gain enough insight to know the risks of not installing the patch, and whether they affect you.

dear jgt,
do you also have the resource cd for sco 5.0.6.
Some older daemons do not work properly after the upgrade to 5.0.6 (Samba and bootp-Daemon). I think i have to reinstall them
they start without an error, but then, they do not work. the samba shares, for example are not available.

if i try a telnet from outside the box to the port 139, the port seems to be available
but trying to reach a share i got only a timeout

The 'optional services' cd is on the same site as the OS cd.
5.0.6 shipped with visionfs rather than Samba.
If you use Samba, you can get the most recent copy from sco.com

We also have still a few customers who are running SCO 5.0.2. Another company has patched somehow the systems in 1999 to make them 2000 compliant. Now we have the same problem described in the previous posts.

@jgt: could you please send me instructions on howto upgrade to 5.0.6?

@ChipperEs: how did you manage it to run 5.0.2 under VMWare? Which VMWare product do you use? Which Harddisk controller did you choose? IDE or SCSI? Could you provide the appropriate SCO bootstrings (defbootstr) for that? And the btld images for the IDE/SCSI drivers?

Thanks,
Rainer

@retz
see post 24 in this thread.

Servus Rainer,

the sco box was virtualized into an vmware 1.0.9 server. this is an outdated product, like the sco server itself

I used Acronis true image to get the data into the vmware, by backuping (take a image, without compression) from the baremetal installation and restoring it on a vmware hard disk.

Set up your virtual machine as other / other, 256 MB ram, 1 CPU, SCSI HDD, Floppy drive, network.
You have to choose a (Buslogic) SCSI controller.

I have to admit, i cannot remember every little step i did in 2009 to get the sco box work.

On vmware 1.0.9 i had to use the pnt lan driver. you can get it from sco ftp.
On newer vmware you can use an intel nic driver like described here: VMware Documentation for SCO OpenServer 5.0

As i remember, i had to boot from a disk with the right scsi controller driver (blc). This should do it for actual VmWare ESX Server too.

i think this link could help you:
SCO Unix 5.0.4 on VMware <- Aplawrence

you have to load the boot disk (i think the Buslogic (blc) disk is bootable, see Aplawrence mmunix.exe or my images below for download), after that, install the driver using btldinstall. you can take the right defbootstr from the applawrence link.

the blc driver i used is extracted from the mmunix.exe (link on applawrence), written by a windows 98 virtualbox on a virtual floppy disk (blc_treiber.img 1,4Mb) and reduced by a linux using dd to 720kb (blc_treiber_red.img)

you need the reduced disk to mount it on the vmware (not on startup, just when you are using "mount" within the sco box). The full disk will not be recognized. that is because SCO somehow recognizes that this is a virtual floppy disk and so it accepts only 720 kb at run-time (not on startup)

here the links for the driver:
http://usb-culture.de/driver/blc_treiber.img
http://usb-culture.de/driver/blc_treiber_red.img