Enumerating Pre-install Packages
Some days ago I bought an MSP-FET, a debugger for MSP430 microcontrollers from TI. My system, with Windows 7 x64, is unable to install the correct drivers. My notebook, with Windows XP does without any problem. The device is described in the in file as:%DESCRIPTION_DBG%=TIUSB, USB Vid_2047&Pid_0014&MI_00%DESCRIPTION1%=TIUSB, USB Vid_2047&Pid_0014&MI_02 It installs two devices.
Enumerating Pre-install Packages
Windows XP shows the correct VID/PID pairs and installs both devices correctly. But my system with Win7 shows the MSP-FET as: USB VID_2047&PID_0014&REV_0200 USB VID_2047&PID_0014 Complains about missing drivers and hardware don't work.
What is working bad in my Windows 7 x64 installation? Both operating systems appear to detect the same VID/PID combination (2047/0014). The difference between the two strings reported by the device manager is due to implementation differences between the two OSs.
Bootcamp Enumerating Pre-install Packages
I have also tried to mount the wim using dism command, its works, but the Pre-install registry Tweak Tool doesn't work on a dism-mounted wim, only on an old imagex-mounted wim. Like i said, it works 100% properly on Vista, so why on Windows 7 my dism get corrupt? Anyone have this problem? Here is the dism.log report. If you’re adhering to semantic versioning and introduce any breaking changes in a major release, a post-install message is a great way to warn users about the changes. However, one thing you want to avoid is enumerating your gem’s full changelog in the message.