I am an advanced program patcher. I have ran every trick I know on the VA11a that usually recognizes itself as VA12A on XP with USB 2.0 port's. I have read all the treads and I can see there is the same problem occuring over and over on many systems.
Here is the only repeatable Easy Fix for now.
0) Regardless of what the software tells you, Do not have any of the X10 usb devices plugged into your computer when you download your software.
1) After you download the software from x10 and are back on the desktop, then run the software setup file. It will Automatically go back on line and finish it's updates.
2) Then Plug the Firecracker- it will auto install ok on XP
3) Then plug in the VA11A it will auto install ok-usually on most systems
4) restart the computer-NOW>>>>>>>>
5) if when you restart the VA11A has an yellow Exclamation point, then unplug the VA11a- and restart
6) DO NOT TURN ON THE COMPUTER with the VA11a or (VA12a) plugged in to any usb.
7) after it is restarted and Running Xp Desktop then Plug the Va11a back in-wait about 15 seconds and it should be working.
THE WHOLE PROBLEM IS THE SOFTWARE DRIVER conflicts out over PRIORITY issues. It must have been rushed out, and not tested. It is as bad as Manually setting IRQ's and DMA address in DOS. Maybe even as bad as SCSI conflict's
Fact is: this should have been resolved before the software was released.
Good Luck with any type of X10 secuirty monitoring device after a powerfailure, if your have a Remote Summer house and loose power there your never going to see anything broadcasted from x10 software. The Vanguard really is bad though- it is just to Prioitized to ONLY look for the VA11a or va12a input card. I have used a lot of other MORE STABLE Viedo input cards that would have made this a good package.
I keep more hacked drivers for the x10 that may work better at:
WWW.rod45103.com