raw ir allocated by IrCOMM... how to release it ?

Hi,

When WinCE 4.2 boots with IrDA support, the IrCOMM component opens the raw
IR port. A 3rd party application requires raw IR access too. Is it possible
for us to force IrCOMM to release the raw IR port allocation (disable it).
Then the 3rd party application would be able to open our raw IR port. After
the 3rd party application is done, we would like to tell IrCOMM to open the
raw IR port again (enable it).

Is such a scheme possible ?

I am asking because I think I approach this too difficult.

The difficult way would be to create two virtual COM ports that interface to
the same IrDA transceiver hardware. One would be for IrCOMM then, and one
for the 3rd party application. When the 3rd party application would open the
virtual COM port, then the virtual COM port for IrCOMM would 'disconnect'
itself from the IrDA transceiver hardware and let the 3rd party COM port get
control over it. IrCOMM would then not notice anything (except that it
doesn't get any IrDA input and all IrDA output just disappears...).

Please enlighten me. Can someone make me happy by telling me there is an
easy way ? I think I'm just not seeing it right now.

Thank you !

Ronald

Ronald
Wed Sep 24 10:04:57 CDT 2003

sorry, it looks like this has been answered before, going to try this now:

Re: Disable IrOBEX programatically
#define CTL_CODE( DeviceType, Function, Method, Access ) ( \ ((DeviceType)
<< 16) | ((Access) << 14) | ((Function) << 2) | (Method) \ ) #define ...
microsoft.public.windowsce.embedded.vc - 11 Aug 2003 by Amit - View Thread
(2 articles)

"Ronald Sloot" <ronald@waterlander.com> wrote in message
news:%23mdcIwogDHA.2984@TK2MSFTNGP11.phx.gbl...
> Hi,
>
> When WinCE 4.2 boots with IrDA support, the IrCOMM component opens the raw
> IR port. A 3rd party application requires raw IR access too. Is it
possible
> for us to force IrCOMM to release the raw IR port allocation (disable it).
> Then the 3rd party application would be able to open our raw IR port.
After
> the 3rd party application is done, we would like to tell IrCOMM to open
the
> raw IR port again (enable it).
>
> Is such a scheme possible ?
>
> I am asking because I think I approach this too difficult.
>
> The difficult way would be to create two virtual COM ports that interface
to
> the same IrDA transceiver hardware. One would be for IrCOMM then, and one
> for the 3rd party application. When the 3rd party application would open
the
> virtual COM port, then the virtual COM port for IrCOMM would 'disconnect'
> itself from the IrDA transceiver hardware and let the 3rd party COM port
get
> control over it. IrCOMM would then not notice anything (except that it
> doesn't get any IrDA input and all IrDA output just disappears...).
>
> Please enlighten me. Can someone make me happy by telling me there is an
> easy way ? I think I'm just not seeing it right now.
>
> Thank you !
>
> Ronald
>
>
>