WinCE 5 using USB RNDIS : LAN vs. W-LAN how to ?



Dear experts,



I have read carefully through all the available to me archive of this newsgroup on this topic and still unable to get things working right, even though several articles did report that it should. A while ago I have tried that and posted some questions, several people replied with useful info, but it still didn't work, now is the second round.



What is under investigation: Windows CE5 as Platform Builder with a cumulative annual QFE applied dated 12-31-2006. That should take care of many things I guess...



Goal is to make the USB rndis working right. The rndis device used is U.S.Robotics USR5421 USB to wireless LAN stick. Tested on PC and proven to work ok. Based on what I have read on this topic, the following environment variables were added to enable USB rndis support to either platform



set SYSGEN_USBFN_NET2280=1

set SYSGEN_ETH_USB_HOST=1

set SYSGEN_USBFN_ETHERNET=1

set SYSGEN_ETH_8021=1

set SYSGEN_NWIFI_STA=1



this should take care of everything needed ( if I understand it correctly).



Two development boards with :



1 --- ARM processor. Has 1 USB port. Built image (using command line) has standard explorer shell. Cmd line is supported, so one can type commands directly on the device. USB port correctly functions and recognizes both USB storage devices and USB printers. There is on-board Ethernet adapter already as well on-board wireless LAN adapter as well, for which 3rd party drivers are used.



Upon insertion of USR5421 into device's USB port no visual effects are seen, but "power" led on the USR5421 comes on, antenna light stays off. Taskbar is showing a new network adapter, as well as control panel->Networking gets another network adapter applet.



Question to this one:

a) what do I miss in terms of why does the USR5421 is detected as wired LAN adapter instead of wireless one ?

b) when using command line and trying to launch wireless zero configuration tool, an error is returned

wzctool -e

WZCEnumInterfaceg() error 0x00000002



2 --- VIA Luke (x86 like). Has 4 USB ports. Built image (using Platform Builder) has custom shell. No cmd line is supported in image. USB port correctly functions and recognizes both USB storage devices and USB printers. There is on-board Ethernet adapter already.



Upon insertion of USR5421 into device's USB port a pop-up dialog shows up, prompting to provide a driver name for unidentified USB device. Typing in the name of the dl lit should use, i.e. usb8023.dll, causes the dialog to pop up immediately back again and so forth indefinitely if repeated.



Question to that one: and why is that one not recognizing USR5421 at all, while the same environment variables were added to build ?





Please advise where to look.



Many thanks



Sergei R

.



Relevant Pages

  • Wireless USB Disconnects Work Around?
    ... my 802.11b wireless USB adapter disconnects randomly and without ... multiple wireless channels, played with all available "preamble type" ... share IRQ's with the USB host controller. ... I used a command built into Windows XP ...
    (microsoft.public.windowsxp.network_web)
  • Re: USB to Serial Bridge
    ... Ein nicht korrekt installiertes USB Gerät wird auch nicht mit Strom ... ATEN liefert nur einen Kabel USB zu Seriell Adapter. ... auf die *.inf Datei und installieren wählen. ... Der Treiber legt einen virtuellen COM Port an mit einer Nummer größer ...
    (microsoft.public.de.german.windowsxp.hardware)
  • Re: USB connected HDs
    ... connected the included external power adapter to the HD and the USB ... HDs I own and with USB flash drives. ... the auxiliary power supply connector. ...
    (microsoft.public.windowsxp.general)
  • Re: USB connected HDs
    ... the included external power adapter to the HD and the USB ... I own and with USB flash drives. ... the auxiliary power supply connector. ...
    (microsoft.public.windowsxp.general)
  • Re: PCMCIA to USB adapter? Hack?
    ... Find a 5Volt PCMCIA to/from USB v? ... Plug adapter ... The configuration of the RPLed files and drivers, ...
    (comp.sys.ibm.ps2.hardware)