Wireless support on PE 2.x/3.x

Just in case it slipped by (as it did for me ):
http://www.msfn.org/...i...37.html&hl=

Since 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

Wonko

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

Does anybody know how to make further improvements for support of WPA encryption ?

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
http://www.msfn.org/...mp;#entry906396

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


=

It seems to me like a small step big leap in the right direction.

Very, VERY good work!



Wonko

Oh, this is also a bug
The file which is missing is the "netnwifi.inf".

Maybe I should update it...I'm still working on it but at the moment only on the porting to C++...
Greets Holger

Wireless Internet with WPA2-PSK + AES Encryption is realized in Windows PE 3.0

I have used Registry Settings from Windows 7 edited according to PENetwork.script of Holger
And I have added in Windows PE 3.0 the missing but Required files according to Holger's script.

More details will follow ....

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


=

I have tried in Windows PE 3.0 to make Network Drives and to Share Local Folders.
The first thing to overcome was to add some extra registry values from Windows 7
so that it became possible to Start the LanmanServer.

Added were from Enum\Root\ the entries for LEGACY_SRV LEGACY_SRV2 LEGACY_SRVNET
and 7 Services: LanmanServer srv srv2 srvnet Netlogon NlaSvc LanmanWorkstation
and I have added files related to these services and I have used netserv.inf of Windows 7

Making Network Drives of folders shared by other computer is working OK,
but Sharing the folders on local computer results in Error as indicated.

What will be needed extra to make this last step working ?

I get the impression that in PE 3.0 Security blocks my attempts to Share Local drives or folders.
Probably a User Account with Password is needed ...

In any case until now I cannot Start Network Location Awareness and Netlogon Services .....
=

Windows PE 3.0 with Network Drive Z: and Sharing Error
=


=

for me sharing folder works only in that case when the firewall service is stopped

at build time i use
ControlSet001\Services\MpsSvc Start 4
and
ControlSet001\Services\Ikeext Start 2

seems if 'MpsSvc Start 3' used then the MpsSvc service starts when PENetwork initialize the network
in this case for me sharing folder is not successful

for me sharing folder works only in that case when the firewall service is stopped

at build time i use
ControlSet001\Services\MpsSvc Start 4
and
ControlSet001\Services\Ikeext Start 2

seems if 'MpsSvc Start 3' used then the MpsSvc service starts when PENetwork initialize the network
in this case for me sharing folder is not successful

Thanks dera,

Disabling the Firewall in build with registry setting ControlSet001\Services\MpsSvc Start 4 has solved the problem.

Now I can Share drives and folders, but only for the originally given permissions.
Changing permissions is not yet possible in Windows PE 3.0. I have got to look at this.

The new created Share GDOWN of folder Downloads is not accessible yet at other computer running XP.
But folders of Windows 7 Users and XP drive and folder with given permission are accessible allready.
=

Windows PE 3.0 with Network Drives Z: and Y: and Sharing of Local Drives
=


=

The new created Share GDOWN of folder Downloads is not accessible yet at other computer running XP.

i think it is mandatory to define the 'Username:' and 'Password:' in PENetwork's 'File Sharing' window,
i can access the shared forlder from other XP computer if i map that shared network path to drive letter,
or when i disable the guest account on the booted WinPE 3.0
(net.exe user guest /active:no)

p.s.
i have tried on PE made by the Win7RescuePE project,
regarding permission
try to share via 'fsmgmt.msc'
or via command
net.exe share sharename=drive:\path /grant:user,read|change|full

Username and Password were defined in PENetwork.
On remote computer I can map shared network path to drive letter,
and can see all folders, but get no permission for access.

Disable the guest did not solve the problem.

fsmgmt.msc is not yet available in Windows PE 3.0 and simple adding it does not work yet.
So I have got to add some more functionality from Windows 7

The net.exe share commands are working, but they also don't give the permission.

Batch Program Make_PE3.cmd was made to create Windows PE 3.0 ISO Boot Image With PStart Menu for Portable Programs.

As source is used AIK for Windows 7 and additional files and registry entries from Installed Windows 7 OS.

Download - Make-PE3 - mirror

More Info:
http://www.911cd.net...o...21883&st=35
=

Windows PE 3.0 with PStart Menu for PE3 System and for Portable Programs
=

=

@wimb

Thank you for this useful script. I am experimenting with it.
One remark : there is a hardcoded place in the script, so if I set :

SET PEWork=C:\tmp\winpe3_%ARCH%
then instead of :
echo 3) Make pe3.iso in Target folder C:\winpe3_%ARCH%

the batch should use %PEWork%.

the batch should use %PEWork%.

You are right, thanks for your remark.

In computing the script only uses %PEWork% and works correct to make your pe3.iso,
but in 2 messages on screen it will indicate Target folder C:\winpe3_%ARCH%

I will make the necessary replacements.

The booting process is very fast. I have a wishlist :
1- Possibility to change keyboard layout at build (or at least dynamically after boot).
2- Possibility to start other programs than pstart.
3- Possibility to have explorer-like shell, something that shows running applications in the bottom taskbar. Currently I have to minimize the current application to see pstart to run other application or to switch to existing one.

Question: how does this tool position versus Win7RescuePE/Win7PE from Winbuilder?
If I use exclusively USB key (writeable media), and have mostly portable appications, with
the 4 provided directories :

Make_PE3\PE3_mod\PE3_add
Make_PE3\PE3_mod\PE3_reg
Make_PE3\PE3_mod\WIN7_add
Make_PE3\PE3_mod\WIN7_drivers

it seems that I can easily add drivers, or applications requiring registry settings, without using the big Winbuilder?

Currently as Winbuilder beginner, I find that it is more cryptic than the old BartPE since Winbuilder relies on scripts which are for me a blackbox. With BartPE I can provide the files, xml, inf etc... to create/adapt a new plug-in. Make_PE3, in addition to provide Wireless with authentication support, seems to give user more control of what he/she wants to add to the build.

Please share your thoughts. Thank you.

If you want to start other programs than PStart.exe then you need to modify file startnet.cmd
located in PE3_mod\PE3_add\x86\Windows\System32 folder
In this way you can easily control what is running at Startup.

Other keyboard layout will be possible, but I have no experience with that yet.

In general I resize application windows such that PStart Window remains visible at the right edge of the screen.
PStart windows serves then as taskbar. May be we can add to the build a shell with real taskbar as you described.
PStart will keep a record of windows size and position, such that on next boot you get your last size.

The present approach keeps the boot image small, which is good for fast booting (30 sec from HDD or 4 min from USB-stick).
Building the pe3.iso boot image with Make_PE3.cmd is very fast, about 2 minutes.
Also you have easy control of what is added to the build and you don't need a Windows 7 Setup DVD.
You simply make use of files and registry settings of installed Windows 7 operating system to improve Windows PE 3.0
Once these files and settings are collected in WIN7_add and PE3_reg folder, you don't need even any more the Installed Windows 7 as source.

To add a WLAN device driver to a Running Windows PE 3.0 you type at the command prompt:

drvload.exe <inf_path>

You can specify multiple inf files by separating each inf file entry with a comma.

Make_PE3.cmd uses the Deployment Image Servicing and Management (DISM) tool to add drivers to the Windows PE 3.0 ISO Boot Image.
Add your Driver files e.g. for WLAN in folder PE3_mod\WIN7_drivers\x86 (recurse scanning allows subfolders with driver files)

The Portable Programs running from PStart Menu are not part of the ISO Boot Image,
so that you can easily make program changes without the need to rebuild the ISO file.
Moreover, you can use the Portable Programs on any occasion, e.g. also without booting from the Windows PE 3.0 ISO

Building Win7RescuePE/Win7PE with Winbuilder involves adding programs to the build and you need a Windows 7 Setup DVD as Source.
Program changes require to rebuild in about 12 minutes with WinBuilder to make a new ISO.
This is less flexible and makes the build much larger and the programs cannot be used easily without booting.
Win7PE is similar in booting and one can use grub4dos ISO emulation to boot from HDD or from USB-stick,
but Win7Rescue PE (500-600 MB). In both cases I was not able to connect Wireless with Internet.

@wimb

Thank you for your informative explanations. They will be a very good start for me.
Speed is important, and network + Wi-Fi access too. So make_pe3.cmd is excellent for me.
I tested successfully in 3 different systems with different wireless hardware.

The keyboard layout matter should not be difficult by reusing what was done on WinPE1.x/WinPE2.x or WinRescue7PE (some registry changes apparently + appropriate DLL). I will try to do this. This function is important when using the command line or when inputting the WPA-PSK key :-).

The classic shell will be welcome, although I am trying to familiarize with Pstart. Currently I use Pstart to start only Total Commanderm, then use the latter as shell, but I need the taskbar functionality to switch quickly between started applications. I will try the resize window method as you said.

By now, make_pe3.cmd is more suitable to my needs than Win7RescuePE (fast build, fast boot, wireless support, much easier to add drivers or new applications, easier update for existing applications without change to the iso, no problem for portable applications...).

Build time: 4'30" under XP SP3.
Boot time:
- 1' on USB HDD and real machine, much longer inside Vmware as USB.
- 5' on Celeron M (this is curious, since the hard disk is not much slower, I guess it is due to the hardware configuration).

For your information:
> but Win7Rescue PE (500-600 MB) is booting from CD and not from USB-stick or HDD.
For me Win7Rescue can be booted as normal Win7PE or Win7, refer to this topic:
http://www.boot-land...showtopic=10383

Speed is important, and network + Wi-Fi access too. So make_pe3.cmd is excellent for me.
I tested successfully in 3 different systems with different wireless hardware.

Good to know

I am interested in the improvements that you can make for keyboard layout or shell with taskbar.

@wimb

For the keyboard layout and regional settings, I found that it could be done via the registry.
But I need make_pe3.cmd capability to invoke an optional user-provided registry file like :
\PE3_mod\PE3_reg\x86\PE3-HKCU_CUSTOM.reg
Better, make_pe3.cmd should be open and offer a way to call optional user-provided .reg file.

Following is the content of such file that should offer support for French keyboard and country-specific settings:

Windows Registry Editor Version 5.00



[HKEY_CURRENT_USER\Keyboard Layout\Preload]

; 409: US, 40C: French

"1"="0000040C"



[HKEY_CURRENT_USER\Control Panel\International]

"Locale"="0000040C"

"iCountry"="33"

"iCurrDigits"="2"

"iCurrency"="3"

"iDate"="1"

"iDigits"="2"

"iLZero"="1"

"iMeasure"="0"

"iNegCurr"="8"

"iTime"="1"

"iTLZero"="1"

"Locale"="0000040C"

"s1159"=""

"s2359"=""

"sCountry"="France"

"sCurrency"="Ç"

"sDate"="/"

"sDecimal"=","

"sLanguage"="FRA"

"sList"=";"

"sLongDate"="dddd d MMMM yyyy"

"sShortDate"="dd/MM/yyyy"

"sThousand"="á"

"sTime"=":"

"sTimeFormat"="HH:mm:ss"

"iTimePrefix"="0"

"sMonDecimalSep"=","

"sMonThousandSep"="á"

"iNegNumber"="1"

"sNativeDigits"="0123456789"

"NumShape"="1"

"iCalendarType"="1"

"iFirstDayOfWeek"="0"

"iFirstWeekOfYear"="0"

"sGrouping"="3;0"

"sMonGrouping"="3;0"

"sPositiveSign"=""

"sNegativeSign"="-"

 

[HKEY_CURRENT_USER\Control Panel\International\Geo]

"Nation"="244"

Other questions:
1- How do I add EXE and DLL files to \windows\system32 directory at build?
2- How do I add .sys files to \windows\system32\drivers directory at build?

@wimb

For the shell, I found BSexplorer, very easy to use:
http://www.boot-land...?showtopic=8525

So in startnet.cmd you could start both bsexplorer and pstart if needed.
bsexplorer will handle the familiar taskbar.

So to summarize:
- wireless OK
- shell OK
- add driver OK (either during build by putting in \PE3_mod\WIN7_drivers directory, or with drvload command)
- need possibility to add registry entries at build (via user-provided .reg file)
- need possibility to add files to \windows\ directory
- need possibility to add files to \windows\system32\ directory

Then pe3.iso booted from writeable media like USB key/HDD, with portable applications would be very
easy to maintain and update, with lot of possibilities (rescue, install OSes...), with its main strong points
(fast build, fast boot, wireless support).

For example Imdisk could be integrated at build (since it has already a plug-in in BartPE etc...), so the conversion to registry entries and files could be done.

- need possibility to add registry entries at build (via user-provided .reg file)
- need possibility to add files to \windows\ directory
- need possibility to add files to \windows\system32\ directory

Is already there, you can use Make_PE3\PE3_mod\PE3_add\x86\Windows\System32 folder

Use the same directory structure as in Windows PE 3.0

Custom Registry might be added via file PE3_CUSTOM.reg placed in the above folder,
and use launch from startnet.cmd with REGEDT32.EXE /S

Thanks for shell solution.

For the keyboard layout and locale settings, there is a simpler way, no need for custom registry settings.
In Make_PE3.cmd, after mounting the boot.wim:
imagex.exe /mountrw "%PEWork%\ISO\sources\boot.wim" 1 "%PEWork%\mount"

I added the following lines:

ECHO SETTING KEYBOARD LAYOUT AND LOCALES
ECHO.
intlcfg.exe -inputlocale:fr-fr -image:%PEWork%\mount
intlcfg.exe -syslocale:fr-fr -image:%PEWork%\mount
intlcfg.exe -userlocale:fr-fr -image:%PEWork%\mount

Note: change fr-fr to other values to match your keyboard layout and locale.
This works well for me.

For the keyboard layout and locale settings, there is a simpler way, no need for custom registry settings.
In Make_PE3.cmd, after mounting the boot.wim:
imagex.exe /mountrw "%PEWork%\ISO\sources\boot.wim" 1 "%PEWork%\mount"

I added the following lines:

ECHO SETTING KEYBOARD LAYOUT AND LOCALES
ECHO.
intlcfg.exe -inputlocale:fr-fr -image:%PEWork%\mount
intlcfg.exe -syslocale:fr-fr -image:%PEWork%\mount
intlcfg.exe -userlocale:fr-fr -image:%PEWork%\mount

Note: change fr-fr to other values to match your keyboard layout and locale.
This works well for me.

Very nice, thanks for your help

It is almost perfect for you now I suppose

It is almost perfect for you now I suppose

You are right, I am very satisfied of your batch file now. With fast build, fast boot, portable apps, drivers add, registry add, files add to system32/[drivers], the sky is open :-).

Question: how can I avoid to indicate Windows 7 drive? Currently I use XP to build, and mount Windows 7 drive by mounting a backup disk image. In other words, the following directory and file are not clear for me:
\PE3_mod\WIN7_add
\PE3_mod\WIN7_Files.txt

Other question: in startnet.cmd, it seems that there could be some possible optimizations.

My Old code:

for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\Win7PE.cd  Start %%i:\Programs\bsexplorer\explorer.exe

for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\Win7PE.cd  Start %%i:\totalcmd.cmd

for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\Win7PE.cd  Start %%i:\Programs\PStart\PStart.exe

Proposed new code:

FOR %%i IN (c d e f g h i j k l m n o p q r s t u v w x y z) DO (

	  if exist %%i:\Win7PE.cd ( 

		Start %%i:\Programs\bsexplorer\explorer.exe

		Start %%i:\totalcmd.cmd

		Start %%i:\Programs\PStart\PStart.exe

		goto _exitfor

	  )

)

:_exitfor

The new code uses a tag file and quits the loop as soon as match is found, and avoids n times loop if there are n applications to be started.

Question: how can I avoid to indicate Windows 7 drive? Currently I use XP to build, and mount Windows 7 drive by mounting a backup disk image. In other words, the following directory and file are not clear for me:
\PE3_mod\WIN7_add
\PE3_mod\WIN7_Files.txt

The folder WIN7_add\x86 is filled by the program with the required Windows 7 files from list given in
WIN7_add\x86\WIN7_add_files.txt file
Later the content of WIN7_add\x86 is copied with xcopy to folder mount.

The required directory structure is generated by the program in WIN7_add\x86 folder

The file WIN7_Files.txt sever as a mother which is copied to file WIN7_add_files.txt if it does not exist.