hijacked com ports



I recently installed some x10 software, it stole my com1 and I can't get it
back. So far, I uninstalled the software, checked all startup entries in
msconfig, reviewed and closed any suspicious processes in task manager,
searched and removed registry entries for x10, and spent a lot of time
websearching for answers. (It seems nobody uses this I/O anachronism
anymore, so info is hard to come by.) Device manager says its "working
properly," but I cant access it with my other automation software on com1 or
with hyperterminal. How can I sort out what services/processes/applications
have commandeered this serial port and root them out?

Thanks, rpg.


rpg said:
I recently installed some x10 software, it stole my com1 and I can't get it

What is X10 software? If it caused a problem, contact the Author of


X10 software is a package for use with the X10 remote control/automation
system. X10 has been around since the 8080 days. Since it was "real time"
software, and maybe 16bit, I'm not suprised that it takes exclusive use of a
com port. X10's web site used to cause popup add problems until you used
blocking cookies.


Chuck is right about the software and the website. The manufacturer has
been contacted via email and a reply is awaited. The ill behaved software
includes drivers for 2 USB devices and is windows based. Chuck's point is
well taken about the origin of this stuff 20 some years ago and it may well
be that some of the legacy code lurks behind my problem. I posted this
question here however to answer the more generic question of how to query XP
and identify exactly what errant software is in control of a com port.
Most of the current home automation devices use this ancient conduit as does
my main system. I keep hoping someone will put out an Ethernet product. But
until then, I need to brush up on com port management.

Thanks for your replies.


I am experiencing a similar problem but do not beleive it to be application
related. I have tried both ActiveSync and Homecontrol (for the X10 devices)
and experience the same problem. However, if I do an uninstall of Com1 and
then reboot I can get the communication working UNTIL the very next reboot,
at which time I can no longer establish communications once again.

Have you been successful in resolving your problem?

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question