3Com 3C589x Driver for Handheld PC 2.0

Offset 97

I know that you patched 97, but I don't think that we know the reason of the unstable drivers. I think this would be good to say in the CESD...

Marco

At this moment in time, I am not ruling out the error being in the Network client. However I have not had any negative feedback on that before either.

I'm basing the fact that it's unstable on non-us devices on what 3Com told me when I started the project, rather than from personal experience.
Have you experienced similar with any other hardware on the device?

The only other hardware for PCMCIA I have is a NoName modem card;it works fine, but is rather expensive:-(
Oh, my CF==>PCMCIA adaptor works fine also, even with a 2adaptor chain:
SD/MMC==>CF==>PCMCIA


Marco

I hate to chime in where I'm not wanted as I know C:Amie is far superior in knowledge but I think that C:Amie is correct, based upon my own experience as well - the network client is at fault.

Your modem working I believe confirms this - the modem binds directly with the PPP stack, not through NDIS as a network card does.

I might say that repairing the TCP stack would probably work but your problem is that you are using a non-US version of CE.

And I bet you that might be the problem - you are probably installing a US version of SP1. The TCP & NDIS layers are breaking.

Do you have the original CDROM that came with your unit? Please try this: do not install the SP1. Install only the network components then the 3com driver. You can (a) try using the NSP network stack with the driver. If that fails then (b) use the network stack included in your CDROM with the driver.

The SP1 patches but is not absolutely required for network connectivity (I believe) - only the NSP / CDROM-supplied NDIS subsystems are.

Snake is correct, the SP1 installation is a firm recommendation, it isn't an actual requirement.

I will try it; I think you GOT IT!!

More infos soon...

Marco

Thank you C:Amie

I am going to seriously jump the gun here and hope that my idea works, because I just had thoughts of why this is happening and want to put it down before I forget.

I bet you the SP1 breaks the NDIS because of 1 clause in your extremely informative SP1 FAQ in

http://www.hpcfactor.com/support/patching/ce20/

And here it is:

CHAP authentication now supports up to 256-character responses. This will permit your Handheld PC to connect to more online service providers.
Continuous network use eventually degrades performance over time. SP1 addresses current known issues which result from long-term use with network connections.

I realized that the 620LX came out in 1998 (looked it up). The U.S. Government was restricting key encryptions embedded for export to only 40 bit. When the SP1 upgrades the TCP stack to handle 256 bit I figure the balance of the OS in your German-model 620LX was only designed - locked in - to 40 bits at the time of design.

And the NDIS system breaks.

*CRY* nothing helps. made a backup-hard reset.
then installed *official* 589drivers and soft reset.
kicked card in. dongle lights a second, stops lightening for a 1/4 second, then the process starts by beginning.

okay. installed NSP, nothing changes after soft reset. giving a manual IP and gateway in network.cpl- same symptoms.

taken card and thrown it into a laptop-works.

you must first install NSP and only then the 589 drivers and only then plug the card in!

At least the lights are a good sign.

*big cry* even this doesnt help...

/me is going to eat his HPC if this proceeds...

Marco

The link to the HPC driver is dead - is there a new link to get it?

Cheers

There was a stray character in the link from the forum upgrade process, I've fixed the links now.

Cheers!