Re: WZC wizard fails to start - Windows CE 5

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

---

• From: "Andrew at Plextek (www.plextek.co.uk)" <ams@xxxxxxxxxxx>
• Date: Mon, 30 Jul 2007 01:59:23 -0700

---

Sergei,

The catalog elements from the Platform Builder 5.0 IDE that you need
to select are as follows:

Catalog
\ Core OS
\ Windows CE Devices
\ Communications Services and Networking
\ Networking - Local Area Networks (LAN)
\ Wireless LAN (802.11) STA - Automatic Configuration and
802.1x
\ Networking Features
\ NDIS User-mode I/O Driver
\ Network Driver Architecture (NDIS)
\ Cose OS Services
\ USB Host Support
\ USB Remote NDIS Class Driver
\ Shell and User Interface
\ User Interface
\ Network User Interface

You will also need a USB host driver that will be specific to the BSP
and platform hardware.

This is the trace I get when I plug in my USR5421:

421095 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::HubStatusChangeThread - port 1, change = 0x0001, status = 0x0501
421290 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::HubStatusChangeThread - device attached on port 1
421290 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: +CHub(Root tier
0)::AttachDevice (USB 2) - port = 1, fIsLowSpeed = 0, fIsHighSpeed = 1
421290 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_OPENING_ENDPOINT0_PIPE, failures = 0
421291 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status = DEVICE_CONFIG_STATUS_USING_ADDRESS0,
failures = 0
421291 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_RESET_AND_ENABLE_PORT, failures = 0
421364 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR_TEST, failures =
0
421366 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_SET_ADDRESS, failures = 0
421368 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status = DEVICE_CONFIG_STATUS_LEAVE_ADDRESS0,
failures = 0
421379 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_DEVICE_DESCRIPTOR,
failures = 0
421381 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR, failures = 0
421383 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SETUP_CONFIGURATION_DESCRIPTOR_ARRAY, failures =
0
421384 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_CONFIG_DESCRIPTOR,
failures = 0
421385 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_CONFIG_DESCRIPTOR, failures = 0
421388 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE, failures = 0
421389 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - Select Configuration 0 on
DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE step
421389 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_SET_CONFIG, failures = 0
421390 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status = DEVICE_CONFIG_STATUS_CREATE_NEW_FUNCTION,
failures = 0
421390 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_INSERT_NEW_DEVICE_INTO_UPSTREAM_HUB_PORT_ARRAY,
failures = 0
421390 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: CHub(Root tier
0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SIGNAL_NEW_DEVICE_ENTER_OPERATIONAL_STATE,
failures = 0
421408 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: >>> Loading module
rndismp.dll at address 0x03280000-0x03299000 (RW data at
0x01F52000-0x01F52894)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\STARNOSETESTPLAT1\RELDIR
\STARNOSE_MIPSII_DEBUG\RNDISMP.DLL'
421462 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: >>> Loading module
usb8023.dll at address 0x032A0000-0x032BF000 (RW data at
0x01F54000-0x01F545A3)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\STARNOSETESTPLAT1\RELDIR
\STARNOSE_MIPSII_DEBUG\USB8023.DLL'
421573 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: +USBD:OpenPipe, EP:
0x81, MaxPkt: 16, Type: Interrupt
421574 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: -USBD:OpenPipe success,
hPipe = 4F08E0
421576 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: +USBD:OpenPipe, EP:
0x82, MaxPkt: 512, Type: Bulk
421577 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: -USBD:OpenPipe success,
hPipe = 4F0A10
421577 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: +USBD:OpenPipe, EP: 0x3,
MaxPkt: 512, Type: Bulk
421578 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: -USBD:OpenPipe success,
hPipe = 4F0AC0
421578 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: StartUsbThread
421580 PID:4ff692e2 TID:2fd58ca2 0x8fd58e00: -CHub(Root tier
0)::AttachDevice - port = 1, fIsLowSpeed = 0, address = 1
421589 PID:4ff692e2 TID:cf944692 0x8f901800: ==>NdisInitializeWrapper
421590 PID:4ff692e2 TID:cf944692 0x8f901800: <==NdisInitializeWrapper
421591 PID:4ff692e2 TID:cf944692 0x8f901800:
==>NdisMRegisterMiniport: NdisWrapperHandle 004F0C10
421592 PID:4ff692e2 TID:cf944692 0x8f901800:
==>ndisRegisterMiniportDriver: NdisWrapperHandle 004F0C10
421593 PID:4ff692e2 TID:cf944692 0x8f901800:
<==ndisRegisterMiniportDriver: MiniBlock 004F0C80
421593 PID:4ff692e2 TID:cf944692 0x8f901800: NdisMRegisterMiniport:
MiniBlock 004F0C80
421594 PID:4ff692e2 TID:cf944692 0x8f901800:
<==NdisMRegisterMiniport: MiniBlock 004F0C80, Status 0
421595 PID:4ff692e2 TID:cf944692 0x8f901800: InitializeWrapper:
successfully registered as a 4.0 miniport
421596 PID:4ff692e2 TID:cf944692 0x8f901800:
421598 PID:4ff692e2 TID:cf944692 0x8f901800: ndisMInitializeAdapter:
Miniport 004F1388,
421602 PID:4ff692e2 TID:cf944692 0x8f901800:
==>ndisQueueMiniportOnDriver: Miniport 004F1388, MiniBlock 004F0C80
421603 PID:4ff692e2 TID:cf944692 0x8f901800:
<==ndisQueueMiniportOnDriver: Miniport 004F1388, MiniBlock 004F0C80,
rc 1
421603 PID:4ff692e2 TID:cf944692 0x8f901800: RndismpInitialize
421637 PID:4ff692e2 TID:cf944692 0x8f901800: +++ LOOKASIDE INITIALIZE
+++ [72] bytes, depth [32]
421638 PID:4ff692e2 TID:cf944692 0x8f901800: +++ LOOKASIDE INITIALIZE
+++ [13] bytes, depth [32]
421639 PID:4ff692e2 TID:cf944692 0x8f901800: +++ LOOKASIDE INITIALIZE
+++ [29] bytes, depth [32]
421640 PID:4ff692e2 TID:cf944692 0x8f901800: RNDISMP: Init Req
message cf0000, Type 2, Length 24, MaxRcv 4096
421649 PID:4ff692e2 TID:4fc7fb5a 0x8f944000: > *** WARNING *** (file
d:\macallan\private\winceos\comm\ndismods\im\rndis\usb8023\rndis.c,
line 593)
421650 PID:4ff692e2 TID:4fc7fb5a 0x8f944000: Reducing adapter
MaxTransferSize from 4000h to 1000h
421655 PID:4ff692e2 TID:cf944692 0x8f901800: RNDISMP: InitComp:
Adapter 6a0000, Version 1.0, MaxPkt 1, AlignIncr 4, AlignMask
fffffffc, MaxXferSize 4096
421656 PID:4ff692e2 TID:cf944692 0x8f901800: ==>NdisMSetAttributesEx:
Miniport 004F1388
421663 PID:4ff692e2 TID:4fc7fb5a 0x8f944000: QueryComplete:
SupportedList: InfoBufLength 1376 (344 OIDs)
421671 PID:4ff692e2 TID:cf944692 0x8f901800:
==>NdisMRegisterAdapterShutdownHandler: Miniport 004F1388
421672 PID:4ff692e2 TID:cf944692 0x8f901800:
<==NdisMRegisterAdapterShutdownHandler: Miniport 004F1388
421690 PID:4ff692e2 TID:cf944692 0x8f901800: RNDISMP: Query for
OID_GEN_MAC_OPT not supported by device!
421717 PID:4ff692e2 TID:cf944692 0x8f901800: Invalid Set OID
(0001021A), Adapter 6a0000
421719 PID:4ff692e2 TID:cf944692 0x8f901800: NDIS: Adapter USB80231 -
NOT using OPTIMIZED RX handler
421723 PID:4ff692e2 TID:f94423a 0x8fc04000: RNDISMP: Query for
OID_GEN_MAC_OPT not supported by device!
421759 PID:4ff692e2 TID:8fd98852 0x8fc04de8: NDISPWR:: BIND
notification for adapter [USB80231]
421841 PID:4ff692e2 TID:cfbeeaaa 0x8f949d30: RNDISMP: Query for
OID_GEN_MAC_OPT not supported by device!
421927 PID:4ff692e2 TID:6f94423a 0x8f9729b8: Invalid Set OID
(00010119), Adapter 6a0000
421931 PID:4ff692e2 TID:6f956e1a 0x8f962800: ZCF:: InfContext
[0x4f3020] created..
421948 PID:4ff692e2 TID:cf944692 0x8f901800: +OpenIFConfigEx(Comm
\USB80231\Parms\TCPIP Handle 0x652F728)
421949 PID:4ff692e2 TID:cf944692 0x8f901800: +OpenIFConfig(Comm
\USB80231\Parms\TCPIP Handle 0x652F728)
421950 PID:4ff692e2 TID:cf944692 0x8f901800: Opened registry info for
Comm\USB80231\Parms\TCPIP
421951 PID:4ff692e2 TID:cf944692 0x8f901800: -OpenIFConfig(Comm
\USB80231\Parms\TCPIP *Handle 0x652F728, BOOL Ret: 1)
421952 PID:4ff692e2 TID:cf944692 0x8f901800: -OpenIFConfigEx(Comm
\USB80231\Parms\TCPIP *Handle 0x652F728, BOOL Ret: 1)
421952 PID:4ff692e2 TID:cf944692 0x8f901800: *CloseIFConfig(Handle
0xD6770)
421953 PID:4ff692e2 TID:cf944692 0x8f901800: +OpenIFConfig(Comm
\USB80231\Parms\TCPIP Handle 0x652F4D0)
421954 PID:4ff692e2 TID:cf944692 0x8f901800: Opened registry info for
Comm\USB80231\Parms\TCPIP
421955 PID:4ff692e2 TID:cf944692 0x8f901800: -OpenIFConfig(Comm
\USB80231\Parms\TCPIP *Handle 0x652F4D0, BOOL Ret: 1)
421956 PID:4ff692e2 TID:cf944692 0x8f901800:
+GetGeneralIFConfig(ConfigInfo 0x652F4D8 Handle 0xD6770)
421956 PID:4ff692e2 TID:cf944692 0x8f901800:
GetGeneralIFConfig:Unable to read DefaultGateway value!
421957 PID:4ff692e2 TID:cf944692 0x8f901800:
GetGeneralIFConfig:Unable to read DNS value!
421958 PID:4ff692e2 TID:cf944692 0x8f901800:
GetGeneralIFConfig:Unable to read WINS value!
421959 PID:4ff692e2 TID:cf944692 0x8f901800:
GetGeneralIFConfig:Unable to read UseZeroBroadcast value!
All-nets broadcasts will be addressed to 255.255.255.255
421960 PID:4ff692e2 TID:cf944692 0x8f901800: -
GetGeneralIFConfig(ConfigInfo 0x652F4D8 Handle 0xD6770 Ret: TRUE)
421960 PID:4ff692e2 TID:cf944692 0x8f901800: +GetIFAddrList(NumAddr*
0x652F570 Handle 0xD6770)
421961 PID:4ff692e2 TID:cf944692 0x8f901800: *IPAddNTE: calling
ARPDynRegister
422188 PID:4ff692e2 TID:4fc7fb5a 0x8f944000: NDIS: Adapter USB80231 -
NOT using OPTIMIZED RX handler
422201 PID:4ff692e2 TID:4fc7fb5a 0x8f944000: Adapter 6a0000: ---
Media Disconnect ---
422302 PID:4ff692e2 TID:cf944692 0x8f901800: IPAddInterface:
PhysicalMedium == NdisPhysicalMediumWirelessLan
422303 PID:4ff692e2 TID:cf944692 0x8f901800: IPAddInterface: Wireless
LAN default to no ConnectDampingInterval.
422304 PID:4ff692e2 TID:cf944692 0x8f901800: IPAddInterface: Wireless
LAN default to no DisconnectDampingInterval.
422305 PID:4ff692e2 TID:cf944692 0x8f901800: *CloseIFConfig(Handle
0xD6770)
422306 PID:4ff692e2 TID:cf944692 0x8f901800: +OpenIFConfig(Comm
\USB80231\Parms\TCPIP Handle 0x652F45C)
422307 PID:4ff692e2 TID:cf944692 0x8f901800: Opened registry info for
Comm\USB80231\Parms\TCPIP
422308 PID:4ff692e2 TID:cf944692 0x8f901800: -OpenIFConfig(Comm
\USB80231\Parms\TCPIP *Handle 0x652F45C, BOOL Ret: 1)
422308 PID:4ff692e2 TID:cf944692 0x8f901800: *CloseIFConfig(Handle
0xD6770)
422309 PID:8fcc2fb2 TID:cf944692 0x8f901800: [NOTIFY]
HandleSystemEvent 5 none
422312 PID:4ff692e2 TID:cf944692 0x8f901800: DHCP:: $$$ NewDhcpInfo:
0x4fe090
422312 PID:4ff692e2 TID:cf944692 0x8f901800: -RequestWLan: Context 3
422313 PID:4ff692e2 TID:cf944692 0x8f901800: -IPAddInterface
[SUCCESS]
422316 PID:4ff692e2 TID:8fda90f2 0x8fda3028: NotifyChange: Setting
Event 8FA11712
422319 PID:4ff692e2 TID:8fda90f2 0x8fda3028: NotifyChange: Setting
Event 8FA11712
422320 PID:4ff692e2 TID:8fda90f2 0x8fda3028: NotifyChange: Setting
Event 2FC04D9A
422321 PID:4ff692e2 TID:8fda90f2 0x8fda3028: NotifyChange: Setting
Event FC51BDA
422377 PID:8fcc2fb2 TID:afcccf62 SMBSRV: invalid LANA on context 3,
maybe the IP isnt valid?
422425 PID:8fcc2fb2 TID:afcccf62 SMBSRV: invalid LANA on context 3,
maybe the IP isnt valid?
422480 PID:4ff692e2 TID:6f956e1a 0x8f962800: ZCF:: OpenIntfHandle()
creating new handle for [USB80231]
422483 PID:4ff692e2 TID:2fb9dfb2 0x8f9729b8: NDIS: Adapter USB80231 -
NOT using OPTIMIZED RX handler
422567 PID:4ff692e2 TID:6fbeea82 0x8f901800: NDIS: Adapter USB80231 -
NOT using OPTIMIZED RX handler
422569 PID:4ff692e2 TID:6f956e1a 0x8f962800: ZCF:: OpenIntfHandle()
creating new handle for [USB80231]
422572 PID:4ff692e2 TID:cfb6bf42 0x8f9729b8: NDIS: Adapter USB80231 -
NOT using OPTIMIZED RX handler
422625 PID:4ff692e2 TID:4fc7fb5a 0x8f944000: Query Complete (Oid =
0D010122): error status C0010014
422640 PID:4ff692e2 TID:6f956e1a 0x8f962800: ZCF:: OpenIntfHandle()
already has handle for [USB80231]
422660 PID:4ff692e2 TID:4f95aaf2 0x8f901800: WZC: NIO RecvThread
4f95aaf2 STARTING 4f8a00
422773 PID:4ff692e2 TID:6f956df2 0x8f949d30: NETUIQC: Could not find
the systray icon associated with the given device name
422814 PID:4ff692e2 TID:2fbee852 0x8fc04000: Loading of Module
'aygshell.dll' (8fca2e40) failed, prevRefCnt = 0, refcnt = 1, inuse =
00000024, dwErr = 0000000e
422836 PID:4ff692e2 TID:2fbee852 0x8fc04000: Loading of Module
'aygshell.dll' (8fca2e40) failed, prevRefCnt = 0, refcnt = 1, inuse =
00000024, dwErr = 0000000e
422842 PID:4ff692e2 TID:2fbee852 0x8fc04000: Loading of Module
'aygshell.dll' (8fca2e40) failed, prevRefCnt = 0, refcnt = 1, inuse =
00000024, dwErr = 0000000e
422904 PID:8fd9ef92 TID:2fbee852 0x8fc04000: DlgMgr: FindDlgItem id 1
returning NULL.
423119 PID:8fd9ef92 TID:2fbee852 0x8fc04000: DlgMgr: FindDlgItem id 1
returning NULL.
423126 PID:4ff692e2 TID:2fbee852 0x8fc04000: Loading of Module
'aygshell.dll' (8fca2e40) failed, prevRefCnt = 0, refcnt = 1, inuse =
00000024, dwErr = 0000000e
423132 PID:4ff692e2 TID:2fbee852 0x8fc04000: Loading of Module
'aygshell.dll' (8fca2e40) failed, prevRefCnt = 0, refcnt = 1, inuse =
00000024, dwErr = 0000000e
423229 PID:8fd9ef92 TID:2fbee852 0x8fc04000: DlgMgr: FindDlgItem id 1
returning NULL.
427591 PID:8fcc2fb2 TID:afca253a 0x8fcaaca8: TEL_IOControl(0xFB25B8,
17039424, 0xE0AF648, 2048, 0x0, 0, 0x0)
427592 PID:8fcc2fb2 TID:afca253a 0x8fcaaca8: FTP_IOControl(0x1,
17039424, 0xE0AF648, 2048, 0x0, 0, 0x0)
427593 PID:8fcc2fb2 TID:afca253a +SMB_IOControl, unknown code
0x1040040

Regards,
Andrew.




On Jul 27, 6:32 pm, "Sergei R" <rusa...@xxxxxxxxxxxxxx> wrote:

Hello experts,

some two weeks ago I have posted a question not being able to make USB RNDIS
adapter to work on both ARM and x86 platform, despite the fact that I have
read and implemented all the steps ever mentioned in this newsgroup regaring
USB RNDIS support in Windows CE 5 to work with U.S.Robotics usr5421.

No one replied. Anyways, I had a chance to go over debugger output and see,
that when usr5421 is inserted into usb slot of the platform device, many
steps go well and it is detected as network device properly, and further
maybe even as wireless network device, but that step never completes. It was
expected that Wireless Zero Config would launch a wizard when such new
wireless network device is added to the system, but it never happened. Debug
output shows this happening

....
437134 PID:7afc38e6 TID:7aee4f9e 0x9ac7f4c8: +USBD:IssueInterruptTransfer,
pipe:2A5020, dwFlags:0x380, Bufsize: 16 vBuf:0x5D0000, pBuf:0x0
437273 PID:7afc38e6 TID:9aeeb326 0x9aeeba0c: RndismpReset: Adapter 590000
437273 PID:7afc38e6 TID:9aeeb326 0x9aeeba0c: Flush done, adapter 590000
437273 PID:7afc38e6 TID:9aeeb326 0x9aeeba0c: RNDISMP:: Sending ResetOID to
microport.
437325 PID:7afc38e6 TID:fabcd69e 0x9ac64b18: NETUIQC: Unable to open key
[Drivers\BuiltIn\Ethman\Log]
437374 PID:7afc38e6 TID:fabcd69e 0x9ac64b18: >>> Loading module wzcsapi.dll
at address 0x03700000-0x03708000 (RW data at 0x01F67000-0x01F67494)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\TT8560_CUSTOM\RELDIR\TT8560_ARMV4I_DEBUG\WZCSAPI.­DLL'
437785 PID:7afc38e6 TID:fabcd69e 0x9ac64b18: WZCSAPI:: CreateFile()
failed..
437785 PID:7afc38e6 TID:fabcd69e 0x9ac64b18: WZCSAPI:: QueryInterface()..
Err[0x2]
437785 PID:7afc38e6 TID:fabcd69e 0x9ac64b18: !WZCUI: WZCQueryInterfaceEx
failed 0x2
437785 PID:7afc38e6 TID:fabcd69e 0x9ac64b18: NETUIQC: Warning - failed to
get wireless info
437841 PID:7afc38e6 TID:fabcd69e 0x9ac64b18: WZCSAPI:: CreateFile()
failed..
437841 PID:7afc38e6 TID:fabcd69e 0x9ac64b18: NETUIQC: WZCQueryContext
failed 0x2
438092 PID:7afc38e6 TID:7aee4f9e 0x9ac7f4c8: -USBD:IssueInterruptTransfer,
pTransfer:0x2A8400
438092 PID:7afc38e6 TID:7aee4f9e 0x9ac7f4c8: +USBD:GetTransferStatus
438092 PID:7afc38e6 TID:7aee4f9e 0x9ac7f4c8: -USBD:GetTransferStatus
....

So as one may see that wireless zero config does in fact attempt to start,
but fails with error 2. Can anyone please comment on that - what does this
wzc need to actually run ? All the possible components for wireless
networking are included into the image.

Thank you

Sergei R

.

---

• Follow-Ups:
  • Re: WZC wizard fails to start - Windows CE 5
    • From: Sergei R

• References:
  • WZC wizard fails to start - Windows CE 5
    • From: Sergei R

• Prev by Date: Re: URL to get support using PB license code
• Next by Date: Re: Stripping down the image via manually editing CE.BIB
• Previous by thread: Re: WZC wizard fails to start - Windows CE 5
• Next by thread: Re: WZC wizard fails to start - Windows CE 5
• Index(es):
  • Date
  • Thread

---

Relevant Pages Re: WZC wizard fails to start - Windows CE 5 ... Interesting that despite some failures, like unable to open icon in systray and foad failed for aygshell.dll it worked for you. ... \ Network User Interface ... NOT using OPTIMIZED RX handler ... maybe even as wireless network device, ... (microsoft.public.windowsce.platbuilder) TidBITS#785/27-Jun-05 ... Jeff Carlson continues his exploration of computerized poker ... and Adam examines both the Canary Wireless ... Rogue Amoeba's Audio Hijack Pro ... A Canary in the Network ... (comp.sys.mac.digest) Re: Linksys NAS200 Network Storage adapter ... The only two wireless network settings that are of any consequence are the SSID and the encryption method and password. ... either click the "Print Network Settings" button on the final screen of the Wizard or simply access the appropriate XML file and get at them that way and then use the information to configure the router manually as I explained earlier. ... I've read thru some of the MS web site on that product and it appears to do everything a NAS will do plus other cool features, such as, with an xbox360 with the wireless adapter, I can stream my video/pics to my TV for family viewing. ... (microsoft.public.windowsxp.network_web) [NMRC Advisory] Microsoft Windows Wireless Exposure on Laptops ... Application: Wireless Network Connection ... This advisory documents an anomaly involving Microsoft's Wireless Network ... If a laptop connects to an ad-hoc network it can later start ... This is known as a Link-Local address, and by default Link-Local is turned on on all Windows platforms on all interfaces, including wireless interfaces. ... (Bugtraq) RE: palm VIIx wireless modem ... Here is a Wireless LAN Security FAQ, ... What are solutions to minimizing WLAN risk? ... that connects clients to the internal network. ... (Security-Basics)

---

• Windows
• Science
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

www.tech-archive.net  > Archive  > WindowsCE  > microsoft.public.windowsce.platbuilder  > 2007-07