Unrecognized Card - Network card in scoket 2

BONEDR · 12-18-07, 11:38 AM

I have developed a problem with my AXIM x50v. When I try to turn on WiFi, I get the message: Unrecognized Card - Network Card in Socket 2. Of course, there is no network card since it is built in to the motherboard. I called Dell and they had me download and install update - this did not help. Dell has given up. I read somewhere that this could be do to a conflict with software - I did a hard reset and tried to turn WiFi on - I still got the same error message. Does anyone know a solution?:

Box · 12-18-07, 11:56 AM

Just a thought and it may be completely wrong, I don't have an x50 and the settings may be different, but you could check,

Go to wireless settings, with wifi turned off (stupid thing to say since you can't turn it on)
Open Network Cards and check that it's not trying to use the wrong adapter, I think it should say wireless adapter at the top of the list.
Might help, might not.

ikehiker · 12-18-07, 01:29 PM

Some people have found this seems to be an issue with certain home routers and the ROM version on the Axim. The solution that worked most often was to upgrade the firmware on the router.

Strongjd · 12-19-07, 02:14 AM

I've had this problem from time to time. However I soft reset is normally sufficient to fix it.

When did this start occurring? Was it following a change you made to your Dell, such as a software install?

How much memory do you have free? It maybe a case their is insufficient memory to allow the drivers to load and run.

BONEDR · 12-20-07, 10:28 PM

Well the unit is almost three years old and my memory seems to be getting low , free storage 2.35 mb and free progra 6.26 mb. May it is time I did a hard reset and reinstall the program trying to as little as possible in the mainmemory. And again maybe it is time to get a new PDA - the HP that is to be release next year really looks interesing - a larger screen and more memory.

12-20-07, 11:01 PM

Yeah, same thing happened to my X50v on PPC 2003 A05. Not sure what triggered it. After a hard reset, problem went away. Also, since upgrading to WM5, it's never reoccurred.