Search the Community
Showing results for tags 'wifi'.
Found 2 results
Intel WLAN 2100, 2200BG, 2915ABG, 3495ABG, 3965ABG Latest generic drivers and comparison charts for Intel Chipset based wireless cards can be found HERE Intel® PROSet/Wireless Software v10.5.0.0 - for 2200BG, 2915ABG, 3945ABG, 3965ABG Driver v10.5.1.57 for 3945ABG Driver v184.108.40.206 for 2200BG/2915ABG Date: 2006-07-21 MultiLanguage and supporting all Windows OS (32bit and 64bit) Size: ~130 MB DOWNLOAD LINK Intel® PROSet/Wireless Software v220.127.116.11 - for 2100 Driver v18.104.22.168 for 2100 Date: 2006-07-28 MultiLanguage and supporting all Windows OS (32bit and 64bit) Size: ~16 MB DOWNLOAD LINK Intel Wireless ID Tool v3.0.3 - for detection of which chipset you have. This release supports the following adapters: Intel® PRO/Wireless 2100 Network Connection Intel® PRO/Wireless 2100A Network Connection Intel® PRO/Wireless 2200BG Network Connection Intel® PRO/Wireless 2915ABG Network Connection DOWNLOAD LINK (60k)
[This, including the title, has been c&p'd from my post over at the Intel forum] When attempting to install on my x64 Win7 laptop, the 22.214.171.124 ProSet software and driver bundle seems to be missing the inf for the 4956AGN chipset, although it's stated to be for this hardware. The result is, that the ProSet software installs and leaves whichever driver you had installed previously. This can cause varying incompatibilities between the two. The alternative standalone driver-only package simply doesn't install, and choosing the "let me choose from a list of drivers" option shows that the 4965AGN is not listed. I tried removing the 13.x driver that it kept from the previous package installation but, upon attempting the 14.x package install again, Windows simply reverted to the 12.x driver which it pulled from its own driver store. I'd like to add that I've now used the Intel Driver Update Utility, which diagnosed that my driver was 12.x and pointed me to the same package I'd already downloaded; which I did, and attempted to install, with exactly the same results - the software installs yet not the driver. There are no errors or indication of this except later, when the incompatibility between the 14.x software and 12.x driver (which remains; installed by Windows) prevents connection to profiles. ---------- Note: In the end I reverted to v13.5 but my profiles are messed up, and I have to type the network key every time I want to connect, and also none of the software components work, and they're not repairable via the installation package.