CF ethernet cards (Socket LP-E, Xircom CF10) not detected in WM5

40th Floor · 11-02-05, 01:56 AM

Socket LP-E (low power ethernet) NE2000 card: Unrecognized Card - Enter the name of the device driver for this card. For information, see the card manufacturer's documentation. [Unknown card in Socket 1]

Xircom CompactCard Ethernet 10 NE2000 card: Unrecognized Card - Enter the name of the device driver for this card. For information, see the card manufacturer's documentation. [Unknown card in Socket 1]

These are standard NE2000-compatible CF cards. They have worked with more than a dozen past CE devices right out of the box. The NE2000 driver is a built-in driver, and has been since CE 2, but apparently is broken in this Dell WM5 upgrade. Bummer. The NE2000 driver is listed in the "Network Cards" list, but it's not recognizing either card.

(This is not activesync related.)

Previously titled: Hardware That Should Work But Doesn't

maarendal · 11-02-05, 02:45 AM

Might be hardware related? See my reply:
http://www.aximsite.com/boards/showthread.php?t=101978

40th Floor · 11-02-05, 03:41 AM

The CF socket is fine. The ethernet cards are fine. Dell's new WM5 detection of NE2000 cards is not. Narrows it down, wouldn't you say.

maarendal · 11-02-05, 03:46 AM

You would think WM5 would have recognized the cards drivers. Would dropping down to WM03 be a fix?

40th Floor · 11-02-05, 04:46 AM

Well, obviously these were working in 2003.

Topic is: Hardware the should work but doesn't (after doing the WM5 upgrade, or even on a x51). Your reply to the guy with an X5 card problem doesn't quite apply.

maarendal · 11-03-05, 02:23 AM

The Xircom CompactCard Ethernet 10 (CFE-10) has been discontinued on 21 October 2005, support was discontinued on 31 December 2005. See:

http://support.intel.com/support/net.../cs-020974.htm

A known bug involved Windows Application Manager failing to find the correct processor cab file (Arm/Mips/Sh3) requiring manual deletion from the program folder. See:

ftp://aiedownload.intel.com/df-suppo...130_README.TXT

Your card may be delivering all embedded cab files resulting a buggy choice. As you have already stated WM05 does not support your card and a separate driver (apart from NE2000) is necessary. Download driver here:

http://downloadfinder.intel.com/scri...OSFullName=All Operating Systems&lang=eng

Follow the read me instructions above and delete the Mips and Sh3 cab files once installed.

40th Floor · 11-03-05, 06:56 AM

Well, I can see you're confused so let me help you out (the readme you have there dates to 2001). These are standard NE2000 cards, and I'm not using Xircom's driver (let alone Socket's driver). They don't need an external driver; the driver is installed with the CE OS. These cards have worked out of the box since CE 2. To spell that out more: CE/Palm-sized PC, Pocket PC (2000), HPC 3.0, HPC 2000, Pocket PC 2002, Pocket PC 2003, Pocket PC 2003SE. These cards have never pop an unrecognized card in socket message. The NE2000 driver is in WM5, but the Dell WM5 upgrade does not detect NE2000 ethernet cards. This is specific to the WM5 upgrade to the Dell X50v. It has nothing to do with SH3, Mips, or whatever else you have there. Xircom doesn't even exist as a company, and hasn't for serveral years. Intel bought them back when they were getting into networking. Do you have an ethernet CF card that doesn't work with WM5?

Topic is: Do you have any hardware that should work but doesn't?

40th Floor · 11-03-05, 07:05 AM

Socket LP-E (low power ethernet) NE2000 card: Unrecognized Card - Enter the name of the device driver for this card. For information, see the card manufacturer's documentation. [Unknown card in Socket 1]

Xircom CompactCard Ethernet 10 NE2000 card: Unrecognized Card - Enter the name of the device driver for this card. For information, see the card manufacturer's documentation. [Unknown card in Socket 1]

These are standard NE2000-compatible CF cards. They have worked with more than a dozen past CE devices right out of the box. The NE2000 driver is a built-in driver, and has been since CE 2, but apparently is broken in this Dell WM5 upgrade. Bummer. The NE2000 driver is listed in the "Network Cards" list, but it's not recognizing either card.

(This is not activesync related.)

Gigi · 11-03-05, 07:10 AM

Threads merged.

40th Floor · 11-03-05, 07:15 AM

Quick shot from the hip, but it's a NEW thread since this one has lost all meaning. The title does little good. Or maybe, a new title is possible. Nope, not possible this far in, not by me anyway. Gigi, how about changing the title then, to this:

CF ethernet cards (Socket LP-E, Xircom CF10) not detected in WM5

Gigi · 11-03-05, 07:53 AM

Quote:

Originally Posted by 40th Floor

Quick shot from the hip, but it's a NEW thread since this one has lost all meaning. The title does little good. Or maybe, a new title is possible. Nope, not possible this far in, not by me anyway. Gigi, how about changing the title then, to this:

CF ethernet cards (Socket LP-E, Xircom CF10) not detected in WM5

No problem... (I wouldn't say that this thread had lost its meaning though...)

maarendal · 11-03-05, 09:30 AM

Yes, I know exactly what your saying with regard to NE2000. My answer was a work-around from NE2000 and to registering a driver specific to that Xircom card; because, as your finding out, NE2000 compatible cards do not always get recognized. If you want NE2000 for fix/clone, its off to the registry.

In the PPC Registry keys you will find the entries;

[HKEY_LOCAL_MACHINE\Comm\NE2000]

And,

[HKEY_LOCAL_MACHINE\Comm\NE20001]

There will be no parameters for the first entry (2000), the current parameters will be found in the second entry (20001). So, Export the key;

[HKEY_LOCAL_MACHINE\Comm\NE20001]

and edit with PNOTEPAD by changing ALL occurrences of NE20001 to NE20002; and then import the key back into the registry. This generates now a third NE2000 registry entry.

Now, edit the "Display Names" so that one says, NE2000 Auto Assign and the other to say NE20002; then configure the later accordingly. Here, you already have the parameters for the card under another WM03 system. Use those to tediously configure the new NE20002 folder.

Next, you need to configure the Xircom card as the one wanted for selection. Go to:

[HKEY_LOCAL_MACHINE\Comm\NE2000\Linkage]

Under "Route" which entry is: NE20001; change this entry to NE20002.

With the above, all you really have done is adopted the parameters of the a WM03 folder and created them in a new WM05 folder without altering WM05's standard parameters for NE2000.