Moreover, just as how the current three generation Zunes are represented by three different IDs, there are three unique class IDs and specifically Product IDs (PID) that identify three potential “Zune Phone” models (not storage capacities) off the bat. %ZuneIp.DeviceDesc% = ZuneMTPZIP, umb\urn:microsoft-com:device:mtpz:1 %Phone.DeviceDesc% = ZuneMTPZUSB, USB\VID_045E&PID_0642 %Phone.DeviceDesc% = ZuneMTPZUSB, USB\VID_045E&PID_0641 %Phone.DeviceDesc% = ZuneMTPZUSB, USB\VID_045E&PID_0640 %Zune.DeviceDesc% = ZuneMTPZUSB, USB\VID_045E&PID_063E %Zune.DeviceDesc% = ZuneMTPZUSB, USB\VID_045E&PID_0710 %Zune.DeviceDesc% = ZuneMTPZUSB, USB\MS_COMP_MTPZ
#ZUNE SOFTWARE DOWNLOAD FAILED DRIVER#
New to this version of the driver which was actually generated on Octoare several lines which pretty much speak for themselves.
INF file is essential component of a driver package responsible for identifying the driver and associating it with compatible USB hardware IDs, and in this case, the Zune.inf file is responsible for associating devices with the Zune driver. The elusive “Zune Phone” is pretty much confirmed.Īs some of you might know, an.
#ZUNE SOFTWARE DOWNLOAD FAILED UPDATE#
What might appear as just a regular software update is actually hiding a very big secret. Coinciding with the scheduled maintenance today, a new Zune software update was also released (version 4.2.202.0 for those playing along at home).
0 kommentar(er)
