Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

New support for wifi

- - - - -

  • Please log in to reply
29 replies to this topic

#1
gosh

gosh

    gosh 2.0

  • Patrons
  • 2,347 posts
  • OS:none specified
  • Country: Country Flag
ince the dawn of time, Windows PE (WinPE) has not had any support for the 802.1x authentication protocol. This meant that any network deployment of Windows via a network secured with 802.1x was a non-starter, causing headaches for a few on my customers; I actually had one customer that ran new network cables to a majority of the desks in order to be able to deploy Windows XP over the network.
However, thanks in part to a colleague of mine who worked on this, Microsoft has released hotfixes that now add 802.1x support to both WinPE 2.1 and WinPE 3.0. You can get the hotfixes and further information at the below links:

WinPE 2.1: http://support.microsoft.com/kb/975483
WinPE 3.0: http://support.microsoft.com/kb/972831


How to remove advertisement from MSFN

#2
Tripredacus

Tripredacus

    K-Mart-ian Legend

  • Super Moderator
  • 9,766 posts
  • OS:Server 2012
  • Country: Country Flag

Donator

Thanks. I updated the WiFi link in the FAQ thread to point to this topic.
MSFN RULES | GimageX HTA for PE 3-5 | lol probloms
msfn2_zpsc37c7153.jpg

#3
TheReasonIFail

TheReasonIFail

    Member

  • Member
  • PipPip
  • 171 posts
So how does one install this? I tried to install it on my laptop with Win7 and says that the update is not applicable.

#4
cluberti

cluberti

    Gustatus similis pullus

  • Supervisor
  • 11,252 posts
  • OS:Windows 8.1 x64
  • Country: Country Flag
You use dism to add the .cab file that exists when you extract the package to a WinPE 2.1 or 3.0 .wim file to "install" the hotfix. It doesn't actually install on a full OS.
MCTS Windows Internals, MCITP Server 2008 EA, MCTS MDT/BDD, MCSE/MCSA Server 2003, Server 2012, Windows 8
--------------------
Please read the rules before posting!
Please consider donating to MSFN to keep it up and running!

#5
TheReasonIFail

TheReasonIFail

    Member

  • Member
  • PipPip
  • 171 posts
Hah!! Doh!! I saw the update package and just double-clicked!!

#6
Eagle710

Eagle710

    Member

  • Member
  • PipPip
  • 159 posts
That is pretty funny considering I got it working just 3 weeks before they released this Hotfix.
Flying High

#7
Eagle710

Eagle710

    Member

  • Member
  • PipPip
  • 159 posts
Now that Wireless works how did we connect to wireless networks. What Interface is recommended?
Flying High

#8
cluberti

cluberti

    Gustatus similis pullus

  • Supervisor
  • 11,252 posts
  • OS:Windows 8.1 x64
  • Country: Country Flag
Netsh is the only interface WinPE would have, and I don't know how much of netsh wlan is even in WinPE after this hotfix. Someone would have to test, or write a GUI utility if they wanted a GUI.
MCTS Windows Internals, MCITP Server 2008 EA, MCTS MDT/BDD, MCSE/MCSA Server 2003, Server 2012, Windows 8
--------------------
Please read the rules before posting!
Please consider donating to MSFN to keep it up and running!

#9
wimb

wimb

    Senior Member

  • Developer
  • 679 posts
I tried to use dism to "install" the HotFix KB972831 in Windows PE 3.0 boot.wim file mounted with imagex in folder mount,
but it fails giving me

Error: 0x800f081e

The specified package is not applicable to this image.


Used in XP OS at Deployment Tools Command Prompt:

Dism /image:F:\winpe3_x86\mount /Add-Package /PackagePath:F:\winpe3_x86\fix283119\Windows6.1-KB972831-x86.cab

Can someone help me to solve the problem ?

#10
andyasselin

andyasselin

    Newbie

  • Member
  • 21 posts

ince the dawn of time, Windows PE (WinPE) has not had any support for the 802.1x authentication protocol. This meant that any network deployment of Windows via a network secured with 802.1x was a non-starter, causing headaches for a few on my customers; I actually had one customer that ran new network cables to a majority of the desks in order to be able to deploy Windows XP over the network.
However, thanks in part to a colleague of mine who worked on this, Microsoft has released hotfixes that now add 802.1x support to both WinPE 2.1 and WinPE 3.0. You can get the hotfixes and further information at the below links:

WinPE 2.1: http://support.microsoft.com/kb/975483
WinPE 3.0: http://support.microsoft.com/kb/972831



You do know they Talk about wired port based auth and not wireless

http://en.wikipedia....iki/IEEE_802.1X

#11
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,266 posts
  • OS:none specified
  • Country: Country Flag

You do know they Talk about wired port based auth and not wireless


Then, being the title of this thread "New support for wifi", and seeing what Eagle710 posted, does it means that BOTH gosh and Eagle710 are lieing? :ph34r: :w00t:

@Eagle710
Care to post some details on the topic and your success? :unsure:

jaclaz

#12
Eagle710

Eagle710

    Member

  • Member
  • PipPip
  • 159 posts

You do know they Talk about wired port based auth and not wireless


Then, being the title of this thread "New support for wifi", and seeing what Eagle710 posted, does it means that BOTH gosh and Eagle710 are lieing? :ph34r: :w00t:

@Eagle710
Care to post some details on the topic and your success? :unsure:

jaclaz

So this is not wireless functionality? Are you sure it seems like they are talking about wireless.

I will but let me put my information together.
Flying High

#13
gosh

gosh

    gosh 2.0

  • Patrons
  • 2,347 posts
  • OS:none specified
  • Country: Country Flag

You do know they Talk about wired port based auth and not wireless


Then, being the title of this thread "New support for wifi", and seeing what Eagle710 posted, does it means that BOTH gosh and Eagle710 are lieing? :ph34r: :w00t:

@Eagle710
Care to post some details on the topic and your success? :unsure:

jaclaz


jaclaz i just copied my post from a Microsoft blog. All content was directly from microsoft. So its not a question of not telling the truth, if Microsoft says it works it works.

#14
gosh

gosh

    gosh 2.0

  • Patrons
  • 2,347 posts
  • OS:none specified
  • Country: Country Flag
The blog is here:

http://blogs.technet...windows-pe.aspx

#15
Eagle710

Eagle710

    Member

  • Member
  • PipPip
  • 159 posts

The blog is here:

http://blogs.technet...windows-pe.aspx

It appears that it is used for most wireless 802.11 access points and is based on the Extensible Authentication Protocol (EAP). Therefore wouldn't this be adding wireless functionality?
Flying High

#16
wimb

wimb

    Senior Member

  • Developer
  • 679 posts
I presume that the Version of the used AIK for Windows 7 is the problem.

dism accepts and works OK for the in the AIK provided cab files with version 6.1.7000
but it rejects the WiFi support cab having version 6.1.7600

Have now AIK with dism and cab files version 6.1.7600
Later more ....

Edited by wimb, 29 January 2010 - 02:22 AM.


#17
wimb

wimb

    Senior Member

  • Developer
  • 679 posts
The new AIK of Windows 7 with dism version 6.1.7600 contains even
the WiFi support file Windows AIK\Tools\PETools\x86\WinPE_OCs\Windows6.1-KB972831-x86.cab

I was able to add the package after adding with dism some extra cabs of WinPE_FPs folder.

After booting with pe3w.iso from GRUB4DOS menu I have a lot of portable programs running from PStart Menu,
but there is not yet WLAN available. The driver was added manually, but WLANAPI is not found on the system.

So we are making progress, but there is still some work to be done ....

More Info http://www.911cd.net...mp;#entry161011

=
Posted Image
=

Edited by wimb, 29 January 2010 - 12:23 PM.


#18
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,266 posts
  • OS:none specified
  • Country: Country Flag
@gosh
By omitting initially that it was a verbatim copy and paste from someone else's blog, you did give the impression :realmad: :
  • that the works was done partly by a colleague of yours
  • that one of your customers had a wired problem now solved by wireless
  • that you were substantially familiar with the thingies and somehow "endorsed" them or their use

@Eagle710
You plainly stated that you were able to enable wireless connections in a PE 2.1 or 3.0, or at least this is the only way your post can be read.

Since I didn't believe you much :ph34r:, in order to try and understand what was it all about, I posted here:
http://www.boot-land...showtopic=10250
reporting the news.

The phishing ;) worked, and wimb got hooked. :thumbup

Now, it seems like turning out that:
gosh believes blindly in whatever MS writes (which does surprise me :w00t:) and never actually tested the thingies
Eagle710 has never had this working as well :unsure:

IMHO the misunderstandings could have been easily avoided if what is coming out now was stated initially, by taking a bit more care in the wording and quoting the sources/adding details.

Thanks to wimb for having taken the time to start the actual testing.

:hello:

jaclaz

Edited by jaclaz, 29 January 2010 - 05:23 AM.


#19
Tripredacus

Tripredacus

    K-Mart-ian Legend

  • Super Moderator
  • 9,766 posts
  • OS:Server 2012
  • Country: Country Flag

Donator

I agree, reposts from other blogs or forums should have their source URL included with the post. This not only will alleviate the problem Jaclaz had in thinking it was something you (gosh) was working on, but it also will stop the original authors from thinking someone is stealing their work. This has come up on other forums in the past, and it is best to cite your sources, although you don't have to go TOW crazy. :ph34r:
MSFN RULES | GimageX HTA for PE 3-5 | lol probloms
msfn2_zpsc37c7153.jpg

#20
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,266 posts
  • OS:none specified
  • Country: Country Flag
@Tripredacus
I am not getting crazy at all :), and definitely not TOW crazy.....

....speaking of which ;):
http://www.metacafe....towing_trailer/
..and also speaking of "blind faith" :whistle:.

The point I was trying to make is that one thing is posting some "news" read somewhere and another thing is to make them appear as your own, besides the point you made about possible "resentment" of the original authors, is that when gosh, I mean gosh, not a JohnDoe42 at his first post on the board, posts something, it automatically (at least in my mind) get a patent of "dependability/reliability", and it is a synonym of "tested".

In other words, and with all due respect for gosh, I was pointing out how he has to be, as reknown Windows tweaker/expert and MSFN Patron, very accurate, as his words do have a weight.

But it seems to me that everything is now clear and cool B) , let's see if we can actually have WiFi working on PE 2.x/3.x.....

:hello:

jaclaz

#21
gosh

gosh

    gosh 2.0

  • Patrons
  • 2,347 posts
  • OS:none specified
  • Country: Country Flag

@gosh
By omitting initially that it was a verbatim copy and paste from someone else's blog, you did give the impression :realmad: :

  • that the works was done partly by a colleague of yours
  • that one of your customers had a wired problem now solved by wireless
  • that you were substantially familiar with the thingies and somehow "endorsed" them or their use

@Eagle710
You plainly stated that you were able to enable wireless connections in a PE 2.1 or 3.0, or at least this is the only way your post can be read.

Since I didn't believe you much :ph34r:, in order to try and understand what was it all about, I posted here:
http://www.boot-land...showtopic=10250
reporting the news.

The phishing ;) worked, and wimb got hooked. :thumbup

Now, it seems like turning out that:
gosh believes blindly in whatever MS writes (which does surprise me :w00t:) and never actually tested the thingies
Eagle710 has never had this working as well :unsure:

IMHO the misunderstandings could have been easily avoided if what is coming out now was stated initially, by taking a bit more care in the wording and quoting the sources/adding details.

Thanks to wimb for having taken the time to start the actual testing.

:hello:

jaclaz


Look, i am very busy. When i find something useful i post it on this site. In retrospect its easy to i should have done this, i should have done that. The microsoft blog said this worked fine without any issues. I had no reason to doubt 2 microsoft employees who said this worked fine. Dont shoot the messenger. If you have a complaint direct it at the original source - the microsoft blog. It would be nice to get a thanks every once in awhile.

#22
Eagle710

Eagle710

    Member

  • Member
  • PipPip
  • 159 posts
I will try and find time to post a zip file of all the regedits and system file I required to get Wireless to work in WinPE 2.1 but have been very busy as of late. Please proceed with testing and I will update you all when I get the chance.

I may be able to take a screenshot of connection to a wireless accesspoint if you would like a quick Proof of Concept. Let me know!
Flying High

#23
wimb

wimb

    Senior Member

  • Developer
  • 679 posts
Unprotected Wireless Internet in Windows PE 3.0 was realized:
It is necessary to let dism Add WLAN drivers in specific way from provided folder WIN7_drivers.
As before, dism was also used to add winpe-wmi.cab and the HotFix WinPE_OCs\Windows6.1-KB972831-x86.cab

The WLANAPI missing message in PENetwork.exe was overcome by Adding WIN7_system32\wlanapi.dll of Windows 7 to system32
Internet access and PENetwork don't work yet for WPA encryption.
There is now a message for problem to be solved:

file netwzc.inf is missing, which is needed for support of Wireless Zero Configuration

Code used to make Windows PE 3.0 - pe3w.iso
copype.cmd x86 F:\winpe3_x86

copy /y F:\winpe3_x86\winpe.wim F:\winpe3_x86\ISO\sources\boot.wim

imagex.exe /mountrw F:\winpe3_x86\ISO\sources\boot.wim 1 F:\winpe3_x86\mount

Dism /image:F:\winpe3_x86\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_FPs\winpe-wmi.cab"
Dism /image:F:\winpe3_x86\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_FPs\en-us\winpe-wmi_en-us.cab"
Dism /image:F:\winpe3_x86\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\Windows6.1-KB972831-x86.cab"
:: Add WLAN drivers
Dism /image:F:\winpe3_x86\mount /Add-Driver /Driver:F:\winpe3_x86\WIN7_drivers /recurse
:: Add wlanapi.dll
xcopy.exe F:\winpe3_x86\WIN7_system32\*.* F:\winpe3_x86\mount\Windows\System32\ /i /k /e /r /y /h
:: Add Browse for Folder support by making empty folder Windows\System32\config\systemprofile\Desktop
md F:\winpe3_x86\mount\Windows\System32\config\systemprofile\Desktop

imagex.exe /unmount /commit F:\winpe3_x86\mount

oscdimg.exe -n -m -o -bF:\winpe3_x86\etfsboot.com F:\winpe3_x86\ISO F:\winpe3_x86\pe3w.iso

More Info: http://www.911cd.net...mp;#entry161011


Windows PE 3.0 with Wireless Internet - Opera Portable and PENetwork.exe
=
Posted Image

=

Edited by wimb, 01 February 2010 - 01:55 AM.


#24
allanf

allanf

    Junior

  • Member
  • Pip
  • 66 posts
Probably a long-shot... but might be interesting to do a Dependency Walker profile of some other wireless networking manager - like one specific to the adaptor.

For example, IntelĀ® PROSet/Wireless WiFi Connection Utility for Windows 7 32-Bit*. There's a zip file there which may be installable to the off-line winpe. Alternatively, the program may be installable online in a running winpe and the installer would probable say what's missing and required.

To start, add all the packages in the WAIK and the wireless driver, and throw the installer and depends.exe into /system32..., and have plenty of RAM.

... just a thought.

Regards :)

#25
wimb

wimb

    Senior Member

  • Developer
  • 679 posts
Thanks allanf for your interest and help.

First attempt to use Intel Utility ICS_s32.exe in Windows PE 3.0 environment failed.

However, I will try now to follow approach of PENetwork.script
and add required files and registry entries needed for WiFi Support with encryption.

Your advice to add empty Desktop folder to config\systemprofile works excellent.
We now have Browse for Folder support in Windows PE 3.0

Edited by wimb, 02 February 2010 - 08:48 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN