-
The driver must conform to the
NWPA specification
rules. This implies that the driver filename must have the .HAM
or .CDM extension. This also implies the following for each
driver:
-
Uses a unique
Novell Assigned Module ID
-
Implements Scatter-Gather
-
Properly handles priority requests
-
Is accompanied by a functioning installation/message (
.DDI ) file
-
The installation/message file must conform to the
DDI (device driver information) file specification
rules. This implies that the filename of the installation/message file must
have the .DDI extension.
-
The driver must pass all appropriate tests in the
Storage Driver Certification Tests
under the applicable test suite. This also implies the following for each
driver:
-
Must not call the assembly
IN , OUT ,
CLI , or STI instructions
-
Able to reject unrecognized or invalid command line parameters without
adversely affecting server operation
-
Able to be unloaded during I/O execution without adversely affecting
server operation
-
Will not allow the loading of more instances than there are hardware
instances available
-
If a driver had been certified in the past, an updated driver by the same
name must be linked with a later date, and, greater major version, minor
version, or revision than that of its predecessor
-
The driver must not import any symbols (APIs) that are not described in the
NWPA specification
-
The driver must not export public symbols
-
The filename of the driver must be compliant to the ISO-9660 filename
format; that is, it must not contain hyphens, spaces, or extended ASCII
characters
-
The filename of the driver must not be offensive or problematic; if you have
questions regarding the appropriateness of your driver filename, don't
hesitate to
contact
us
-
The internal (link) date and external (DOS stamp) date of the driver must
match, and they must be a date that has already passed
-
Only drivers written by Novell are permitted to use the name "Novell" in the
text of their copyright strings
|