Re: Problem with OpenNetCF.Net adapter
From: Paul G. Tobey [eMVP] (ptobey_no_spam_at_instrument_no_spam.com)
Date: 05/27/04
- Next message: Mark Arteaga: "Custom PB SDK in VS.Net"
- Previous message: William Ryan eMVP: "Re: Potential Memory Leak with DataSet ?"
- In reply to: Paul G. Tobey [eMVP]: "Re: Problem with OpenNetCF.Net adapter"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 27 May 2004 12:54:13 -0700
We have a fixed version to be tested. Someone will post here when the fix
is actually available publicly.
Paul T.
"Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument_no_spam.com> wrote in
message news:%23yS5G8AREHA.4016@TK2MSFTNGP12.phx.gbl...
> I should have a fix for testing in the source today. Note that there may
be
> some minor changes to the API.
>
> Paul T.
>
> "Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument_no_spam.com> wrote in
> message news:uOOYqFAREHA.2876@TK2MSFTNGP09.phx.gbl...
> > There are two possible sources of the problem that I see, one more
likely
> > than the other:
> >
> > 1. There might be no adapters in the list (less likely cause).
> >
> > 2. Rather than using the Next field of the current IP_ADAPTER_INFO
> structure
> > to find the next one, we're assuming that each one is the same size. A
> > similar problem showed up in one of the SSID-related enumerations.
> > Apparently, some network adapters return information differently and the
> > network stack simply passes that along. The problem, if this is the
case,
> > is in IP_ADAPTER_INFO.NextAdapter(). A fix might be to keep, rather
than
> > just an index value, the actual offset within the byte array of the
> current
> > adapter information. Alternatively, each time a NextAdapter() is done,
> > you'd have to step through the list from the beginning, counting each
Next
> > as you went through it until you got to the index you wanted. The
> > NDIS_802_11_BSSID_LIST class does it this way (check the Item method).
> >
> > Paul T.
> >
> > "Peter Foot [MVP]" <feedback@nospam-inthehand.com> wrote in message
> > news:OTM3Aj9QEHA.1624@TK2MSFTNGP09.phx.gbl...
> > > This is a known issue with the v1.1 release which only affects certain
> > > devices. We are currently investigating the issue. For a list of
> currently
> > > known issues please see the release-notes:-
> > >
> >
>
http://www.opennetcf.org/PermaLink.aspx?guid=a8b2c046-b9fd-4b0b-bd21-f0d03f6bec55
> > >
> > > Peter
> > >
> > > --
> > > Peter Foot
> > > Windows Embedded MVP
> > > www.inthehand.com | www.opennetcf.org
> > >
> > > "Francesco" <cescoc@yahoo.it> wrote in message
> > > news:f0078d13.0405270124.1bc6ba4b@posting.google.com...
> > > > Hi everybody.
> > > > I have writed a small test application to understand the
> > > > functionalities offered by OpenNetCF.Net namespace.
> > > >
> > > > My problem is that, when i do this call in the code:
> > > >
> > > > AdapterCollection ac = OpenNETCF.Net.Networking.GetAdapters();
> > > >
> > > > I get the following excpetion:ArgumentOutOfRangeException
> > > > it seems very strange to me, in fact i don't give any argument to
the
> > > > method...
> > > >
> > > > Anyone can help?
> > > > I tested it in a pocketPc2002, maybe the openNet framework is
designed
> > > > for pocketPc 2003?
> > > >
> > > > Thanks for your answers.
> > > > Francesco
> > >
> > >
> >
> >
>
>
- Next message: Mark Arteaga: "Custom PB SDK in VS.Net"
- Previous message: William Ryan eMVP: "Re: Potential Memory Leak with DataSet ?"
- In reply to: Paul G. Tobey [eMVP]: "Re: Problem with OpenNetCF.Net adapter"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
