PCI compliance refers to the law around financial transactions, specifically credit/debit card transactions. A certain level of security is required in order to be allowed to facilitate these transactions. If you accept payments via credit card and want to run them through your sever, then the connection between your server and the payment network must have a minimum required level of security.
 
This security is encoded in the transfer protocol between your server and the payment network, which is called “Transport Layer Security”, also known as “TLS”. Because of recent changes in the law, you must have the most up-to-date version of TLS (at least version 1.2). You will fail a PCI compliance certification if you do not have the right version of TLS.
 
Additionally, this TLS update can affect some other programs on your server. Specifically, this can affect your ability to log in to your server remotely via a program called SSH (“Secure Socket Shell”). The most up-to-date version of SSH available on legacy versions of SCO (i.e., 5.05, 5.06, 5.07, 5.07V, and 6.0) does not play well with the necessary TLS version. Contact us to get a custom version of SSH that works with legacy versions of SCO that also meets PCI compliance standards.

The master boot record which starts the operating system is missing.  To correct insert the floppy disk, turn on the server and choose the floppy drive as your boot device.  At the Boot prompt enter  hd(40)unix which direct the system to boot from the kernel on the hard drive.  Boot into single user mode and type dparam -w which will direct the system to rewrite the master boot record.  Remove the floppy and reboot the server, the system should boot normally.

This works on SCO UNIX 3.2.4.2, SCO 5.0, 5.2, 5.4, 5,5, 5,6, 5,7 and 6.0

System starts to boot does not complete and give the following error:

NOTICE: aacraid #0: Adapter Shutdown

WARNING: aac_comm_shutdown: send_sync_fib_failed

Suggest you examine any usb devices plugged into the server and remove devices except for the keyboard and mouse.

This works on SCO UNIX 6.0

The hard drive might have failed.  If using an IDE hard drive, verify the BIOS setting for the hard drive are correct.  The boot sector of the hard drive might be corrupted by a hardware failure or a boot sector virus.  Try placing a boot floppy in the drive and at the boot prompt type 

for UNIX      hd(40)unix swap=hd(41) dump=hd(41) root=hd(42)
for Xenix     hd(40)xenix


If the system does boot, copy the boot command off the floppy drive onto the hard drive and test by rebooting.
                         /etc/mount -r /dev/install /mnt
                         /bin/cp /mnt/boot /boot
                         /etc/umount /dev/install

Make sure the floppy disk drive and CD device is empty.  Unplug all USB devices except for the keyboard and mouse.

This error might appear when a system is being booted.  The error means a device on the server cannot start because the IRQ configured for that device is already being used.  Typically that means the bios was reset and on-board devices are using that IRQ.  Change the bios to reserve that IRQ needed for UNIX as a ISA device.  This tells the motherboard it cannot use that IRQ for their internal devices.  Try rebooting the system again and adjust as needed.

NOTICE: Sdsk: Unrecoverable error reading SCSI disk 0 dev 1/42 (ha=0 bus=0 id=0 lun=0) block=806534

Medium error

NOTICE: Sdsk: Unrecoverable error reading SCSI disk 0 dev 1/42 (ha=0 bus=0 id=0 lun=0) block=806536

Medium error

The error above indicates the hard drive identified as SCSI ID0 is failing and should be replaced.  These errors might occur for months before total failure.  Data on a bad area of the hard drive would be lost and backups will become less useful as they are rotated and written over with new data.

Check the bios of the motherboard to ensure the IDE hard drive controller is enabled and set the hard drives to auto recognize.  If the system stills does not boot, pull the drive and see if there are settings listed on the label.  The drive should run at it's defaults but older versions of the operating system might require different settings.  This might be due to the operating system only able to recognize partitions limited to a specific size such as SCO Xenix which has a 1GB limit.

Another parameter you can try adjusting is the hard drive mode.  The three typical modes are

• LBA  - Logical Block Addressing
• Normal or CHS
• Large - Uses translation to ensure the number of cyl is less than 1024
• Auto - Automatically detect and set the mode.

Try setting the mode first to Normal and see if the system boots.   Work through the modes and see if any of the different modes allows you to boot.

This is typically found on SCO Xenix and SCO UNIX 3.2v4.2, 5.0, 5.2, 5.4.

This means your main partition of the hard drive has run out of space.  Any error of no space on /dev/?? should be investigated.  This could cause services not to start or run such as printers, applications, and user login sessions.   Look at system logs for files that could be cleared.

Check the date on the server or in the CMOS. This error typically appears if the system date is less than June 1, 1995. This was put in the operating to prevent software piracy.

This is valid for SCO UNIX 5.0, 5.2, 5.4, 5.5, 5.6, and 6.0.

This is typically caused by a read-only root filesystem, lack of valid user licenses, or damaged files in the /etc/ifor_pmd directory.  The CMOS or system date can also be incorrect causing a licensing issue.

If the CMOS date is correct, contact us for help in resolving this issue.