CM11a Controller w/Addressing Issues

[AutoMan]

The Stats:
CM11a controller
New house professionally wired approx. 10 yrs ago (pretty new)
About 2 dozen X10 devices in use
2 noise suppressors in use on TV system and desktop computer area
Phase coupler in system
Programmed from desktop w/Windows XP Pro

Problem:
Controller had been working flawless for years (previously programmed with earlier version of Windows) Now programmed w/XP PRO.
The problem that has cropped up is that 3 outlets addressed with O1, O2 & O3 respectively now respond to their address AND address O5, O6 & O7 respectively. And the units programmed w/O5, O6 & O7 do not respond.

Has anyone expierienced this or anything simular? Any ideas on a fix other than changing addresses? Sounds like a possible O/S issue doesn't it?
Thanks in advance for any help.

[Dan Lawrence]

Some people have experienced problems connecting to the CM11A in WindowsXP due to motherboard problems with the COM ports, others have had no problems.  In your case I suspect your .X10 file(s) have somehow become corrupt.  I would try creating a new .x10 file (using the same modules and addresses) and uploading it to the CM11A. If the issues described continue, it may be time to upgrade to Active Home Pro and the CM15A usb interface.

[AutoMan]

Yeah,
From some of the posts i've read on here it looks like older controllers and newer O/S's don't play too well together sometimes.

[Dan Lawrence]

I ran into that when I updated by old P-III system to Windows XP Home.  Its motherboard played the "vanishing/reappearing" act and AH could loose and find the CM11A on an irregular schedule, so I updated to AHP and the CM15A.

[Charles Sullivan]

Problems with the old ActiveHome 1.42 on newer versions of Windows can generally be overcome by using a USB->Serial adapter to connect the CM11A to the PC. (Provided of course that at least one of the comm ports COM1 through  COM4 remains previously unassigned.)