As some of you might know, an .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.
New to this version of the driver (generated October 20, 2009) are several lines which reference a phone device.
%Zune.DeviceDesc% = ZuneMTPZUSB, USBMS_COMP_MTPZ
%Zune.DeviceDesc% = ZuneMTPZUSB, USBVID_045E&PID_0710
%Zune.DeviceDesc% = ZuneMTPZUSB, USBVID_045E&PID_063E
%Phone.DeviceDesc% = ZuneMTPZUSB, USBVID_045E&PID_0640
%Phone.DeviceDesc% = ZuneMTPZUSB, USBVID_045E&PID_0641
%Phone.DeviceDesc% = ZuneMTPZUSB, USBVID_045E&PID_0642
%ZuneIp.DeviceDesc% = ZuneMTPZIP, umburn:microsoft-com:device:mtpz:1
; Localizable strings
Msft = Microsoft
Zune.DeviceDesc = Zune
Phone.DeviceDesc = Phone
I Started Something believes that the three unique class IDs and specifically Product IDs (PID) identify three potential Zune Phone models not just capacity variants (since various Zune capacities are all grouped under the same PID).
Read More [via Engadget]