Sponsored Content
Operating Systems SCO SCO unix binary compatibility problem Post 302371323 by jgt on Saturday 14th of November 2009 07:49:38 AM
Old 11-14-2009
I found this, http://www.vtsoft.com/vcssupport/vv/...s/VV-00099.txt as an explanation. Do you know if 'cvtomf' is part of the OS or the Development System?
Never mind.

Here: ftp://ftp.sco.com/pub/SLS/
There appears to be a revised version in lng353a
 

10 More Discussions You Might Find Interesting

1. SCO

inetd problem in Unix Sco

Hi, I cannot remote login into my unix sco server, only at the box itself, when I write root to login then enter, it immediately logs in without asking me the password :confused: , at the prompt it gives me this error : inetd:system defaults databse couldn't be allocated due to : cannot... (6 Replies)
Discussion started by: BAM
6 Replies

2. Filesystems, Disks and Memory

UNIX problem concerning Microsoft Office Binary

I just started using Terminal on my Mac this summer, and right now I am having problems making a shell script. This shell should run the "Microsoft Setup Assistant" once I run the Automator Script. Alas, I still have problems. Here is the offending scriptlet: Sudo Tcsh root# cd... (2 Replies)
Discussion started by: chrisfrap
2 Replies

3. Filesystems, Disks and Memory

Unix Sco Open Server, Windows Computers Problem Access Unix Shared Files Help!!!!!

Hello Moto I hope someone can help We's here at work, have a unix box with sco openserver 5 on it, so it has a nice gui interface.. and also a fair few windows computers.. a system admin guy b4 me, has set up a user called neil, which can, when u try to access the unix box using windows... (2 Replies)
Discussion started by: haggo
2 Replies

4. UNIX for Dummies Questions & Answers

Problem with FTP o n Unix SCO

my problem is like this while ftping locally it works, but when users from WAN try the ftp services it doesnt comes the message it displays is as follows "connection closed by remote host " please help Thanks (5 Replies)
Discussion started by: Athos19
5 Replies

5. SCO

SCO 5.0.6 application compatibility w/ Linux?

Hello Valued Members, I was wondering if there are any Linux, BSD, versions that can run SCO 5.0.6 applications without much modification? I was looking into purchasing a copy of Caldera Openlinux, the last version, but wanted to ask if there are any other options of a newer variant. I am also... (8 Replies)
Discussion started by: stay0ut
8 Replies

6. UNIX for Dummies Questions & Answers

Problem installing SCO UNIX 6.0

Hi all, This is the first time I have attempted to install SCO UNIX. I have a customer that has requested we install it on a desktop sized machine and they have supplied me with their install CD - "SCO UNIX Release 6.0.0 Base Operating System Install disk CD 1" I am attempting to install it... (0 Replies)
Discussion started by: Becks
0 Replies

7. SCO

load sco xenix and sco unix binary ?

Hi I have some sco xenix object, bin and archive files that operate in sco unix 5.0.7. I know that sco unix kernel can support sco xenix binary. I want to know how can I link xenix and unix archives together? (0 Replies)
Discussion started by: javad1_maroofi
0 Replies

8. SCO

Binary compatibility

Hi I'm going to buy C-ISAM 7.25 under sco unixware 7 to install in sco openserver 5.0.7. I'm wondering sco unixware 7 and sco openserver 5.0.6 are binary compatibles ? tnx (1 Reply)
Discussion started by: javad1_maroofi
1 Replies

9. SCO

sco unix backward compatibility on "max open file per process"

Hi How to increase maximum number of open file in "sco xenix binary" running in "sco unix openserver 5.0.7" ? I have changed "NOFILES" kernel parameter to 512, but xenix binray can't open more than 60. tnx (4 Replies)
Discussion started by: javad1_maroofi
4 Replies

10. SCO

SCO Unix 5.0.6 SATA in compatibility mode

I am very new to SCO Unix so I apologize if this is a easy or dumb question. I have a 160GB SATA hard drive and SATA CD-ROM drive connected to one of my systems. I have both the drives running in compatibility mode. I also have the hard drive set as a primary master and the CD-ROM drive set as... (10 Replies)
Discussion started by: NPIGuy
10 Replies
CS(1)							  The Canonical Csound Reference						     CS(1)

NAME
cs - Starts Csound with a set of options that can be controlled by environment variables, and input and output files determined by the specified filename stem. . DESCRIPTION
Starts Csound with a set of options that can be controlled by environment variables, and input and output files determined by the specified filename stem. SYNTAX
cs [-OPTIONS] <name> [CSOUND OPTIONS ... ] INITIALIZATION
Flags: o - OPTIONS = OPTIONS is a sequence of alphabetic characters that can be used for selecting the Csound executable to be run, as well as the command line flags (see below). There is a default for the option 'r' (selects real-time output), but it can be overridden. o <name> = this is the filename stem for selecting input files; it may contain a path. Files that have .csd, .orc, or .sco extension are searched, and either a CSD or an orc/sco pair that matches <name> the best are selected. MIDI files with a .mid extension are also searched, and if one that matches <name> at least as close as the CSD or orc/sco pair, it is used with the -F flag. NOTE The MIDI file is not used if any -M or -F flag is specified by the user - new in version 4.24.0) Unless there is any option (-n or -o) related to audio output, an output file name with the appropriate extension is automatically generated (based on the name of selected input files and format options). The output file is always written to the current directory. NOTE file name extensions are not case sensitive. o [CSOUND OPTIONS ... ] = any number of additional options for Csound that are simply copied to the final command line to be executed. The command line that is executed is generated from four parts: 1. Csound executable (possibly with options). This is exactly one of the following (the last one has the highest precedence): o a built-in default o the value of the CSOUND environment variable o environment variables with a name in the format of CSOUND_x where x is an uppercase letter selected by characters of the -OPTIONS string. Thus, if the -dcba option is used, and the environment variables CSOUND_B and CSOUND_C are defined, the value of CSOUND_B will take effect. 2. Any number of option lists, added in the following order: o either some built-in defaults, or the value of the CSFLAGS environment variable if it is defined. o environment variables with a name in the format of CSFLAGS_x where x is an uppercase letter selected by characters of the -OPTIONS string. Thus, if the -dcba option is used, and the environment variables CSFLAGS_A and CSFLAGS_C are defined as '-M 1 -o dac' and '-m231 -H0', respectively, the string '-m231 -H0 -M 1 -o dac' will be added. 3. The explicit options of [CSOUND OPTIONS ... ]. 4. Any options and file names generated from <name>. NOTE Quoted options that contain spaces are allowed. EXAMPLES
Assuming the following environment variables: CSOUND = csoundfltk.exe -W CSOUND_D = csound64.exe -J CSOUND_R = csoundfltk.exe -h CSFLAGS = -d -m135 -H1 -s CSFLAGS_D = -f CSFLAGS_R = -m0 -H0 -o dac1 -M "MIDI Yoke NT: 1" -b 200 -B 6000 And a directory that contains: foo.orc piano.csd foo.sco piano.mid im.csd piano2.mid ImproSculpt2_share.csd foobar.csd The following commands will execute as shown: cs foo => csoundfltk.exe -W -d -m135 -H1 -s -o foo.wav foo.orc foo.sco cs foob => csoundfltk.exe -W -d -m135 -H1 -s -o foobar.wav foobar.csd cs -r imp -i adc => csoundfltk.exe -h -d -m135 -H1 -s -m0 -H0 -o dac1 -M "MIDI Yoke NT: 1" -b 200 -B 6000 -i adc ImproSculpt2_share.csd cs -d im => csound64.exe -J -d -m135 -H1 -s -f -o im.sf im.csd cs piano => csoundfltk.exe -W -d -m135 -H1 -s -F piano.mid -o piano.wav piano.csd cs piano2 => csoundfltk.exe -W -d -m135 -H1 -s -F piano2.mid -o piano2.wav piano.csd CREDITS
Author: Istvan Varga Jan 2003 AUTHORS
Barry Vercoe MIT Media Lab Author. Dan Ellis MIT Media Lab, Cambridge Massachussetts Author. COPYRIGHT
5.10 08/01/2011 CS(1)
All times are GMT -4. The time now is 02:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy