MZ@ !L!This program cannot be run in DOS mode. $Rؕ3}3}3}H̴3}H̱3}Rich3}PEL!  B`Mm@X@.rsrcPB@@( @Xp   :dLMUI3h:`x^ϥsqGe@7V MUI en-US''xt'u'~''NN114400PPDPPtpp p!p%p%pt)p)p0p0p@@p@pPpPpepep|ppzp$ $46%9:'T U )  8*  +  ,>N>N,0uEu0-d:A driver package which uses user-mode driver framework version %2 is being installed on device %1. The UMDF service %1 (CLSID %2) was installed. It requires framework version %3 or higher. The UMDF service %1 (CLSID %2) was upgraded. It requires framework version %3 or higher. hThe driver package installation has succeeded. The driver package installation has failed. The final status was %1. `A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. The device %2 (location %3) is offline due to a user-mode driver crash. Windows will attempt to restart the device %5 more times. Please contact the device manufacturer for more information about this problem. hThe device %2 (location %3) is offline due to a user-mode device crash. Windows will no longer attempt to restart this device because the maximum restart limit has been reached. Disconnecting the device and reconnecting it, or disabling it and re-enabling it from the device manager, will reset this limit and allow the device to be accessed again. Please contact the device manufacturer for more information about this problem. The device %2 was unable to start due to conflict between the settings for driver %5 (%3 - %4) and the other drivers. Windows will not be able to start this device. Please contact the device manufacturer for assistance. The UMDF reflector was unable to complete startup because the %2 service was not found. This service may be started later during boot, at which point Windows will attempt to start the device again. The device %2 (location %3) is offline due to a user-mode driver crash. Windows will attempt to restart the device %5 more times in its own process. Please contact the device manufacturer for more information about this problem. 4The device %2 (location %3) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process %5 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. 4UMDF Test Event (%1) $Response Time SQM Info Start Stop Critical Error Information Verbose XStartup of the driver manager service. XCreation of a new driver host process. PShutdown of a driver host process. TStartup of a new driver host process. tLoading drivers to control a newly discovered device. |Pnp or Power Management operation to a particular device. PShutdown of a driver host process. \Installation or update of device drivers. @User-mode Driver problems. Pnp or Power Management operation to a particular driver in a device stack. DStartup of the UMDF reflector Performance measurement for installation or update of device drivers. tPerformance measurement for predevice install phase. tPerformance measurement for postdevice install phase. dPerformance measurement for framework update. $Testing UMDF HDDI call to read from Hardware. 0Read from Hardware. HDDI call to Write to hardware. 0Write to hardware. TUMDF hardware interrupt notification. Sqm Task. `Microsoft-Windows-DriverFrameworks-UserMode Operational System hThe Driver Manager service started successfully The Driver Manager service failed to start. The error reported was %2. XThe Driver Manager service was stopped The Driver Manager service is starting a host process for device %3. `The host process (%1) started successfully. The host process (%1) failed to start successfully. The error reported was %2. lThe host process (%1) is being asked to shutdown. The host process (%1) has a problem (%2) and is being terminated. \The host process (%1) has been shutdown. `The UMDF Host Process (%1) is starting up. lThe UMDF Host Process (%1) started successfully. The UMDF Host Process (%1) failed to start successfully. The error reported was %2. The UMDF Host Process (%1) has been asked to load drivers for device %2. The UMDF Host is loading driver %4 at level %3 for device %2. The UMDF Host Process (%1) has loaded module %3 while loading drivers for device %2. |The UMDF Host successfully loaded the driver at level %3. The UMDF Host failed to load the driver at level %3. The error reported was %4. The UMDF Host Process (%1) has successfully loaded drivers for device %2. The UMDF Host Process (%1) has failed to load drivers for device %2. The error reported was %3 |Received a Pnp or Power operation (%3, %4) for device %2. Completed a Pnp or Power operation (%3, %4) for device %2 with status %9. Forwarded a finished Pnp or Power operation (%3, %4) to the lower driver for device %2 with status %9. Forwarded a Pnp or Power operation (%3, %4) for device %2 to the lower driver with status %9 Received a Pnp or Power operation (%3, %4) for device %2 which was completed by the lower drivers with status %9 hThe UMDF Host (%1) has been asked to shutdown. LThe UMDF Host (%1) has shutdown. UMDF State Machine %4 start processing event %5 (Queueing %6) XUMDF State Machine %4 dropped event %5 UMDF State Machine %4 state change from %5 to %7 on event %6 UMDF State Machine %4 event processing finished in state %5 UMDF State Machine %4 event processing stopped in state %5 Power IRP related event in the User-mode Driver Frameworks Host Process A driver package which uses user-mode driver framework version %2 is being installed on device %1. The driver package installation has finished. The final status was %1. PreDevice installation (UMDF version %2) is starting for device %1. PreDevice installation has finished. The final status was %1. PostDevice installation (UMDF version %2) is starting for device %1. PostDevice installation has finished. The final status was %1. <UMDF update has started. hUMDF has been updated. The final status was %1. DDI to read from hardware begins (TargetType: %1, TargetSize: %2, BufferCount: %3). DDI to read from hardware ends (TargetType: %1, TargetSize: %2, BufferCount: %3). Read from hardware begins (TargetType: %1, TargetSize: %2, BufferCount: %3). Read from hardware ends (TargetType: %1, TargetSize: %2, BufferCount: %3). DDI to write to hardware begins (TargetType: %1, TargetSize: %2, BufferCount: %3). DDI to write to hardware ends (TargetType: %1, TargetSize: %2, BufferCount: %3). Write to hardware begins (TargetType: %1, TargetSize: %2, BufferCount: %3). Write to hardware ends (TargetType: %1, TargetSize: %2, BufferCount: %3). Read from hardware begins (TargetType: %1, TargetSize: %2, BufferCount: %3). Read from hardware ends (TargetType: %1, TargetSize: %2, BufferCount: %3). Write to hardware begins (TargetType: %1, TargetSize: %2, BufferCount: %3). Write to hardware ends (TargetType: %1, TargetSize: %2, BufferCount: %3). UMDF Reflector sent notification for hardware interrupt (Message ID %1). UMDF framework received notification for hardware interrupt (Message ID %1). QueueToTail $QueueToFront QueueFull 4VS_VERSION_INFO@%@%?RStringFileInfo.040904B0LCompanyNameMicrosoft Corporation7FileDescriptionWindows Driver Foundation - User-mode Platform Libraryr)FileVersion6.3.9600.16384 (winblue_rtm.130821-1623): InternalNameWUDFPlatform.LegalCopyright Microsoft Corporation. All rights reserved.ROriginalFilenameWUDFPlatform.dll.muij%ProductNameMicrosoft Windows Operating SystemBProductVersion6.3.9600.16384DVarFileInfo$Translation PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGX