The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Can't get Intel PRO/Wireless 2100 3B to work on Windows 7 - t42

    Discussion in 'Lenovo' started by JakeL645, Aug 11, 2010.

  1. JakeL645

    JakeL645 Notebook Consultant

    Reputations:
    0
    Messages:
    133
    Likes Received:
    0
    Trophy Points:
    30
    I've just having trouble installing it. I got the installer working and it says it successfully installed but it still comes up as an unknown device. Everything on in BIOS and I've tried the System update thing from thinkpad. No luck. When I press the FN key to turn the wireless on it tells me there's no wireless card installed. I've also tried manually selecting the driver by updating the unkown device from device manager, again, no luck. Anyone got it to work on windows 7 or can help?
     
  2. PatchySan

    PatchySan Om Noms Kit Kat

    Reputations:
    3,971
    Messages:
    2,248
    Likes Received:
    221
    Trophy Points:
    81
    What drivers you tried using? It's not impossible as we got a Dell Inspiron 510m with Intel Wireless 2200BG card working fine on Windows 7 (Starter 32 bit).

    Have you tried manually loading the Vista drivers of Intel Wireless 2100 into Windows 7?
     
  3. JakeL645

    JakeL645 Notebook Consultant

    Reputations:
    0
    Messages:
    133
    Likes Received:
    0
    Trophy Points:
    30
    Yes I've tried using the vista drivers. I know it's possible but the methods I've read don't work for me *sigh* stupid drivers :\
     
  4. wordsworth

    wordsworth Notebook Guru

    Reputations:
    0
    Messages:
    61
    Likes Received:
    0
    Trophy Points:
    15
    Well, the 2100-3B and 2200BG are completely different animals in windows 7. It's very easy to get the 2200 working. The 2100 can be a pain. But I have a T42p right now running Windows 7 with a 2100-3B installed and it works. I do remember having to fight through some odd problems, like the device manager showing everything working right, but the Thinkpad software showing the device turned off. When I do an F5, the Thinkpad software still shows the device as turned off. But it works anyways.

    Unfortunately, I can't remember what I did to get it to work. I just remember trying a lot of different things and rebooting a lot.
     
  5. JakeL645

    JakeL645 Notebook Consultant

    Reputations:
    0
    Messages:
    133
    Likes Received:
    0
    Trophy Points:
    30
    Hmm well if this helps, windows 7 recognizes the what driver I should install and stuff when I go to install it via device manager and the windows drivers, when I install it it says "Windows encountered a problem installing the driver software for your device.

    Windows found the driver software for your device but encountered an error while attempting to install it. This operation returned because the timeout period expired."

    Hmm... this is a pain
     
  6. JakeL645

    JakeL645 Notebook Consultant

    Reputations:
    0
    Messages:
    133
    Likes Received:
    0
    Trophy Points:
    30
    SUCCESS! I removed the wireless card manually and put it back in, turned it on and it worked :)
     
  7. Renee

    Renee Notebook Virtuoso

    Reputations:
    610
    Messages:
    2,645
    Likes Received:
    0
    Trophy Points:
    55
    Probably you just re-seated it.
    Renee
     
  8. JakeL645

    JakeL645 Notebook Consultant

    Reputations:
    0
    Messages:
    133
    Likes Received:
    0
    Trophy Points:
    30
    Actually, it may also have something to do with the power settings, because I had it running on battery and the power setting was set to "maximum power savings" and the card just didn't work, but still recognised it, until I set it to max performance. Maybe that might of had something to do with it too.

    This was after I got the driver working.