back to list| Mailing List os2-wireless_users@2rosenthals.com Archived Message #4373 |
back to list |
|
|---|
FWIW:Do you mean DHCP with the Wi-Fi card or with your Intel Pro? If Wi-Fi, then this (almost) makes sense. The card being recognized by card services doesn;t necessarily mean that it has been initialized & bound to any protocols (can't be bound until it's initialized; merely having resources supplied to it doesn't get it initialized, either, as it needs to have recognizable - recognizable by the NIC driver - resources assigned to it, and not just whatever's free). If the protocol isn't bound to it, you can't do DHCP, as you can't broadcast a DHCP discover packet to find a DHCP server, let alone do anything with an address from one.
I find that there a conflict with the PCCard v4.2 and the WiFi Stat utility and the card driver. I removed all of the Dani drivers and went with a full IBM only kit. When I do this with a full set of the PCCard 4.2 the PCCard detects that the card is in the PCMCIA slot, but the WiFi doesn't find the card. DHCP doesn't work either.
If I revert back to the earlier version of PCCARD with the exception of one of the PCCard drivers, the card functions and DHCP works along with the WiFi Stat utility.I believe Oliver mentioned that the newer package can actually backlevel some stuff, and that all that's really been updated (until perhaps this latest release - 7 is it?) is IBMSS14.SYS.
To work with this I removed the Intel Pro PCI NIC from MPTS. I only have the feedback loop and the Netgear card configured. And now, instead of a mere 2mb, I get 11.I'm guessing that when you say "feedback loop" you mean "loopback," which is a bit different... ;-) I don't get the speed difference at all. I don't see what would have changed, unless there was some resource conflict which was bogging the card down before.
|
Subscribe: Feed,
Digest,
Index. Unsubscribe Mail to ListMaster |