I'm there with you. The problem is Intel's site shows 15.3.1 as the latest version and yet 15.4.0.11 dated 6 December 12 is clearly the latest version for Dells (mine is a Latitude E6520). ProSet whines that it's not compatible with 15.4.0.11 and tells me to "upgrade" to an older version then lists those versions. The other problem here is Intel rarely answers problems here and when they do they're not helpful (see the thread about drops on teh 6300 series wireless cards.
Here's the link for the "latest" drivers:http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Wireless+Networking&ProductLine=Intel%C2%AE+Centrino%C2%AE+Wi-Fi+Products&ProductProduct=Intel%C2%AE+Centrino%C2%AE+Ultimate-N+6300
Notice they're dated 3 weeks before our version.
As I indicated I already have ver 15.4.0.11 installed but I do not see any indocation that I can use wifi direct. It does not show up in the control panel or under the Intel Programs. Do you have any suggestions on how to activate?
Intel is very frustrating since they have not bothered answering this posting and I also filed a request for support by email with Intel and of course they never bothered respoding to the technical support issue.
I finally figured out that I had to install a WIFI Dashboard driver so I did that (version 15.3.1_s64). When I did that and ran the dashboard I get a message which says that the PC is capable of using wifi technology but a program is not installed. When I click on the link in the message it sends me to the Intel support site but I have no idea what needs to be installed. So I downloaded and installed the wifi driver which matches that version of dashboard and then reran wifi dashboard but still get same message. The wifi direct shows as "off" and I cannot seem to turn it on. Also the control panel still does not show wifi direct.
Anyone have suggestions for me?
Look here : http://communities.intel.com/message/178329
I have the same issue with Intel Centrino N-1030 and reinstalling Intel My WiFi Dashboard fixed the problem.
Please Intel fix that bug.
