Sponsored Content
Operating Systems SCO Can I run Perkin Elmer software on SCO ? Post 302371396 by TonyLawrence on Saturday 14th of November 2009 02:27:40 PM
Old 11-14-2009
Quote:
Originally Posted by Neo
Ha! If that is the case, then Wiki says that SCO Open Desktop 2.0 is 3.2v4.1 1992.

So, can software for SCO 3.2v4.1 run on SCO OpenServer 5.0 3.2v5.0 1995 ? I assume it can.

Are these really the old 5" floppies? I can't understand the posts so well Smilie
Nor can we :-)

Most older SCO apps could transition to the 5.0.x versions. If there were obstacles, sometimes a little creative linking/ symlinking could resolve it, but in general, you have to need or want it very badly if it doesn't just pop up working. I can tell you that it would take a lot more than money to get me involved in anything like that today. In general, I strongly urge people toward Linux - and even (shudder) Windows if there is no other choice.

The stuff is just too hard to support. I fixed up an old SCO spreadsheet app to run on a 5.0.6 system some years back - for unexplained reasons it just stopped working last year. The people wanted me to fix it again - I just put my foot down and told them they had to move on because I wasn't going to mess with it again. They were not happy, but I was :-)

---------- Post updated at 02:27 PM ---------- Previous update was at 02:20 PM ----------

I found Peerkins Elmer software running on SCO:

EVISA Instrument database: Perkin-Elmer Corp. - Optima 3000

Bottom of the page:

Quote:
Operating Systems: SCO/UNIX ODT (multitasking & multiuser environment), MS-DOS, and Microsoft Windows.
So - he very well could have old SCO software. Again, could be xinstall, pkgadd or even just tar or cpio disks.
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How can i set up Software disk mirroring(Raid1) in SCO 5.0.5 with two SCSI harddisk ?

thank u very much, (1 Reply)
Discussion started by: coralsea
1 Replies

2. SCO

Software router on SCO Unixware 2.X

Hi, I am trying to setup an old SCO Unix 2.x box to act as a router. I have got 2 network cards in the box. As far as I know, I need to setup "ip forwarding" and "routes". Can anyone tell me how to setup "ip forwarding" on SCO Unixware 2.X? (0 Replies)
Discussion started by: sreenir
0 Replies

3. UNIX for Advanced & Expert Users

Netscape - What version will run on SCO Unix v3.2 2 Release 5

This question has been resolved. (0 Replies)
Discussion started by: system77
0 Replies

4. SCO

I need a box to run SCO 3.2 5.0.5 i386 with...

need it to be able to run Seagate STT8000A tape drive. Any suggestions where to go. (5 Replies)
Discussion started by: Mike Gomes
5 Replies

5. SCO

Recommendation for hardware to run SCO OSR 5.0.7 natively

Looking for a modern server to run SCO OSR 5.0.7 without VM (native), h/w must have manufacturers warranty. Requirements would be to accommodate light loads of up to 15 users, app does not take more than 30 - 40 MB of RAM and data stored takes up to 15 - 20 GB, no internet connections... (3 Replies)
Discussion started by: migurus
3 Replies
COMPAT_IBCS2(8) 					    BSD System Manager's Manual 					   COMPAT_IBCS2(8)

NAME
compat_ibcs2 -- setup procedure for running iBCS2 binaries DESCRIPTION
NetBSD supports running Intel Binary Compatibility Standard 2 (iBCS2) binaries. This only applies to i386 systems for now. Binaries are supported from SCO UNIX and other systems derived from AT&T System V Release 3 UNIX. iBCS2 support is only well tested using SCO binaries. XENIX binaries are also supported although not as well tested. SVR4 binaries are supported by the COMPAT_SVR4 option. iBCS2 supports COFF, ELF, and x.out (XENIX) binary formats. Binaries from SCO OpenServer (version 5.x) are the only ELF binaries that have been tested. Most programs should work, but not ones that use or depend on: kernel internal data structures STREAMS drivers (other than TCP/IP sockets) local X displays (uses a STREAMS pipe) virtual 8086 mode The iBCS2 compatibility feature is active for kernels compiled with the COMPAT_IBCS2 option enabled. If support for iBCS2 ELF executables is desired, the EXEC_ELF32 option should be enabled in addition to COMPAT_IBCS2. Many COFF-format programs and most ELF-format programs are dynamically linked. This means that you will also need the shared libraries that the program depends on. Also, you will need to create a ``shadow root'' directory for iBCS2 binaries on your NetBSD system. This directory is named /emul/ibcs2. Any file operations done by iBCS2 programs run under NetBSD will look in this directory first. So, if an iBCS2 pro- gram opens, for example, /etc/passwd, NetBSD will first try to open /emul/ibcs2/etc/passwd, and if that does not exist open the 'real' /etc/passwd file. It is recommended that you install iBCS2 packages that include configuration files, etc. under /emul/ibcs2, to avoid nam- ing conflicts with possible NetBSD counterparts. Shared libraries should also be installed in the shadow tree. Generally, you will need to look for the shared libraries that iBCS2 binaries depend on only the first few times that you install an iBCS2 program on your NetBSD system. After a while, you will have a sufficient set of iBCS2 shared libraries on your system to be able to run newly imported iBCS2 binaries without any extra work. Setting up shared libraries How to get to know which shared libraries iBCS2 binaries need, and where to get them? Depending on the file type of the executable, there are different possibilities (when following these instructions: you will need to be root on your NetBSD system to do the necessary installation steps). COFF binaries You can simply copy all of the available shared libraries since they are fairly small in size. The COFF shared libraries are typically found in /shlib and can be obtained from the following sources: SCO UNIX version 3.x (aka ODT) SCO UNIX version 5.x (aka OpenServer) SCO UnixWare Many versions of SVR4.2/x86 After copying the shared libraries, you should have at least the following files on your system: /emul/ibcs2/shlib/libc_s /emul/ibcs2/shlib/libnsl_s /emul/ibcs2/shlib/protlib_s ELF binaries You can simply copy all of the available shared libraries from the source system or distribution or use ldd(1) to determine the libraries required by a specific binary. After copying the shared libraries, you should have at least the following files on your system: /emul/ibcs2/usr/lib/libc.so.1 /emul/ibcs2/usr/lib/libcrypt.so /emul/ibcs2/usr/lib/libndbm.so /emul/ibcs2/usr/lib/libsocket.so.1 If you don't have access to a SCO system, you will need to get the extra files you need from a SCO distribution. As of January 1998, SCO sells a copy of SCO OpenServer (iBCS2) and/or SCO UnixWare (SVR4) for personal/non-commercial use for only the cost of shipping (about $20US). The distribution comes on an ISO9660-format CDROM which can be mounted and used to copy the necessary files. Run the following script to copy the basic set of files from a SCO distribution directory mounted somewhere locally: /usr/share/examples/emul/ibcs2/ibcs2-setup [directory] You should now be set up for SCO binaries which only need standard shared libs. BUGS
The information about SCO distributions may become outdated. Attempting to a use a nameserver on the local host does not currently work due to an absurd shortcut taken by the iBCS2 network code (remem- ber that there are no kernel sockets). 16/32/64 bit offsets may not be handled correctly in all cases. BSD
February 8, 1998 BSD
All times are GMT -4. The time now is 05:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy