The paradigm for driver autoconfiguration and autodetection
in SVR5 follows the resource manager model established for
SCO SVR5 2.0 and is quite different from that used in SCO OpenServer 5.
for information about these facilities.
The resource manager presents
all parameters as strings.
Hardware configuration is implemented with
(Device Configuration Utility),
or a SCOAdmin manager,
depending on the type of device being configured.
``Resource manager database''
``Using configuration interfaces''.
Drivers can view configuration information
from the resource manager databsae with the
function and the parameters documented on the
Note that DDI 8 drivers must only call
from within a configuration manager transaction,
begun with a call to
and ended with a call to
View the sample drivers
to get an understanding of
how driver autoconfiguration works.
© 2005 The SCO Group, Inc. All rights reserved.
OpenServer 6 and UnixWare (SVR5) HDK - June 2005