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.

Yes, I can but it didn't work to change the date. That error keeps on happening

---------- Post updated at 09:36 AM ---------- Previous update was at 09:32 AM ----------

This is the first time I use an sco ( i only had used linux so far) but I think is a 5.0 version.

@gallok, What is the output of 'uname -X'

date says that the century is optional.

date -t [[CC]YYMM....

that system was bought in 1998. Then in year 2000 the original manufacturer of the system (which now does not longer exists) has done something to make the system y2k compliant.

that was all long bevore my time. the system runned until 2009, then the hardware gived up and it was transformed into a vmware.

i tooked the work to my home, and then started it in an virtualbox. there it is running. On the virtualbox on the work the fork errors appeared.

working virtualbox (@home): version 4.2.2 r18
nonworking virtualbox (@work): 4.3.20 r96997
@work it should run on an vmware server 1.09, as it did since 2009

@jgt uname -x says not found but uname -r says 3.2
It's a SCO openserver enterprise 5.0.2c (swconfig command)

I think your system supplier made their application code y2k compliant.
Either way, I don't see any solution to your problem that does not involve upgrading the OS version.

it is uname -X not uname -x. case is important.