can't get widget to install
jifop
Registered User
Hi guys, i am using a samsung netbook and a 17" elo touchscreen running XP home for my HogPc setup but i can't get the widget to install, i have tried uninstalling and reinstalling hogpc including the older hog2pc release also many reboots but i still can't seem to get it to recognise the widget even if i point it to the windows/inf folder.
does anyone have any ideas?
does anyone have any ideas?
Comments
If it is a 64-bit OS you will not be able to install the widget drivers.
Hope this helps.
http://www.highend.com/support/downloads/dl/Uninstalling%20or%20Upgrading%20PreSP3.pdf
You can tell by looking for the silver oval around the DMX port....if it is blue it might not be upgraded.
The surest way to tell is to run the widget upgrader utility and see if it shows up Red....if so you need to buy an upgrade.
Are you logged on as "Administrator" to you computer?
The drivers should install, and you should see it show up under "Flying Pig Systems devices in the Windows Device Manager (Start: Run:type in "devmgmt.msc", press enter) even if it's not upgrade to support Hog3 mode. (The device will show up, it just won't let you use it under Hog III).
I've heard of a number of problems using Widgets with Netbooks. Netbooks tend to have very tight power budgets, and frequently can't supply the amount of power they're supposed to be able to supply to the USB ports. You might try a Powered USB hub and see if that helps.
1: Don't Search Windows Update
2: Install Driver Automatically.
It should then install and load the driver.
When you plug in the widget, and get the "Found New Hardware" wizard, you should select:
1: Don't Search Windows Update - Done
"this wizard helps you install software for:
USB Device"
2: Install Driver Automatically.
It then says "cannot install the hardware"
should i try a powered hub? or should i fresh instal xp sp2? the machine came with sp3 so a downgrade is imposible
by the way thanks for all your suggestions!
Try the powered hub.
Also, if you have both 2PC and 3PC on the system, make sure you install 3PC *after* you installed 2PC. Also, it's best to have all wings and widgets unplugged when you install the software, then reboot after the install before you try and connect any widgets.
Try a new USB cable as well to rule it out.
plus i can't afford a new one at the moment
Call support @ +1 (800) 890-8989
tried this, once installing automatically and the secondtime pointing machine at windows/inf and this is what it said:
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.
thanks a million