for the device. If no DeviceHandlers entry is found under the device instance, AutoPlay checks for the existence of a DeviceGroup entry, again under the device instance. This allows a whole set of devices to share device parameters. HKLM\...\Enum\USB\Vid_059b&Pid_0031\059B003112010E93\Device Parameters DeviceGroup "ZipDrive100" The parameters for this device group are stored in: So for the ZipDrive100 group example: HKLM\...\AutoPlayHandlers\DeviceGroups\ZipDrive100 Icons "%SystemRoot%\system32\shell32.dll,-230\0\0" Label "Zip Drive 100" DeviceHandlers "ZipDeviceHandler" Lastly, AutoPlay searches the relevant Device Interface Class GUIDs. The parameters for device classes are stored in: Here is the entry that the Microsoft application Movie Maker registers for any and all Video Camera devices: HKLM\...\AutoPlayHandlers\DeviceClasses\{CC7BFB41-F175-11D1-A392-00E0291F3959} DeviceHandlers "VideoCameraDeviceHandler" Label "@C:\Program Files\Movie Maker\wmm2res.dll,-63094" Icons "C:\WINDOWS\system32\shell32.dll,-317\0\0" See also AutoRun Software providing similar functionality in other environments gnome-volume-manager in GNOME Thunar (using the thunar-volman plugin) in Xfce References External links AutoPlay in Windows XP, MSDN Magazine, November 2001 Implement an Autoplay Handler, CodeProject Windows components