can't get widget to install

[quote=jifop;41284]#-019 Searching for hardware ID(s): usb\vid_04b0&pid_0001

the correct descriptor for a dmx widget is VID_0CB0&PID_0001; yours being different points to EEPROM corruption.

fortunately, dmx widgets don't store much in their cypress boot EEPROM's: a (corrupted) usb descriptor, a serial number, the 3PC "proof-of-purchase", etcetera, so the damage may be minimal, and it might be worked around.

all the code for dmx slot generation, blinking the LED's and such is not stored in EEPROM, but downloaded to RAM; installing this code to your widget is the sole purpose of the first (loading) driver.

to get the first driver to deposit this code onto your widget, you'll need to edit fps_dmx.inf: replace all occurrences of VID_0CB0&PID_0001 with VID_04B0&PID_0001 (this is roughly equivalent to changing a _lib manufacturer = line)

leave all VID_0CB0&PID_0002's as they are; once your VID_04b0&PID_001 usb controller gets its code, it will correctly ReNumerate as a VID_0CB0&PID_0002 dmx widget and the second (friendly) driver will be matched to fps_dmx.inf based on this descriptor, which is hard-coded in the payload transferred by the (loader) driver.



no promises, but if it works, remember to make the same change on your other machine, and back-up the .inf which will be overwritten with every 2PC or 3PC install.

[quote=jifop;41284]#-019 Searching for hardware ID(s): usb\vid_04b0&pid_0001

the correct descriptor for a dmx widget is VID_0CB0&PID_0001; yours being different points to EEPROM corruption.

fortunately, dmx widgets don't store much in their cypress boot EEPROM's: a (corrupted) usb descriptor, a serial number, the 3PC "proof-of-purchase", etcetera, so the damage may be minimal, and it might be worked around.

all the code for dmx slot generation, blinking the LED's and such is not stored in EEPROM, but downloaded to RAM; installing this code to your widget is the sole purpose of the first (loading) driver.

to get the first driver to deposit this code onto your widget, you'll need to edit fps_dmx.inf: replace all occurrences of VID_0CB0&PID_0001 with VID_04B0&PID_0001 (this is roughly equivalent to changing a _lib manufacturer = line)

leave all VID_0CB0&PID_0002's as they are; once your VID_04b0&PID_001 usb controller gets its code, it will correctly ReNumerate as a VID_0CB0&PID_0002 dmx widget and the second (friendly) driver will be matched to fps_dmx.inf based on this descriptor, which is hard-coded in the payload transferred by the (loader) driver.



no promises, but if it works, remember to make the same change on your other machine, and back-up the .inf which will be overwritten with every 2PC or 3PC install.