06-09-2006
SCO Openserver Installation problem
we have to facing problem on IBM x226 server to installation of SCO
Openserver 5.0.7 (UNIX). when we succesfuly load to
adaptec controlar driver ad320 BTLD , The system gives the Error message
WARNING : Cannot Connect to APM, Error 0x0008
System Loaded Press <Return> to Start
then we have continue installation of SCO UNIX but after completion
of unix it could not be boot and again mesage apairs
WARNING : Cannot Connect to APM, Error 0x0008
System Loaded Press <Return> to Start
IBM SERVER X226
M/T 8648ECY
BIOS_Ver. __ 1.62C UPDATED
HOT SWAP HDD 73 GB CHECKED ON BOTH CH
can any one help
10 More Discussions You Might Find Interesting
1. IP Networking
I have certain problems while Installing UNIX OPENSERVER.Could anyone solve that if I provide that problem. (3 Replies)
Discussion started by: Rajraius
3 Replies
2. Filesystems, Disks and Memory
Hello all,
I'm trying to install SCO openserver 5 on a 2.5 Gig hard drive, and I tried fdisk and a low-level format of the drive. When I insert the boot diskette all seems fine, and it asks me to set the cd-rom and it sees it and reads from it. Well, I'm thinking all is well until right after I... (1 Reply)
Discussion started by: immulett
1 Replies
3. UNIX for Dummies Questions & Answers
My company has a Compaq NeoServer running SCO OpenServer Release 5 (vintage late 1998) that we inherited from another small company. This has been a very reliable file server for our small company. We recently installed a new Linux server and would like to convert the NeoServer to other functions... (1 Reply)
Discussion started by: Jeff Boyce
1 Replies
4. UNIX for Dummies Questions & Answers
I am running the beta version of Openserver by SCO and the
Graphical login only gives me the option of logging into the
system v xwindows and I know that this build included KDE 3.3
I have tried the kde kdm command at shell prompt: command not
found. Any ideas anyone? (0 Replies)
Discussion started by: coreykirk
0 Replies
5. SCO
we are installing Openserver 5.0.7, system have SAS controller (Hard Disk Attached) as well as Adaptec ultra 320 controller (Tape Drive Attached).
At the time of installation we link both driver BTLD
Boot: Defbootstr link=accraid ad320
Aftes succesfully installation of accraid btld... (6 Replies)
Discussion started by: hafizurr
6 Replies
6. SCO
can not for the life of me workout which BTLD to load allways shows no HDD available can any one give me a clue
tried
hpsas
aacraid
lsil
a160
a320
server is a ML310 G4 ?????:confused::confused: (7 Replies)
Discussion started by: wildginger
7 Replies
7. SCO
hello, i want to install release 5.0.5 on my notebook but the system hangs when extracing files from source media in fact after configuration all of setting please help me:confused: (1 Reply)
Discussion started by: hossein
1 Replies
8. SCO
I am currently having a problem with my SCO OpenServer 5.0.5 / 3.2v5.0.5 system.
Running smoothly for the past 3 years, at random on March 16, 2010 the system crashes. I reboot it. Everything is normal again. 9 hours later it crashes again. This cycle has repeated itself ever since then. System... (2 Replies)
Discussion started by: jesmith
2 Replies
9. UNIX for Advanced & Expert Users
Hi All ,
I wanted to install SCO Open server 5.0.7 on HP DC7600 Desktop Machine, is there any bootloader and which site i can find it to enable me install it because the system is not recognizing the Hard disk just like the ML G Series machine installations.
Please help if you have done this... (4 Replies)
Discussion started by: davosky
4 Replies
10. SCO
Hello all,
First off- great forum! I have learned a lot just by reading some of the questions and answers. Good to see there are good people out there still willing to help!
Here is my dilemma- I have a fairly new server running an Activant product on it, which runs SCO openserver 5.0.5... (9 Replies)
Discussion started by: crt001
9 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)