09-25-2002
CHECK OUT RTM's URL in PASHA's question for solve on this.
It ended up needing a boot driver to tell the comp that it was over 2gig. All installed now.......thx RTM.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have just been made responsible for setting up Apache on our office SCO
box. I have searched the internet, but
haven't found any details that I can make
sense of. I'm unfamiliar with Unix and would appreciate any help members of
the forum have to offer. (1 Reply)
Discussion started by: cstovall
1 Replies
2. 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
3. SCO
Hi everyone,
We r installing sco openserver 5.07 on dell poweredge 2800 but we are facing problem when installing SCSI-raid drivers. Dell provide Perc4 raid card and we dont found raid drivers for this specific raid card. So we r stuck up on primary stage and we also dont know the... (2 Replies)
Discussion started by: mineshkoli
2 Replies
4. 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
5. SCO
Even though IBM states that the x3500 server is Openserver 6.x compatible, it is still a bit of a trick to install SCO Openserver 6 to the machine because the standard method of installing the BTLD required to install the OS requires that the driver be written to a floppy which doesn't exist on... (3 Replies)
Discussion started by: qkrenge
3 Replies
6. 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
7. SCO
hi
Howto install SCO Openserver 5.0.7 as a trial or howto get a trial license number? (0 Replies)
Discussion started by: ccc
0 Replies
8. SCO
Hi
I am trying to install NIC FastNic 10/100 PCI Ethernet driver into PCI# 3 of the GA-SIML Rev 1.0 Motherboard on 1GB Hard-disk driveI have following the instruction on the CD-Disk and when I added NIC by netconfig and I do not know what is the following question:
PCI BUS#
DEVICE#... (3 Replies)
Discussion started by: TinhNhi
3 Replies
9. SCO
Hi,
Im installing sco openserver 5 (OpenServer-5.0.7Hw-10Jun05_1800.iso) on a vmware server 1.0.4.
Installation is ok but on when x server is loading i just can login, mouse does not move and most of keyboard cases do not respond.
I choose usb mouse + french keyboard while installating, should i... (1 Reply)
Discussion started by: sup69
1 Replies
10. SCO
hi
Howto install iperf on SCO OpenServer 5.0.7? (0 Replies)
Discussion started by: ccc
0 Replies
LEARN ABOUT SUNOS
wsreg_get_required_components
wsreg_add_required_component(3WSREG) Product Install Registry Library Functions wsreg_add_required_component(3WSREG)
NAME
wsreg_add_required_component, wsreg_remove_required_component, wsreg_get_required_components - add or remove a required component
SYNOPSIS
cc [flag ...] file ...-lwsreg [library ...]
#include <wsreg.h>
int wsreg_add_required_component(Wsreg_component *comp, const Wsreg_component *requiredComp);
int wsreg_remove_required_component(Wsreg_component *comp, const Wsreg_component *requiredComp);
Wsreg_component **wsreg_get_required_components(const Wsreg_component *comp);
DESCRIPTION
The wsreg_add_required_component() function adds the component specified by requiredComp to the list of required components contained in
the component specified by comp.
The wsreg_remove_required_component() function removes the component specified by requiredComp from the list of required components con-
tained in the component specified by comp.
The wsreg_get_required_components() function returns the list of required components contained in the component specified by comp.
RETURN VALUES
The wsreg_add_required_component() function returns a non-zero value if the specified required component was successfully added. Otherwise,
0 is returned.
The wsreg_remove_required_component() function returns a non-zero value if the specified required component was successfully removed. Oth-
erwise, 0 is returned.
The wsreg_get_required_components() function returns a null-terminated array of Wsreg_component pointers that represents the specified com-
ponent's list of required components. If the specified component has no required components, NULL is returned. The resulting array must
be released by the caller through a call to wsreg_free_component_array(). See wsreg_create_component(3WSREG).
USAGE
The relationship between two components in which one must be installed for the other to be complete is a dependent/required relationship.
The component that is required by the other component is the required component. The component that requires the other is the dependent
component.
The required component must be installed and registered before the dependent component can be. Uninstaller applications should check the
registry before uninstalling and unregistering components so a successful uninstallation of one product will not result in another product
being compromised.
Read access to the product install registry is required in order to use these functions because these relationships are held with light-
weight component references that can only be fully resolved using the registry contents.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|MT-Level |Unsafe |
+-----------------------------+-----------------------------+
SEE ALSO
wsreg_add_dependent_component(3WSREG), wsreg_can_access_registry(3WSREG), wsreg_create_component(3WSREG), wsreg_initialize(3WSREG),
wsreg_register(3WSREG), attributes(5)
SunOS 5.10 22 Sep 2000 wsreg_add_required_component(3WSREG)