A permission granted to a process to manipulate a specified object in a particular way by calling a system service. Different system object types support different access rights, which are stored in an object's access control list.
A set of template-based C++ classes that are often used to simplify the creation of COM objects.
In a USB interface, a collection of endpoints that describe a function for the device.
A macro that can be applied to source code to help PREfast analyze the code more effectively.
The context of the thread that happens to be running on a processor when the system borrows the thread to run a driver routine, such as an ISR. The driver routine can make no assumptions about the contents of the address space.
A model for I/O in which the operations carried out to satisfy I/O requests do not necessarily occur in sequence. The application that originally made the request can continue executing rather than waiting for its I/O to complete, the I/O manager or a higher-level driver can reorder I/O requests as they are received, and a lowest-level driver can start an I/O operation on a device before it has completed the preceding request, particularly in a multiprocessor machine.
Active Template Library
An operation that must run to completion without interruption.
A driver that is installed during the boot procedure and is required to start the system.
An error that is generated when core Windows data structures have been irretrievably corrupted, sometimes referred to as a system crash.
A driver that enumerates the devices that are attached to bus.
A "cabinet" of compressed installation files, with a file extension of .cab.
A driver-created object on which a UMDF driver implements the callback interfaces that are required to service events raised by one or more framework objects.
A build that has been compiled with debug symbols and built with special support for debugging. Checked builds are used only for testing and debugging.
A driver that typically provides hardware-independent support for a class of physical devices and is supplied by Microsoft.
A specialized COM object that clients use to create an instance of a particular COM object.
See setup class GUID.
A GUID that uniquely identifies a particular COM object. CLSIDs are required for COM objects that are created by a class factory, but are optional for objects that are created in other ways.
A DLL that augments the device installation operations performed by a class installer.
A KMDF object that maintains a linked list of other KMDF objects of any types.
Component Object Model, which is a platform-independent, distributed, object-oriented system for creating binary software components that can interact.
A process that uses COM objects.
A COM object that provides services to clients.
A DMA design in which the driver allocates a buffer in system memory that it shares with the DMA device. Sometimes referred to as "continuous DMA."
An annotation composed of two or more primitive annotations and other composite annotations.
The simultaneous execution of two code sequences.
A driver-defined area within a WDF object in which the driver stores information that is specific to that instance of the object.
(1) A device object that is not part of the Plug and Play device stack. (2) When capitalized, a device object that is the target for I/O requests between the reflector and the UMDF driver manager.
A locking mechanism that prevents the delivery of most asynchronous procedure calls. A thread running in a critical region is running at an intermediate IRQL level between PASSIVE_LEVEL and APC_LEVEL. Sometimes called a "critical section."
See critical region.
A thread's priority at any given time.