Notification from IrDA device arrival

NTDEV
1

Does anybody know how to know about IrDA device arrival asynchronously?
(i.e. not by periodically calling getsockopt(,IRLMP_ENUMDEVICES,)).
This must be possible, however not properly documented, because some
Windows components use this feature.

Thanks a lot for any information.
Paul

2

Zpr?vaMaybe WM_DEVICECHANGE helps?

----- Original Message -----
From: Paul Hrdina
To: NT Developers Interest List
Sent: Wednesday, November 27, 2002 1:24 PM
Subject: [ntdev] Notification from IrDA device arrival

Does anybody know how to know about IrDA device arrival asynchronously?
(i.e. not by periodically calling getsockopt(,IRLMP_ENUMDEVICES,)).
This must be possible, however not properly documented, because some
Windows components use this feature.

Thanks a lot for any information.
Paul

You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to %%email.unsub%%

3

I’m not sure if this is useful for IrDA devices which become
accessible from the IrDA adapter connected to your computer.
Unfortunately, the IrDA bus doesn’y

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Wednesday, November 27, 2002 1:38 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Notification from IrDA device arrival

Maybe WM_DEVICECHANGE helps?

----- Original Message -----
From: Paul Hrdina mailto:xxxxx
To: NT Developers Interest List mailto:xxxxx
Sent: Wednesday, November 27, 2002 1:24 PM
Subject: [ntdev] Notification from IrDA device arrival

Does anybody know how to know about IrDA device arrival asynchronously?
(i.e. not by periodically calling getsockopt(,IRLMP_ENUMDEVICES,)).
This must be possible, however not properly documented, because some
Windows components use this feature.

Thanks a lot for any information.
Paul

—
You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to %%email.unsub%%

—
You are currently subscribed to ntdev as: xxxxx@compelson.com
To unsubscribe send a blank email to %%email.unsub%%</mailto:xxxxx></mailto:xxxxx>

4

Don’t tell me that there is no one who can throw some light to this
topic!
I’m going more deeply now…There must be some possibility (and I hope
that it’s availbale for non-Microsoft products) to receive notifications
about
IrDA device state changes, however not properly documented.

At least one Windows component uses this feature - I mean the small icon
in taskbar, which:

  • appears when the first device starts to be in range
  • changes when the communication with the device is in progress or
    broken
  • disappears when the last device goes out of range.

Paul

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Paul Hrdina
Sent: Wednesday, November 27, 2002 11:24 AM
To: NT Developers Interest List
Subject: [ntdev] Notification from IrDA device arrival

Does anybody know how to know about IrDA device arrival asynchronously?
(i.e. not by periodically calling getsockopt(,IRLMP_ENUMDEVICES,)).
This must be possible, however not properly documented, because some
Windows components use this feature.

Thanks a lot for any information.
Paul

You are currently subscribed to ntdev as: xxxxx@compelson.com
To unsubscribe send a blank email to %%email.unsub%%

5

Zpr?vaPaul,

I’m going to play the devils advocate. Maybe your concentrating to much on “IrDA”. This “thing” connects to a bus, does it not? I would assume then that the signalling you mention is bubbling up from a bus-driver to the level that some task bar app can use it to toggle that indicator. Should you be loking at USB, SERIAL or PARALLEL bus-drivers? HID maybe?

I dunno …

–
Gary G. Little
Have Computer, Will Travel …
909-698-3191
909-551-2105
“Paul Hrdina” wrote in message news:xxxxx@ntdev…
Don’t tell me that there is no one who can throw some light to this topic!
I’m going more deeply now…There must be some possibility (and I hope
that it’s availbale for non-Microsoft products) to receive notifications about
IrDA device state changes, however not properly documented.

At least one Windows component uses this feature - I mean the small icon
in taskbar, which:
- appears when the first device starts to be in range
- changes when the communication with the device is in progress or broken
- disappears when the last device goes out of range.

Paul
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Paul Hrdina
Sent: Wednesday, November 27, 2002 11:24 AM
To: NT Developers Interest List
Subject: [ntdev] Notification from IrDA device arrival

Does anybody know how to know about IrDA device arrival asynchronously?
(i.e. not by periodically calling getsockopt(,IRLMP_ENUMDEVICES,)).
This must be possible, however not properly documented, because some
Windows components use this feature.

Thanks a lot for any information.
Paul

—
You are currently subscribed to ntdev as: xxxxx@compelson.com
To unsubscribe send a blank email to %%email.unsub%%

6

Yes, Gary, I agree with your “logical” point of view. However I think
that
this is one of those things which are completely hidden to the classic
Plug-and-Play manager. The IrDA communication interface is exposed
through the Winsock - so IrDA bus driver is NDIS driver.

The file af_irda.h contains some constants and structures to enumerate
the IrDA bus and connect to some device. But it doesn’t contain a way
of notification about changes on the bus… :-((.

And if the IrDA bus driver can be opened directly (through CreateFile)
to
be queried by some DeviceIoControl requests, I haven’t found any doc

Paul

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Friday, November 29, 2002 6:48 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Notification from IrDA device arrival

Paul,

I’m going to play the devils advocate. Maybe your concentrating to much
on “IrDA”. This “thing” connects to a bus, does it not? I would assume
then that the signalling you mention is bubbling up from a bus-driver to
the level that some task bar app can use it to toggle that indicator.
Should you be loking at USB, SERIAL or PARALLEL bus-drivers? HID maybe?

I dunno …

–
Gary G. Little
Have Computer, Will Travel …
909-698-3191
909-551-2105

“Paul Hrdina” < xxxxx@compelson.com> wrote in message news:xxxxx@ntdev…
Don’t tell me that there is no one who can throw some light to this
topic!
I’m going more deeply now…There must be some possibility (and I hope
that it’s availbale for non-Microsoft products) to receive notifications
about
IrDA device state changes, however not properly documented.

At least one Windows component uses this feature - I mean the small icon
in taskbar, which:

  • appears when the first device starts to be in range
  • changes when the communication with the device is in progress or
    broken
  • disappears when the last device goes out of range.

Paul

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Paul Hrdina
Sent: Wednesday, November 27, 2002 11:24 AM
To: NT Developers Interest List
Subject: [ntdev] Notification from IrDA device arrival

Does anybody know how to know about IrDA device arrival asynchronously?
(i.e. not by periodically calling getsockopt(,IRLMP_ENUMDEVICES,)).
This must be possible, however not properly documented, because some
Windows components use this feature.

Thanks a lot for any information.
Paul

You are currently subscribed to ntdev as: xxxxx@compelson.com
To unsubscribe send a blank email to %%email.unsub%%

You are currently subscribed to ntdev as: xxxxx@compelson.com
To unsubscribe send a blank email to %%email.unsub%%

7

Zpráva I would file a documentation bug to MS on this subject.

The thing is that MSDN Library contains the following note:

“The second approach to performing discovery of IrDA device addresses
is to perform a lazy discovery; in this approach, the application is
not notified until the discovered devices list changes from the last
discovery run by the stack.”

  • and contains it several times, but there is no description on
    how to do the lazy discovery.

Now let’s note the following from af_irda.h:

#if defined(_WIN32_WINNT) // WSAIoctl for lazy discovery
#define SIO_LAZY_DISCOVERY _IOR(‘t’, 127, u_long)
#endif

Why is it not documented on MSDN?

Max

8

Hi Max,
I already know about this feature, but it’s not enough because:

  1. it probably works on NT platform only, but what should I use on
    Windows 98, ME?
  2. there’s no possibility to know about changes when the communication
    with
    the device is in progress or broken and when the device goes out of
    range

So, what do you say now?
Paul

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Saturday, November 30, 2002 9:55 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Notification from IrDA device arrival

I would file a documentation bug to MS on this subject.

The thing is that MSDN Library contains the following note:

“The second approach to performing discovery of IrDA device addresses is
to perform a lazy discovery; in this approach, the application is not
notified until the discovered devices list changes from the last
discovery run by the stack.”

  • and contains it several times, but there is no description on how
    to do the lazy discovery.

Now let’s note the following from af_irda.h:

#if defined(_WIN32_WINNT) // WSAIoctl for lazy discovery
#define SIO_LAZY_DISCOVERY _IOR(‘t’, 127, u_long)
#endif

Why is it not documented on MSDN?

Max

You are currently subscribed to ntdev as: xxxxx@compelson.com
To unsubscribe send a blank email to %%email.unsub%%