DriverEntry of Changer Miniclass Drivers routine
In Microsoft Windows 2000, changer miniclass drivers do not have a DriverEntry routine, but in Windows XP and later operating systems a miniclass driver must have a DriverEntry routine with the following characteristics.
Syntax
NTSTATUS DriverEntry(
_In_ PVOID Argument1,
_In_ PVOID Argument2
);
Parameters
Argument1 [in]
Pointer to operating system-specific information.
Argument2 [in]
Pointer to operating system-specific information.
Return value
The miniclass driver's DriverEntry routine must return the value returned by the ChangerClassInitialize routine.
Remarks
Parameters Argument1 and Argument2 point to operating system-specific information. A Miniclass driver should not attempt to interpret these parameters. Instead, it should pass these parameters to the ChangerClassInitialize routine.
ChangerClassInitialize performs most of the initialization required by the miniclass driver. The principal task of the minidriver in its DriverEntry routine is to load the entry points to its command processing routines into an MCD_INIT_DATA structure and pass the address of this structure to the ChangerClassInitialize routine.
Requirements
Target platform |
Desktop |
Header |
Mcd.h (include Mcd.h) |
Library |
NtosKrnl.lib |
DLL |
NtosKrnl.exe |
See also
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for