3com lan adapter working but connection manager can't see it??

Hi

I have a 3com 3CRDAG675 11a/b/g Wireless PCI adapter and Windows 98SE.

The card and drivers are installed - System, Device Manager shows the card
and says "This device is working properly". The light on the card flashes on
and off in the correct sequence for "I'm on and working (but not sending
data)".

If I do "ipconfig", it has a system assigned IP - so Windows is seeing it.

However, the 3com Lan Manager software you use to set up the connections for
the wireless card says "Device not detected" - as do all the other utilities
(I suspect a common mode failure - presume they are all going through a
common point). I downloaded their "Connection Assistant" diagnostics utility
and it told me everything was tickety boo >:-(

This is a problem because this Lan Manager software seems to be core to
setting up working connections with the card.

I'm wondering has anyone else seen this before and have any suggestions?
I've been up and down the 3com support site and it's told me nothing.

Unfortunately I can't register the product for direct email support cos its
a loaner from a mate whilst I wait for my (different brand) card to make it
out of the industrial dispute affecting the DHL shipment I've been told it
is stuck in. Well worth the 30 bucks "next day delivery" shipping charge :-(

My access point is 802.11g with WPA enabled, and the card has been assigned
interrupt 10 - in case, these are relevant.

Thanks for any suggestions.

Doug




DR

FYI: It was down to the Lan Manager software.

I had all but given up so went to uninstall it. Unfortunately all the
uninstaller did was reinstall the software and uninstall the uninstaller.
Neat.

So I had to go through the registry to work out how I was going to get it
out of my system (searching for all occurrences of 3com) when I came across
a key describing the device to which an 802.1x agent was bound. It was the
name of a 3com device I don't even own, presumably some generic value
inserted during install, but pre post-install config.

It seems like the installer is crapping out (but not giving any indication
of why, though I assume this is why uninstall does a half-arsed re-install)
and not updating this registry key; either that or 3com QA hasn't bothered
to test this on win 98se :-(

I got the device name from control panel, system - put this exact string in
the registry key and suddenly everything started working.

Card seems pretty ok otherwise.

"DR" <(E-Mail Removed)> wrote in message
news:cra00c$e4o$(E-Mail Removed)...
> Hi
>
> I have a 3com 3CRDAG675 11a/b/g Wireless PCI adapter and Windows 98SE.
>
> The card and drivers are installed - System, Device Manager shows the card
> and says "This device is working properly". The light on the card flashes
> on and off in the correct sequence for "I'm on and working (but not
> sending data)".
>
> If I do "ipconfig", it has a system assigned IP - so Windows is seeing it.
>
> However, the 3com Lan Manager software you use to set up the connections
> for the wireless card says "Device not detected" - as do all the other
> utilities (I suspect a common mode failure - presume they are all going
> through a common point). I downloaded their "Connection Assistant"
> diagnostics utility and it told me everything was tickety boo >:-(
>
> This is a problem because this Lan Manager software seems to be core to
> setting up working connections with the card.
>
> I'm wondering has anyone else seen this before and have any suggestions?
> I've been up and down the 3com support site and it's told me nothing.
>
> Unfortunately I can't register the product for direct email support cos
> its a loaner from a mate whilst I wait for my (different brand) card to
> make it out of the industrial dispute affecting the DHL shipment I've been
> told it is stuck in. Well worth the 30 bucks "next day delivery" shipping
> charge :-(
>
> My access point is 802.11g with WPA enabled, and the card has been
> assigned interrupt 10 - in case, these are relevant.
>
> Thanks for any suggestions.
>
> Doug
>