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
uname(1)							   User Commands							  uname(1)

NAME
uname - print name of current system SYNOPSIS
uname [-aimnprsvX] uname [-S system_name] DESCRIPTION
The uname utility prints information about the current system on the standard output. When options are specified, symbols representing one or more system characteristics will be written to the standard output. If no options are specified, uname prints the current operating sys- tem's name. The options print selected information returned by uname(2), sysinfo(2), or both. OPTIONS
The following options are supported: -a Prints basic information currently available from the system. -i Prints the name of the platform. -m Prints the machine hardware name (class). Use of this option is discouraged. Use uname -p instead. See NOTES section below. -n Prints the nodename (the nodename is the name by which the system is known to a communications network). -p Prints the current host's ISA or processor type. -r Prints the operating system release level. -s Prints the name of the operating system. This is the default. -S system_name The nodename may be changed by specifying a system name argument. The system name argument is restricted to SYS_NMLN char- acters. SYS_NMLN is an implementation specific value defined in <sys/utsname.h>. Only the super-user is allowed this capa- bility. This change does not persist across reboots of the system. Use sys-unconfig(1M) to change a host's name perma- nently. -v Prints the operating system version. -X Prints expanded system information, one information element per line, as expected by SCO UNIX. The displayed information includes: o system name, node, release, version, machine, and number of CPUs. o BusType, Serial, and Users (set to "unknown" in Solaris) o OEM# and Origin# (set to 0 and 1, respectively) EXAMPLES
Example 1: Printing the OS name and release level The following command: example% uname -sr prints the operating system name and release level, separated by one <SPACE> character. ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of uname: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. SYSV3 This variable is used to override the default behavior of uname. This is necessary to make it possible for some INTERACTIVE UNIX Systems and SCO UNIX programs and scripts to work properly. Many scripts use uname to determine the SYSV3 type or the version of the OS to ensure software is compatible with that OS. Setting SYSV3 to an empty string will make uname print the following default values: nodename nodename 3.2 2 i386 The individual elements that uname displays can also be modified by setting SYSV3 in the following format: os,sysname,node,rel,ver,mach os Operating system (IUS or SCO). sysname System name. node Nodename as displayed by the -n option. rel Release level as displayed by the -r option. ver Version number as displayed by the -v option. mach Machine name as displayed by -m option. Do not put spaces between the elements. If an element is omitted, the current system value will be used. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ SEE ALSO
arch(1), isalist(1), sys-unconfig(1M), sysinfo(2), uname(2), nodename(4), attributes(5), environ(5), standards(5) NOTES
Independent software vendors (ISVs) and others who need to determine detailed characteristics of the platform on which their software is either being installed or executed should use the uname command. To determine the operating system name and release level, use uname -sr. To determine only the operating system release level, use uname -r. Notice that operating system release levels are not guaranteed to be in x.y format (such as 5.3, 5.4, 5.5, and so forth); future releases could be in the x.y.z format (such as 5.3.1, 5.3.2, 5.4.1, and so forth). In SunOS 4.x releases, the arch(1) command was often used to obtain information similar to that obtained by using the uname command. The arch(1) command output "sun4" was often incorrectly interpreted to signify a SunOS SPARC system. If hardware platform information is desired, use uname -sp. The arch -k and uname -m commands return equivalent values; however, the use of either of these commands by third party programs is dis- couraged, as is the use of the arch command in general. To determine the machine's Instruction Set Architecture (ISA or processor type), use uname with the -p option. SunOS 5.10 17 Sep 2003 uname(1)
All times are GMT -4. The time now is 11:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy