Re: How to get USB / Ethernet (NIC) working on MS Windows CE 5.0 ?

No, you're looking in the wrong place. Are you looking in the device
drivers section of the catalog or something? You want OS components, not
device drivers, for adding WiFi support...

Paul T.

"DES" <descasals@xxxxxxxxx> wrote in message
news:1163629783.480230.136160@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Paul,
Thanks for your input.

In Platform Builder, I already have in the OS Design :
Shell and User Interface
- User Interface :
- Network User Interface
- Driver for NDIS power management
- Network and Dial Up Connections UI
- UI for establishing and providing status for RAS
connections

But, in the Catalog, under Networking->Local Area Networking (LAN)
devices,
the following are listed :
- CISCO Aironet 340/350 .............. WLAN Card
- Intersil Prism2............................ PCMCIA Driver
- National Semiconductor......................
- NE2000...... (PCI card)
- NE2000...... (PCMCIA card)
- NE2000...... (ISA card)
- RealTek RTL8139
- RealTeak ....... Wi-Fi STA driver
- RealTeak ....... Wi-Fi AP driver
- SMS SMSC100FD

Should I add ALL the above to the OS Design ?

-Des

Paul G. Tobey [eMVP] wrote:
If you have been using Platform Builder for any length of time, you'll be
familiar with adding appropriate components, not DLLs, to an OS
configuration. Add the 802.11 components from the Network - Local Area
Networking (LAN) section of the catalog, after reading up on what they
are.
You also need the user interface for the networking stuff, so add Network
User Interface from the Shell & User Interface section.

Paul T.

"DES" <descasals@xxxxxxxxx> wrote in message
news:1163622280.735660.314580@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Paul,
You might have observed Luc Cool published a list of RNDIS compatible
USB adapters.I shall try one of them.
Presently, I have the following dlls :
USBprn.dll
USBMSC.dll
USBModem.dll
USBdisk6.dll
USBd.dll
USBhid.dll
USB8023.dll

I'm not aware which additional dlls I need to get 802.11 working.Also,
I do not have a wireless RNDIS compatible USB adapter at present.

Thanks,
-Des

Paul G. Tobey [eMVP] wrote:
All hardware is OS independent. The OS might be hardware-dependent,
but
never the other way around that I can think of.

You're getting the message because you don't have a driver for that
card.
The key phrase from my first message was, "Since the USR5421 is a
RNDIS
device (it provides a standard interface), and since there is a RNDIS
client
driver in Windows CE, the device works." The only way to know that
it's
RNDIS is for the vendor of the device to tell you so. If they don't
say
that, assume that it's not RNDIS.

Yes, Windows CE supports the USR5421 because it's RNDIS-compatible.
And,
yes, as it turns out, it's an 802.11b/g device and Windows CE provides
messages/capabilities that a driver for a device can express to
indicate
to
the OS that it's a wireless adapter. Windows CE can then display a
suitable
user interface for configuration of the wireless capabilities of the
adapter, as well as the more-ordinary IP properties of any network
adapter.
What DLLs are you looking for?

Paul T.

"DES" <descasals@xxxxxxxxx> wrote in message
news:1163619792.625864.318590@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Paul,
Thanks for your comments. So, if the USB device hardware is OS
independent, why am I getting the message "Unidentified USB Device"
when I plug in the Netgear FA120 USB adapter ?
Is FA120 NOT RNDIS compatible ?
How do I verify that a USB device is RNDIS compatible ?

You have mentioned that USR5421 works on WinCE. USR5421 is a
Wireless
LAN adapter. Does WinCE 5.0 support IEEE 802.11 ? I do not see the
relevant dlls in my Platform Builder 5.0.

-Des

Paul G. Tobey [eMVP] wrote:
The USB device hardware doesn't care what OS is running. As long
as
the
signals it gets over the USB bus are right, it doesn't even *know*
what
operating system is generating them. Since the USR5421 is a RNDIS
device
(it provides a standard interface), and since there is a RNDIS
client
driver
in Windows CE, the device works. Their specification is based on
the
driver
that they ship with the stick, which, as indicated, is a desktop
Windows
driver...

Paul T.

"DES" <descasals@xxxxxxxxx> wrote in message
news:1163613215.233726.18710@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for your response. Upon going thro' the tech. specs. for
USR5421, it listed 98SE / 2000 / ME / XP as the operating systems
supported. CE was not amomg them. Also, the connection protocol
is
IEEE
802.11 (as it is Wireless). We have 802.3 (wired ethernet)
driver.
Reg. U2ES, it is out of production as you had pointed out,
however
I'm
researching U2ESC (the next generation product). I'm in the
process
of
researching whether it supports WinCE.

Thanks,
DES

voidcoder wrote:
Is NETGEAR FA120 RNDIS class device? If not, why do you
try to use RNDIS driver for it?

You won't have much success with non RNDIS USB Ethernet
adapters, unless the manufacturer is providing CE drivers
for it.

Don't know any supported wired USB to Ethernet adapters,
but you may want to check wireless. There is a number of
RNDIS based USB WLAN adapters (like USR5421) supported
on CE. Anyway, Google is your friend.


DES wrote:
I need to get USB / Ethernet working on MS Windows CE 5.0.
Firstly, which device supports it ?
I was trying to use NETGEAR FA120. According to the tech.
manual,
Win
CE is NOT supported.

We are using Windows CE ver. 5.0 in our product and I have
been
trying
to get the RNDIS working; but have not been successful so far.
I have a NETGEAR Model FA120 USB / Ethernet adapter (NIC)
plugged
into
the USB port of our product running WinCE 5.0.

Is NETGEAR FA120 supported on Windows CE ? Their spec. does
not
list
Win CE (it lists 98, ME, 2000 and XP)

As soon as I plug in the NETGEAR NIC, I get the message
'Unidentified
USB Device' on my application console.
When I type the Driver name 'USB8023.DLL', I get the message :

4294860032 PID:4ffb6b3a TID:ac53bc2 0x8abe1400: >>> Loading
module
rndismp.dll at address 0x03660000-0x03674000 (RW data at
0x01F6A000-0x01F6A894)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\N40\RELDIR\N40_SH4_DEBUG\RNDISMP.DLL'
4294860036 PID:4ffb6b3a TID:ac53bc2 0x8abe1400: >>> Loading
module
usb8023.dll at address 0x03680000-0x03697000 (RW data at
0x01F6C000-0x01F6C5A7)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\N40\RELDIR\N40_SH4_DEBUG\USB8023.DLL'

4294861129 PID:4ffb6b3a TID:ac53bc2 0x8abe1400:
ParseUsbDescriptors
failed!
4294861132 PID:4ffb6b3a TID:ac53bc2 0x8abe1400: Invalid
Parameter

4294861134 PID:4ffb6b3a TID:ac53bc2 0x8abe1400: RNDISMP:
DllUnload
called!
4294861137 PID:4ffb6b3a TID:ac53bc2 0x8abe1400: <<< Unloading
module
usb8023.dll at address 0x03680000-0x03697000 (RW data at
0x01F6C000-0x01F6C5A7)
Unloaded symbols for
'C:\WINCE500\PBWORKSPACES\N40\RELDIR\N40_SH4_DEBUG\USB8023.DLL'
4294861141 PID:4ffb6b3a TID:ac53bc2 0x8abe1400: <<< Unloading
module
rndismp.dll at address 0x03660000-0x03674000 (RW data at
0x01F6A000-0x01F6A894)
Unloaded symbols for
'C:\WINCE500\PBWORKSPACES\N40\RELDIR\N40_SH4_DEBUG\RNDISMP.DLL'
4294861204 PID:8fdedd56 TID:ac53bc2 0x8abe1400: DlgMgr:
FindDlgItem
id
1 returning NULL.

I believe RNDISMP.DLL and USB8023.DLL are part of WinCE 5.0.
How
can
I
get it working so that the driver of the USB / Ethernet NIC
plugged
into the USB port is recognized ?
We do not have the source code for USB8023.DLL (part of
Microsoft
library).

The USB port itself on our product works as plugging a USB
flash
drive
works.







.

Relevant Pages