Help - Search - Members - Calendar
Full Version: WinXP: Release locked serial port
Forums.MrPLC.com > PLCs and Supporting Devices > General Topics - The Lounge > Computer Help and Networking
transporter_ii
Verified this on at least three different laptops. If you open up GE MDS programming software (you don't even have to connect to an MDS radio), the comm port is left locked when you exit the software, and the next thing you want to use that uses the same comm port won't work. The fix is to go to Control Panel > System > Device Manager > Comm ports and turn off the comm port and turn it back on. The comm port will work fine after that.

Does anyone know of a batch script or little program that will release the comm port and free it up without having to go three layers deep into Device Manger and then having to click "no" to rebooting the computer on top of all of that?

Any thoughts would be greatly appreciated.

Thanks,

Transporter_ii
BobLfoot
QUOTE(transporter_ii @ Nov 22 2008, 09:29 AM) [snapback]76075[/snapback]

Verified this on at least three different laptops. If you open up GE MDS programming software (you don't even have to connect to an MDS radio), the comm port is left locked when you exit the software, and the next thing you want to use that uses the same comm port won't work. The fix is to go to Control Panel > System > Device Manager > Comm ports and turn off the comm port and turn it back on. The comm port will work fine after that.

Does anyone know of a batch script or little program that will release the comm port and free it up without having to go three layers deep into Device Manger and then having to click "no" to rebooting the computer on top of all of that?

Any thoughts would be greatly appreciated.

Thanks,

Transporter_ii

Just a thought - there must be a CPU process tying up the com post.

Try this.

Open your Task Manager and note all running processes.

Open and then close the MDs software.

Recheck Task manager and see what new process was left running.

Kill this process and see if you get your port back.

If that works, you should be able to craft a script or activeX to call a WinApI to kill that process.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2010 Invision Power Services, Inc.