Hello,

I'm developing an application that will automatically setup the wireless network depending on where the end-user actually is. The network information is pre-defined and I'm simply trying to load the wireless settings into the adapter and have it connect.

The problem I'm running into is that there is no external WiFi card on the device, PPT8846, however it does have wireless capabilities that can be set through the Connection Manager. I have iterated through the network interfaces, and the interface that is actually connected to a wireless network is not of the Wireless type per the SDF, but instead of the Ethernet type.

Any help as to how to get wireless settings implemented even though the SDF doesn't see the adapter as being wireless?

Thank you,
Jerry

OpenNETCF Network Interface diagnostic output:

3/21/03 12:28:27 PM
===========
Interface 196610
===========
 Type: NetworkInterface
 Name: NETWLAN1
 Description:
 Network Interface Type: Ethernet
 MAC: 00:15:70:9B:2D:12
 Operational Status: Up
 Speed: 1500bps
 *Interface Operational Status: Operational
 *Current IP: 10.0.0.103
 *Current Subnet: 255.255.255.0

 IP Properties
 -------------
 DHCP Server 0: 10.0.0.1
 DNS Server 0: 10.0.0.1
 Gateway 0: 10.0.0.1
 No WINS Servers
 Unicast address 0: 10.0.0.103
 Address Family: InterNetwork
 IPv4 Mask: {none}
 Preferred Lifetime: 604775
 Valid Lifetime: 4
 DHCP Lease Lifetime: 604775
 DAD State: Deprecated
 IS DNS Eligible
 IS NOT Transient
 Prefix Origin: 16
 Suffix Origin: OriginDhcp
 Unicast address 1: fe80::215:70ff:fe9b:2d12%6
 Address Family: InterNetworkV6
 Scope ID: 6
 Preferred Lifetime: 4294967295
 Valid Lifetime: 4
 DHCP Lease Lifetime: 4294967295
 DAD State: Preferred
 IS DNS Eligible
 IS Transient
 Prefix Origin: 28
 Suffix Origin: WellKnown
 No Anycast ad

 This is using the latest SDF (2.2) I assume?

The primary issue is that we ask the adapter to tells us what type it is.  If it conforms to a standard, like WZC, tehn we can control it.  If the OEM deviced to implement all of the wireless features with a proprietary interface (which is what it sounds like your OEM did) then you have no way of getting at the adapter without using their specific API.

Thanks for responding so quickly.

Yes, this was the latest SDF.

That makes sense. This is a Symbol PPT8846 and Symbol does provide an SDK for this platform, however, I feel I've exhausted the possibilities of using it simply because it can't make proper calls to the Fusion public API with their own libraries. Even their own example crashes out. This is my only alternative other than manually doing this, which is what we're trying to avoid.

I know this isn't Symbol support forums, but it appears the problem is a rather generic PPC2003 p/invoke problem. The specific error for the Symbol library is "FusionInterfaceOpen Failed : Unable to load Fusion public API". It uses FusionInterface.dll which appears isn't being properly utilize, or that it can't find fusion.dll on the system. Know anything about fusion.dll on the PPC?

Any ideas for fixing/tracking DllImport calls in .Net code for the PPC? Any managed code libaries to control the connection manager on PPC 2003's?

Thank you,
Jerry