Re: Cisco Aironet 350 & CE.NET 4.2
From: Michel Verhagen [eMVP] (michel.verhagen_at_nospam.pts.nl)
Date: 07/08/04
- Next message: Derek Ou: "Re: an easy question"
- Previous message: Bruce Eitman \(eMVP\): "Re: SOURCELIBS and TARGETLIBS"
- In reply to: Michel Verhagen [eMVP]: "Re: Cisco Aironet 350 & CE.NET 4.2"
- Next in thread: Tweeeek: "Re: Cisco Aironet 350 & CE.NET 4.2"
- Reply: Tweeeek: "Re: Cisco Aironet 350 & CE.NET 4.2"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 8 Jul 2004 17:28:00 +0200
I just copied the pcx500.dll (cisco driver) from 4.1 to 4.2, and now my card
works!
Or... At least ZeroConfig doesn't error out any more... Could it be my cisco
card is damaged, and the old driver is not using that part of the card, but
the new driver is?
Paul, any idea?
Thx,
Michel.
"Michel Verhagen [eMVP]" <michel.verhagen@nospam.pts.nl> wrote in message
news:%23Gj2yMMZEHA.4032@TK2MSFTNGP11.phx.gbl...
> SYSINTR seems ok, I/O seems ok, 4.1 works ok, 4.2 doesn't. I didn't try it
> on 5.0 yet...
>
> I'll keep on searching...
>
> Thx,
>
> Michel Verhagen, eMVP
> Windows CE Consultant
> PTS Software
> The Netherlands
> [if you want to reply to me directly, remove .nospam from my email
address]
>
>
> "Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument_no_spam.com> wrote in
> message news:uG7g9iDZEHA.2216@TK2MSFTNGP10.phx.gbl...
> > No, I don't recognize anything that is just plain wrong there. Any
chance
> > that some registry entry is assigning the wrong SYSINTR value or wrong
> base
> > I/O or memory address to something, differently than what happened in
> CE.NET
> > 4.x? You're running 5.0 here, right?
> >
> > Paul T.
> >
> > "Michel Verhagen [eMVP]" <michel.verhagen@nospam.pts.nl> wrote in
message
> > news:OtNbOp$YEHA.2516@TK2MSFTNGP10.phx.gbl...
> > > Paul,
> > >
> > > The thing is: The card works like a charm when using Windows CE 4.1,
so
> > > hardware is okay. We are developing on an Advantech TPC1560, so
standard
> > > hardware. Even when downloading the new drivers from Cisco, we have
> > similar
> > > problems (somewhat different debug output, but still not working).
I've
> > also
> > > upgraded the firmware to the last version (5.41).
> > >
> > > Any more ideas? I'm really stuck here, because source of the zero
config
> > > stuff is not available.
> > >
> > > Thanks,
> > >
> > > Michel Verhagen, eMVP
> > > Windows CE Consultant
> > > PTS Software
> > > The Netherlands
> > > [if you want to reply to me directly, remove .nospam from my email
> > address]
> > >
> > >
> > > "Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument_no_spam.com> wrote
in
> > > message news:%23rsn$v4YEHA.3432@TK2MSFTNGP10.phx.gbl...
> > > > Michel,
> > > >
> > > > I'd check whether the hardware has things like the interrupt request
> pin
> > > > from the card slot pulled to the correct state (low, I think), with
> > > > resistors of the right size. It almost seems as though an incorrect
> > > > resistor value (or values on multiple lines), are in use, causing
> > strange
> > > > signal values. We don't see that with the 350 card on our
> PXA255-based
> > > > devices (more than one).
> > > >
> > > > Paul T.
> > > >
> > > > "Michel Verhagen [eMVP]" <michel.verhagen@nospam.pts.nl> wrote in
> > message
> > > > news:eo$zrh2YEHA.3564@TK2MSFTNGP11.phx.gbl...
> > > > Hi,
> > > >
> > > > There's been a lot of discussion about the Cisco Aironet 350, but I
> > can't
> > > > find any solution to the problem I'm seeing...
> > > >
> > > > I've used the Aironet 340/350 on several different (all x86 based)
> > > devices,
> > > > and I've never encountered this problem. Maybe somebody else has
seen
> it
> > > > before, I've marked the important things red (not sure this ng
> supports
> > > rich
> > > > text though...):
> > > >
> > > > 0x86f89d7c: PCMCIA:IREQInt: Got interrupt, but no IREQ owner!!!
> > > > 0x86d80dc4: PCMCIA:LoadPCCardDriver:
> > > >
> > >
> >
>
RegOpenKeyEx(Drivers\PCMCIA\Cisco_Systems-350_Series_Wireless_LAN_Adapter-51
> > > > 2A) returned 2
> > > > 0x86d80dc4: PCMCIA:RunDetectors: 3 detection modules
> > > > 0x86d80dc4: >>> Loading module serial.dll at address
> > 0x03790000-0x037A6000
> > > > (RW data at 0x01F75000-0x01F755E8)
> > > > Loaded symbols for
> > > > 'C:\WINCE420\PUBLIC\ADVTPCTEST\RELDIR\ADVTPCDEBUG\SERIAL.DLL'
> > > > 0x86d80dc4: PCMCIA:RunDetectors: calling 10:SERIAL.DLL:DetectModem
> > > > Unloaded symbols for
> > > > 'C:\WINCE420\PUBLIC\ADVTPCTEST\RELDIR\ADVTPCDEBUG\SERIAL.DLL'
> > > > 0x86d80dc4: +DetectModem 6, , 138
> > > > 0x86d80dc4: <<< Unloading module serial.dll at address
> > > 0x03790000-0x037A6000
> > > > (RW data at 0x01F75000-0x01F755E8)
> > > > 0x86d80dc4: >>> Loading module pcx500.dll at address
> > 0x039D0000-0x039E5000
> > > > (RW data at 0x01F92000-0x01F92B51)
> > > > Loaded symbols for
> > > > 'C:\WINCE420\PUBLIC\ADVTPCTEST\RELDIR\ADVTPCDEBUG\PCX500.DLL'
> > > > 0x86d80dc4: Cisco DLL_PROCESS_ATTACH Handle=0x86e1ce48
> > > > 0x86d80dc4: PCMCIA:RunDetectors: calling 41:pcx500.DLL:DetectPCX500
> > > > 0x86d80dc4: Cisco DetectCisco Routine Handle=0x86d80000
> > > > 0x86d80dc4: Cisco Loaded Pcmcia, Handle=0x86f90cf0
> > > > 0x86d80dc4: Cisco: Detected Cisco Card
> > > > 0x86d80dc4: Cisco DLL_PROCESS_DETACH
> > > > 0x86d80dc4: <<< Unloading module pcx500.dll at address
> > > 0x039D0000-0x039E5000
> > > > (RW data at 0x01F92000-0x01F92B51)
> > > > Unloaded symbols for
> > > > 'C:\WINCE420\PUBLIC\ADVTPCTEST\RELDIR\ADVTPCDEBUG\PCX500.DLL'
> > > > 0x86d80dc4: PCMCIA:RunDetectors: 41:pcx500.DLL:DetectPCX500 returned
> > CISCO
> > > > 0x86d80dc4: DEVICE!ActivateDeviceEx(Drivers\PCMCIA\CISCO) entered
> > > > 0x86d80dc4: >>> Loading module pcx500.dll at address
> > 0x039D0000-0x039E5000
> > > > (RW data at 0x01F92000-0x01F92B51)
> > > > Loaded symbols for
> > > > 'C:\WINCE420\PUBLIC\ADVTPCTEST\RELDIR\ADVTPCDEBUG\PCX500.DLL'
> > > > 0x86d80dc4: Cisco DLL_PROCESS_ATTACH Handle=0x86e1ce48
> > > > 0x86d80dc4: PCX500:: Initializing..
> > > > ==>NdisInitializeWrapper
> > > > <==NdisInitializeWrapper
> > > > ==>NdisMRegisterMiniport: NdisWrapperHandle 0005ED50
> > > > ==>ndisRegisterMiniportDriver: NdisWrapperHandle 0005ED50
> > > > <==ndisRegisterMiniportDriver: MiniBlock 0005EDC0
> > > > NdisMRegisterMiniport: MiniBlock 0005EDC0
> > > > <==NdisMRegisterMiniport: MiniBlock 0005EDC0, Status 0
> > > > 0x86d80dc4: PCX500:: Initialization done [Successful]
> > > >
> > > > ndisMInitializeAdapter: Miniport 00055F18,
> > > > ==>ndisQueueMiniportOnDriver: Miniport 00055F18, MiniBlock 0005EDC0
> > > > <==ndisQueueMiniportOnDriver: Miniport 00055F18, MiniBlock 0005EDC0,
> rc
> > 1
> > > > ==>NdisMSetAttributesEx: Miniport 00055F18
> > > > ***NDIS*** (a, 514)
> > > > ==>NdisMRegisterInterrupt: Miniport 00055F18 Vector 3
> > > > ***NDIS*** (a, 719)
> > > > <==NdisMRegisterInterrupt: Miniport 00055F18, Status 0
> > > > ==>NdisMRegisterAdapterShutdownHandler: Miniport 00055F18
> > > > <==NdisMRegisterAdapterShutdownHandler: Miniport 00055F18
> > > > 0x86d80dc4: PCX500:: OID_GEN_MEDIA_CONNECT_STATUS return
> [Disconnected]
> > > > 0x86d80dc4: +OpenIFConfigEx(Comm\CISCO1\Parms\TCPIP Handle
0x832E730)
> > > > 0x86d80dc4: +OpenIFConfig(Comm\CISCO1\Parms\TCPIP Handle 0x832E730)
> > > > 0x86d80dc4: Opened registry info for Comm\CISCO1\Parms\TCPIP
> > > > 0x86d80dc4: -OpenIFConfig(Comm\CISCO1\Parms\TCPIP *Handle 0x832E730,
> > BOOL
> > > > Ret: 1)
> > > > 0x86d80dc4: -OpenIFConfigEx(Comm\CISCO1\Parms\TCPIP *Handle
0x832E730,
> > > BOOL
> > > > Ret: 1)
> > > > 0x86d80dc4: *CloseIFConfig(Handle 0x86D30)
> > > > 0x86d80dc4: +OpenIFConfig(Comm\CISCO1\Parms\TCPIP Handle 0x832E63C)
> > > > 0x86d80dc4: Opened registry info for Comm\CISCO1\Parms\TCPIP
> > > > 0x86d80dc4: -OpenIFConfig(Comm\CISCO1\Parms\TCPIP *Handle 0x832E63C,
> > BOOL
> > > > Ret: 1)
> > > > 0x86d80dc4: +GetGeneralIFConfig(ConfigInfo 0x832E5D4 Handle 0x86D30)
> > > > 0x86d80dc4: GetGeneralIFConfig:Unable to read DefaultGateway value!
> > > > 0x86d80dc4: GetGeneralIFConfig:Unable to read DNS value!
> > > > 0x86d80dc4: GetGeneralIFConfig:Unable to read WINS value!
> > > > 0x86d80dc4: GetGeneralIFConfig:Unable to read UseZeroBroadcast
value!
> > > > All-nets broadcasts will be addressed to 255.255.255.255
> > > > 0x86d80dc4: -GetGeneralIFConfig(ConfigInfo 0x832E5D4 Handle 0x86D30
> Ret:
> > > > TRUE)
> > > > 0x86d80dc4: +GetIFAddrList(NumAddr* 0x832E570 Handle 0x86D30)
> > > > 0x86d80dc4: *IPAddNTE: calling ARPDynRegister
> > > > 0x86d80dc4: PCX500:: OID_GEN_MEDIA_CONNECT_STATUS return
> [Disconnected]
> > > > 0x86d80dc4: PCX500:: OID_GEN_MEDIA_CONNECT_STATUS return
> [Disconnected]
> > > > 0x86d80dc4: IPAddInterface: PhysicalMedium ==
> > > NdisPhysicalMediumWirelessLan
> > > > 0x86d80dc4: IPAddInterface: Wireless LAN default to no
> > > > ConnectDampingInterval.
> > > > 0x86d80dc4: IPAddInterface: Wireless LAN default to no
> > > > DisconnectDampingInterval.
> > > > 0x86d80dc4: *CloseIFConfig(Handle 0x86D30)
> > > > 0x86d80dc4: +OpenIFConfig(Comm\CISCO1\Parms\TCPIP Handle 0x832E490)
> > > > 0x86d80dc4: Opened registry info for Comm\CISCO1\Parms\TCPIP
> > > > 0x86d80dc4: -OpenIFConfig(Comm\CISCO1\Parms\TCPIP *Handle 0x832E490,
> > BOOL
> > > > Ret: 1)
> > > > 0x86d80dc4: *CloseIFConfig(Handle 0x86D30)
> > > > 0x86d80dc4: DHCP:: $$$ NewDhcpInfo: 0x57220
> > > > 0x86d80dc4: -RequestWLan: Context 3
> > > > 0x86d80dc4: -IPAddInterface [SUCCESS]
> > > > 0x86d80dc4: PPP: -AddAdapter:NdisOpenAdapter(CISCO1) failed with
> > > 0xC0010019
> > > > 0x86d80dc4: PNP interface class
{f8a6ba98-087a-43ac-a9d8-b7f13c5bae31}
> > > > (NDS1:) ATTACH
> > > > 0x86f68b60: TAPI:AddTapiDevice: GetDeviceKeys(CISCO1) returned 1200
> > > > 0x86f68b60: TAPI:OldAddTapiDevice RegQueryValueEx(Tsp) returned 2
> > > > 0x86fef840: NOTIFICATION::XCeEventHasOccurred
> > > > 0x86fef840: NOTIFICATION::HandleSystemEvent 7 /ADD CISCO1
> > > > 0x86fef840: NOTIFICATION::HandleSystemEvent::Don't want
> > > > \\.\Notifications\NamedEvents\DSTTimeChange
> > > > 0x86fef840: NOTIFICATION::HandleSystemEvent::Don't want
> > > > \\.\Notifications\NamedEvents\DSTTzChange
> > > > 0x86fef840: NOTIFICATION::HandleSystemEvent::Don't want repllog.exe
> > > > 0x86fef840: NOTIFICATION::XCeEventHasOccurred
> > > > 0x86fef840: NOTIFICATION::HandleSystemEvent 7 /ADD NDS1:
> > > > 0x86fef840: NOTIFICATION::HandleSystemEvent::Don't want
> > > > \\.\Notifications\NamedEvents\DSTTimeChange
> > > > 0x86fef840: NOTIFICATION::HandleSystemEvent::Don't want
> > > > \\.\Notifications\NamedEvents\DSTTzChange
> > > > 0x86fef840: NOTIFICATION::HandleSystemEvent::Don't want repllog.exe
> > > > 0x86f43e18: ZCF:: InfContext [0x57470] created..
> > > > 0x86f43e18: PCX500:: OID_GEN_MEDIA_CONNECT_STATUS return
> [Disconnected]
> > > > 0x86f43e18: ZCF:: ## Assert!! File
> > > >
> > >
> >
>
[D:\mckendric\private\winceos\COMM\layer2svc\zeroconfig\Server\.\deviceio.c]
> > > > -- Line No [1228] ##
> > > > 0x86f43e18: ZCF:: ## Assert!! File
> > > >
> > >
> >
>
[D:\mckendric\private\winceos\COMM\layer2svc\zeroconfig\Server\.\deviceio.c]
> > > > -- Line No [1260] ##
> > > > 0x86f43e18: ZCF:: ## Assert!! File
> > > >
> > >
> >
>
[D:\mckendric\private\winceos\COMM\layer2svc\zeroconfig\Server\.\deviceio.c]
> > > > -- Line No [1374] ##
> > > > 0x86f43e18: ZCF:: Failed set OID_802_11_WEP_STATUS.
> > > > 0x86f43e18: ZCF:: ## Assert!! File
> > > >
> > >
> >
>
[D:\mckendric\private\winceos\COMM\layer2svc\zeroconfig\Server\.\deviceio.c]
> > > > -- Line No [1210] ##
> > > > 0x86e1cca0: NDISPWR:: BIND notification for adapter [Cisco1]
> > > > 0x86e1c800: PCX500:: OID_GEN_MEDIA_CONNECT_STATUS return
> [Disconnected]
> > > > 0x86f41df8: NotifyChange: Setting Event C6E21A72
> > > > 0x86ed2000: !WZCUI: 802.11 OIDs not supported by driver
> > > > 0x86ed2000: NETUIQC: Warning - failed to get wireless info
> > > > 0x86d80dc4: NETUIQC: Could not find the systray icon associated with
> the
> > > > given device name
> > > > 0x86d80dc4: NETUIQC: Error getting systray icon for given device
name
> > > > 0x86f43e18: IPTimer: setting IPTimer of NTE F98D0 to 0
> > > > 0x86e1edf8: PCX500:: OID_GEN_MEDIA_CONNECT_STATUS return
> [Disconnected]
> > > > 0x86e1edf8: ZCF:: ## Assert!! File
> > > >
> > >
> >
>
[D:\mckendric\private\winceos\COMM\layer2svc\zeroconfig\Server\.\deviceio.c]
> > > > -- Line No [1228] ##
> > > >
> > > > After this last Assert from ZCF, the device "hangs" (not really, but
> > mouse
> > > > is not updated anymore) until the card is removed. No popup, no
> nothing.
> > > >
> > > > Any ideas anybody?
> > > >
> > > >
> > > > Thanks in advance,
> > > >
> > > > Michel Verhagen, eMVP
> > > > Windows CE Consultant
> > > > PTS Software
> > > > The Netherlands
> > > > [if you want to reply to me directly, remove .nospam from my email
> > > address]
> > > >
> > > >
> > >
> > >
> >
> >
>
>
- Next message: Derek Ou: "Re: an easy question"
- Previous message: Bruce Eitman \(eMVP\): "Re: SOURCELIBS and TARGETLIBS"
- In reply to: Michel Verhagen [eMVP]: "Re: Cisco Aironet 350 & CE.NET 4.2"
- Next in thread: Tweeeek: "Re: Cisco Aironet 350 & CE.NET 4.2"
- Reply: Tweeeek: "Re: Cisco Aironet 350 & CE.NET 4.2"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
