I have a software app that is communicating to some hardware on
COM1... but I want to use COM1 for another application (while the
original app still runs). So, I want to release COM1 from that app
and use it on my new app... I don't want to share the COM Port between
the two... I simply want to release it from one app and use it in the
new one.
I didn't know where to post this question, but I thought that the
solution may lie within driver development.
I'd really appreciate any help.
> I have a software app that is communicating to some hardware on
> COM1... but I want to use COM1 for another application (while the
> original app still runs). So, I want to release COM1 from that app
> and use it on my new app... I don't want to share the COM Port between
> the two... I simply want to release it from one app and use it in the
> new one.
You could try disabling/enabling the port in question, assuming the
original app doesn't try to reclaim it when it comes back up (and also
assuming it drops its handle when the device disappears). A more
foolproof solution would be to layer some sort of upper filter on the
port that would control access somehow.
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
<davidm...@gmail.com> wrote in message
news:1c800b0e-23fe-4b4c...@34g2000hsh.googlegroups.com...
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply
<davidm...@gmail.com> wrote in message
news:1c800b0e-23fe-4b4c...@34g2000hsh.googlegroups.com...
> You should realize that if this is a for a general purpose application your
> ass will be sued. For instance, I know a glass artist who uses com1 to
> control her kiln, you mess with it and a multi-thousand dollar piece of art
> can be ruined.
Why do you think that lawsuit could possibly be won? Your glass
artist is the one who installed the offending application *and* ran
it.....and the EULA will just avow all damages
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply
<chris.a...@gmail.com> wrote in message
news:6a44e280-d8e2-4ba7...@t54g2000hsg.googlegroups.com...
as previously stated, you can't rip the COM port away from the
application unless the application is coded in a way that would allow
it (presumably by allowing sharing at handle creation).
however, i have discovered that you can create an upper-level driver
filter that will allow for control over the COM port's IRPs and such.
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
<davidm...@gmail.com> wrote in message
news:6ad0d49c-a3f2-43f5...@m44g2000hsc.googlegroups.com...
Doron Holan [MSFT] wrote:
> you can do that, but what will it mean? what if both apps want different
> baud rates? how will you know which app to report data to?
>
--
Ray
d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ray Trent" <r...@nospam.nospam> wrote in message
news:ehI9bAD...@TK2MSFTNGP02.phx.gbl...