Autoconfiguration Flow for GPD in Windows Vista
Autoconfiguration follows the following sequence:
Port Monitor sends to the spooler a notification that contains any values that formerly were not in the cache or that changed.
The spooler responds to the notification from the port monitor by calling DrvPrinterEvent.
Printer_Event_Configuration is passed to the driver that contains any and all new values. The driver is notified that the value of an attribute has changed, and the registry is also updated.
If the notification is too big, Reduced Schema Event is called.
The PPD file is parsed, including all GDL file extensions and GDL content within the PPD. All GDL content in either GDL file extensions or throughout the PPD file must be surrounded with *Ifdef: GDL_Enabled and *Endif: GDL_Enabled.
Your plug-in will retrieve the value for *MSBidiValue, which will be based on the current string value for *QueryString. For example, a *QueryString value of "\Printer.Configuration.DuplexUnit:Installed" will represent a *BidiValue value of BOOL(TRUE).
Your plug-in will update the driver UI according to the latest configuration.