Re: X10 entertainment

[Jamie Bennett <jamie.bennett@xxxxxxxxx>]

On 11/12/05, Martin Howell <martin.howell@xxxxxxx> wrote:
>  Testing the interface on any port always produces a
>  comms failure message, so it can't see the interface.  Not only that,
>  the software now hogs the cpu to the extent that the machine is
unusable
>  - tried it on two different PCs, one with XP and one with 2003
Server,
>  same result.  The process that eats up the cpu is called
X10com32.exe.

I've just purchased the same item and had the exact same problems as
you. I found that the following proceedure worked for me.

1) Wipe any drivers off your system that you installed to do with the
CM12 (including the usb->serial driver).
2) Re-install them without plugging the unit in.
3) Reboot and plug the unit in when windows has finished booting.
4) Select the right comms port, for me it hogged the cpu when it was
on the wrong port. I think, from memory, mine was on comm 4.

As always YMMV. Worked for me though.

>  Martin

Jamie