PaulSM

Copy 13.3MB file from my server to my X51v:
- With Trendnet TE-CF100 = 19 minutes
- With built-in WiFi (128-bit WEP and VPN) = 2 minutes

Can anyone get the Trendnet to work with the X51v at a reasonable speed? Can you post how fast your Trendnet compares to the built-in WiFi?

Has anyone tried the LP/Fast Ethernet from Socket Comm? How fast is it?

qwertyzone

I have the same problem after trying to have my x51v recognize TE-CF100 in WM5.0 using the hack someone posted in this forumn. Please let me know if you find anything.

Brewdude

Use File Explorer on the Axim and look in the My Device (the top level) folder. Is there a file there called "test" that grows with Ethernet activity? That'll make it really slow. You need a version of le100.dll that has that feature taken out.

Ticonderoga

Originally Posted by Brewdude

Use File Explorer on the Axim and look in the My Device (the top level) folder. Is there a file there called "test" that grows with Ethernet activity? That'll make it really slow. You need a version of le100.dll that has that feature taken out.

Where can we get a copy of that? The older version (v1.4) works very well on WM2003SE but does not work on WM5.

Brewdude

This is what they sent to me last year after I complained about that file being there in v1.5. I don't know what version number it is and if it's better than v1.4 or not, but it doesn't create that file and seems to work okay. It seems to make the Ethernet run a lot faster than the old v1.5 driver, although still seems a little slower than it was on WM2003.

Unzip this (le100.dll) and copy it to the windows folder on your pocket PC. If the old le100.dll isn't there, you need to run TrendNet's setup program first prior to copying this file over to make sure everything get registered and stuff. If it asks you for the name of the driver when you insert the card, type in "le100".

I previously did a search on this card and see that someone else has also uploaded an le100.zip, so I don't know which version that is either.

Ticonderoga

Wow it works! Finally my card is actually usable. Thanks Brewdude!

(p.s. I have no idea why they do not simply put this version on their webpage)

MCopley

I'm struggling to get my Trendnet card working with my X51. I've done a hard reset and reinstalled Activesync. One of the posts above mentions running the Trendnet setup program...I've run that, it connects to the Axim, copies the LE100.DLL (which I'm guessing I need to overwrite with the one that's been posted here, which I did) but when I insert the card I NEVER get prompted for a driver, nothing at all happens...the lights on the card flash when connected to the network, so it's getting a link, in the "network cards" menu I see the "NE2000 Compatible Ethernet Driver" but there are no options for specifying a driver...

What am I doing wrong??

MCopley

Okay, still troubleshooting, but finding some very strange stuff along the way. I managed to get the "CompactFlash Size 10/100 Fast Ethernet" to show up now under network cards. I still cannot get the TrendNet adapter to work, however I have noticed that when I plug it in (link lights come on, speed, duplex, etc) and under network cards the "CompactFlash Size 10/100 Fast Ethernet" always shows "Not Connected" however the "NE2000 Compatible Ethernet Driver" shows an IP address of "fe80::3ff:ff:fe03:1" for about a minute, then it changes to a 169.254.x.x address. Correct me if I'm wrong, but that first address looks like an IPV6 address, right? (I don't have an IPV6 DHCP server running) Has anyone seen this behavior before?

Also, I was able to get a spare X50 from our office and the TrendNet card works perfectly on it (of course, it's WM2003).

I refuse to give up on this, there's GOT to be a way to make this work on the X51!

tatatimmy

re: TrendNet TE-CF100 and Dell AXIM x51v

My experiance...

Dell Axim x51v rev. A02 - it worked fine...install the TrendNet Driver, push the card, it prompted, give it the name of the le100.dll and presto...No problems...I recently patched the rom to rev. A12...installed the TrendNet Driver, push the card, nothing...

Good luck...post a fix when you find one...Thanks!

aximpal

MCopely Wrote: "I managed to get the "CompactFlash Size 10/100 Fast Ethernet" to show up now under network cards."
Can you pls. share how you did that. Has anybody got it working on WM5.0 with ROM A12?
Thanks!!

danzig69

I also need how you did to show up now under network cards!!
I am currently able to use this card on a HP IPAQ 2410 with windows mobile 2003 (CE 4.21) "CompactFlash Size 10/100 Fast Ethernet" appear under network
On the new IPAQ 2490b with WM5 (CE5) it never prompt me. And I'm unable to make "CompactFlash Size 10/100 Fast Ethernet" appear under network tab!
I can see an icone changing next to the time on the screen when I insert the card on both device. On the 2410 it said internet when I click on the icone. On the 2940b it said network card.
I've contacted Trendnet and they told me :"Trendnet does not have drivers Windows 5.0 drivers for the TE-CF100." snif snif
I give up! I suggest you to buy this card http://www.socketcom.com/product/EA2917-722.asp#specs

krokodil

I think I know why the card may not work with A12.

When I installed the TE-CF100 driver on my x51v A12, and pushed in the card, it got recognized by WM5 as a NE20001 compatible. There was no obvious way for me to tell WM5 to use the installed le100.dll with the card, and pre-installed ne2000.dll didn't work with my card.

To make it work I had to edit the registry to change drivers used for NE2000/NE20001 compatible cards:

HKEY_LOCAL_MACHINE\Comm\NE2000\ImagePath change ne2000.dll to le100.dll
HKEY_LOCAL_MACHINE\Comm\NE20001\ImagePath change ne2000.dll to le100.dll

You can use any Pocket PC registry editor, for example this one: http://www.freewareppc.com/utilities...ryeditor.shtml

Hope this helps.

yengkl

It really works!! Deeply appreciate your great idea!!

Originally Posted by krokodil

I think I know why the card may not work with A12. When I installed the TE-CF100 driver on my x51v A12, and pushed in the card, it got recognized by WM5 as a NE20001 compatible. There was no obvious way for me to tell WM5 to use the installed le100.dll with the card, and pre-installed ne2000.dll didn't work with my card. To make it work I had to edit the registry to change drivers used for NE2000/NE20001 compatible cards: HKEY_LOCAL_MACHINE\Comm\NE2000\ImagePath change ne2000.dll to le100.dll HKEY_LOCAL_MACHINE\Comm\NE20001\ImagePath change ne2000.dll to le100.dll You can use any Pocket PC registry editor, for example this one: http://www.freewareppc.com/utilities...ryeditor.shtml Hope this helps.

volfied

Krokodil!. You are the man!, Yeah!.. works, works, wooooorks!!!.
Thanks a lot

Originally Posted by krokodil

I think I know why the card may not work with A12. When I installed the TE-CF100 driver on my x51v A12, and pushed in the card, it got recognized by WM5 as a NE20001 compatible. There was no obvious way for me to tell WM5 to use the installed le100.dll with the card, and pre-installed ne2000.dll didn't work with my card. To make it work I had to edit the registry to change drivers used for NE2000/NE20001 compatible cards: HKEY_LOCAL_MACHINE\Comm\NE2000\ImagePath change ne2000.dll to le100.dll HKEY_LOCAL_MACHINE\Comm\NE20001\ImagePath change ne2000.dll to le100.dll You can use any Pocket PC registry editor, for example this one: FreewarePPC.com - Freeware Pocket PC / Freeware Windows Mobile: Mobile Registry Editor v1.11 Hope this helps.

sibble-comp

Originally Posted by krokodil

I think I know why the card may not work with A12. To make it work I had to edit the registry to change drivers used for NE2000/NE20001 compatible cards: HKEY_LOCAL_MACHINE\Comm\NE2000\ImagePath change ne2000.dll to le100.dll HKEY_LOCAL_MACHINE\Comm\NE20001\ImagePath change ne2000.dll to le100.dll Hope this helps.

That works good, however, if you also have an ne2000 compatible nic like the socket LP-E, it stops working. Anyone what registry settings to add to allow both to work, ie have the cf ethernet card show up in the list and use the le100.dll while the ne2000 compatible ones use ne2000.dll?