The Intel Camera issue is vexing. I found a solution to this problem that I found in the forums a while ago. I had it in a text file, so I do not remember who the poster was, but thanks to them...
"The root problem is that the device IDs for
the newer VA11A units are identical to the
built-in drivers for the Intel camera
(vend/prod 0x733/0x430) The ONLY way to
prevent this conflict is to disable the OEM
Intel camera drivers before connecting the
VA11A.
To disable the built-in drivers, execute
these commands in a command prompt:
ren %windir%\inf\icam4usb.??f *.*.old
ren %windir%\inf\oem48.??f *.*.old
After you run those two commands, install
your X10 drivers if you haven't already,
connect your VA11A, and XP will recognize
everything without a hassle.
Oh, don't worry. Your original Intel camera
drivers are still there. They're just
disabled. If you need them back, go into
your Windows INF directory, and look for
four files with ".old" at the end. take
the ".old" of the end and your Intel drivers
are back."
Also I felt like an idiot this evening. I had to replug in my USB things and as usual I got the uknown device message for the USB controller. I took the batteries out again and again only to realize after half an hour I had to UNPLUG it too!
Between the command prompt fix above and the disconnecting power fix for the box things have gone more smoothly with the frustrating X10 and XP war.