Jump to content











Photo
* * * * * 4 votes

Make-PE3 Program to Create Portable Windows 7 PE

7pe tutorial

  • Please log in to reply
867 replies to this topic

#801 Agent47

Agent47

    Frequent Member

  • Advanced user
  • 164 posts
  •  
    India

Posted 15 March 2013 - 04:12 AM

Hi Wimb

 

I fixed Media player issue by using a reg fix and Copy it to the "Make_PE3\PE3_mod\PE3_reg\x86\plugins" folder.

 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\PE3-SOFTWARE\Microsoft\MediaPlayer\Setup\Installed Versions]
"wmp.dll"=hex:00,00,0c,00,6a,44,b1,1d
"wmplayer.exe"=hex:00,00,0c,00,6a,44,b1,1d
"wmploc.dll"=hex:00,00,0c,00,6a,44,b1,1d

[HKEY_LOCAL_MACHINE\PE3-SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\WindowsFeatures\WindowsMediaVersion]
@="12.0.7601.17514"
"Version"=hex:00,00,0c,00,6a,44,b1,1d

 

 

I also made a plugin for "ShutdownPE" and now shutdown and restart buttons are working fine in my build


Edited by Agent47, 15 March 2013 - 04:13 AM.


#802 Agent47

Agent47

    Frequent Member

  • Advanced user
  • 164 posts
  •  
    India

Posted 15 March 2013 - 07:24 AM

Hi Wimb

 

I forgot to say that i use "Windows 7 Ultimate SP1 32 US English" version as source.



#803 wimb

wimb

    Platinum Member

  • Developer
  • 2679 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 15 March 2013 - 08:10 AM

I fixed Media player issue by using a reg fix and Copy it to the "Make_PE3\PE3_mod\PE3_reg\x86\plugins" folder.

 

I also made a plugin for "ShutdownPE" and now shutdown and restart buttons are working fine in my build

 

Thanks for giving details on how to fix madia player error.

 

Can you upload your plugin for Shutdown PE so that I can test it and possibly add it to Make_PE3 ?

 

:cheers:



#804 Agent47

Agent47

    Frequent Member

  • Advanced user
  • 164 posts
  •  
    India

Posted 15 March 2013 - 10:32 AM

Hi Wimb

 

Here is the link to my "ShutdownPE" plugin : http://www.mediafire...y1u9vvoilj5uq5w

 

 

All credit goes to Homes32 who made this great tool and Wimb for Make_PE3.

 

Default behavior of ShutdownPE can be altered via an ini file. More details on the development topic : 

 

http://reboot.pro/to...012-shutdownpe/


Edited by Agent47, 15 March 2013 - 10:41 AM.


#805 wimb

wimb

    Platinum Member

  • Developer
  • 2679 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 20 March 2013 - 08:26 AM

Hello Agent47,
 
Can you test Make_PE3_43 to make Media Version using your Win7 Source DVD mounted in ImDisk Virtual drive
(use R-mouse menu to mount Win7 DVD iso file) .
Then boot with the created 7pe_x86_M.iso from grub4dos menu on local harddisk Target Drive and see if Media Player fix is working for you ?
 
ShutdownPE is added as option, but if desired then user must manually add it as described.
 
Download Make_PE3_43 from http://www.mediafire.../?fi81wqcdmzdv5
 
:cheers:
 
Attached File  2013-03-20_101840.png   1MB   37 downloads


#806 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 20 March 2013 - 11:38 AM

Since improvements for the project are again on the table, i recommend replacing pnputil with dpinst and dpinstl. They do the same job faster.

:cheers:

#807 wimb

wimb

    Platinum Member

  • Developer
  • 2679 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 20 March 2013 - 01:47 PM

Since improvements for the project are again on the table, i recommend replacing pnputil with dpinst and dpinstl. They do the same job faster.

 

dpinst.exe is already used by driver_fix.cmd via drv_find.au3 for external drivers e.g. video driver found in drv folder searched on any drive.

 

When in pnp_fix.cmd replacing pnputil.exe by dpinst.exe /q /path %SystemRoot%\System32\DriverStore\FileRepository

then the process to install all drivers takes even more time (pnputil=2.5 min and dpinst=3.5 min)

 

Can you explain what you have in mind and give details on where and how improvements can be made.

 

:cheers:



#808 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 20 March 2013 - 02:45 PM

When in pnp_fix.cmd replacing pnputil.exe by dpinst.exe /q /path %SystemRoot%\System32\DriverStore\FileRepository
then the process to install all drivers takes even more time (pnputil=2.5 min and dpinst=3.5 min)
That's curious, i always had the exact opposit impression.
Will time driver install from Host OS, with both tools again and report back.

:cheers:

#809 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 21 March 2013 - 03:28 PM

You seem to be right Wimb.
Using your "Drivers from HostOS" is way faster than using dpinstl to install drivers from the HostOS.

Though declaring a clear winner is kinda tricky. After running your "Drivers from HostOS" one can still see a bunch of unknown devices in device manager. This is not the case after using dpinst+dpinstl.

So the second might just take longer, because it installs more drivers.

Also, when running pnputil agains X:\Windows\Inf, it's a good deal slower, than running dpinst against X:\Windows\System32\Driverstore\Filerepository.

It's probably your autoit script, which makes pnputil more eficient, than running it on it's own.

:cheers:

#810 wimb

wimb

    Platinum Member

  • Developer
  • 2679 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 21 March 2013 - 04:41 PM

Screenshot here http://reboot.pro/to...-33#entry169723

shows that all drivers are auto installed in Media Version after pnp_fix.cmd has finished.

 

There are several stages:

driver_fix.cmd is the initial installer of essential drivers and will start services and then call pnp_fix.cmd in case of Media Version.

pnp_fix.cmd (visible on taskbar when running) includes install Drivers from HostOS by using pecmd.exe and then pnputil to install all machine drivers.

 

With your manual approach you must compare the runtimes of Drivers from HostOS + dpinst.exe against running pnp_fix.cmd

where both cases give the comparable result of all drivers are installed.

 

:cheers:



#811 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 21 March 2013 - 11:33 PM

Wimb, forget what, i've said.
I thought you use pnputil exclusivly. But you switch forth and back between various solutions, so i think you will have already done all possible test to figure out what works best.

Two questions though.
- When and where is pnpbatch.cmd used?
- Why do you install hal.inf, cpu.inf, usb.inf, msports.inf twice?

:cheers:

#812 wimb

wimb

    Platinum Member

  • Developer
  • 2679 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 22 March 2013 - 06:47 AM

Two questions though.
- When and where is pnpbatch.cmd used?
- Why do you install hal.inf, cpu.inf, usb.inf, msports.inf twice?

 

driver_fix.cmd is the initial installer of essential drivers and will start services and then call pnp_fix.cmd in case of Media Version.

Manually you can run pnp_fix.cmd from Admin Tools\Hardware programs menu

 

Everything was designed for best performance and to offer flexibility and is the result of a lot of testing.

Running some inf twice does not take extra time, but it was handy not to miss them in pnp_fix.cmd

 

:cheers:



#813 Agent47

Agent47

    Frequent Member

  • Advanced user
  • 164 posts
  •  
    India

Posted 22 March 2013 - 09:36 AM

Hi Wimb

 

I did a media version build with new "make_PE3" version 43 with SP1 Ultimate as source. Yes, media player works fine in new version  :)  


Edited by Agent47, 22 March 2013 - 09:37 AM.

  • wimb likes this

#814 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 22 March 2013 - 11:34 AM

driver_fix.cmd is the initial installer of essential drivers and will start services and then call pnp_fix.cmd in case of Media Version.
Manually you can run pnp_fix.cmd from Admin Tools\Hardware programs menu
Have you misread my question by any chance?
I was wondering about the file pnpbatch.cmd in your PE. It doesn't seem to be called from anywhere.

:cheers:

#815 wimb

wimb

    Platinum Member

  • Developer
  • 2679 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 22 March 2013 - 12:03 PM

Have you misread my question by any chance?
I was wondering about the file pnpbatch.cmd in your PE. It doesn't seem to be called from anywhere.

 

I thought you meant pnp_fix.cmd but

pnpbatch.cmd is indeed not used. It belongs to HWPnp.exe

 

:cheers:



#816 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 22 March 2013 - 02:12 PM

Thanks, wimb!

:cheers:

#817 wimb

wimb

    Platinum Member

  • Developer
  • 2679 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 25 March 2013 - 07:09 AM


-
*** Update Make_PE3_43 package ***
 
  • Update  - Make_PE3 can be used in Windows 8/7/XP Multi-Boot environment
  • Update  - Windows Media Player registry Fix in case of Media version made from Win 7 SP1 DVD as Source
  • Added   - ShutdownPE is added as option, but if desired then user must manually add it as described
Thanks to Homes32 and Agent47 http://reboot.pro/to...-33#entry169408
  • Added   - GetWAIKTools - Thanks to JFX
  • Added   - msdmo.dll to WIN7_add_explor.txt filelist - support of Firefox V18 & V19 - Thanks to mbarnes
  • Changed - Program Version - latest version is 4.3
 
 
Download  - Make_PE3_43
 
It is required to extract Make_PE3.exe to the root of your drive
 
Make_PE3 can be used in Windows 8/7/XP Multi-Boot environment
Source can be fresh installed Win7 SP0 without Updates or Win7 DVD SP0 or SP1 - x86 or x64 versions
 
 
:cheers:


#818 wimb

wimb

    Platinum Member

  • Developer
  • 2679 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 28 March 2013 - 11:18 AM

-
*** Update Make_PE3_44 package ***
 
 
  • Added   - Adobe Flash Version 11 Plugin for Make_PE3 - file Make_PE3_Flash_V11.exe
  • Changed - Program Version - latest version is 4.4
 
 
Download  - Make_PE3_44
 
It is required to extract Make_PE3_44.exe to the root of your drive.
Make_PE3_44.exe does not contain Adobe Flash - You need to make use of the NEW plugin.
The plugin has the same folder structure as Make_PE3 and to insert the plugin you can
Extract Make_PE3_Flash_V11.exe to the same drive as where Make_PE3 folder is located.
 
Make_PE3 can be used in Windows 8/7/XP Multi-Boot environment
Source can be fresh installed Win7 SP0 without Updates or Win7 DVD SP0 or SP1 - x86 or x64 versions
Adobe Flash V 11 plugin supports x86 and x64 version of 7 PE - Browsers IE8 Or Portable Firefox Opera or QtWeb
 
 
:cheers:
 


#819 gbohn

gbohn
  • Members
  • 8 posts
  •  
    United States

Posted 29 March 2013 - 02:23 AM

Hi;

 

   I just tried using Make PE 3_44 to make the 64-bit pe3_amd64_E image. This boots o.k., but a few applications I added fail (when I try to start them) with a message about a 'side-by-side' failure:

 

"X:\Program Files\LatencyMon\LatMon.exe

 

The application has failed to start because it's side by side configuration is incorrect"

 

  This only happens when I use a 64-Bit Windows 7 Professional disk with SP1 as the "Windows 7 Source" in Make_PE3.exe.

 

  If I use the 64-Bit Professional version without SP1 as the source, I don't see this issue. I used the 'middle' option in Make_PE3 of 'Get Win 7 files - and use AIK...".

 

  So far, this happens with two applications I added.

 

  The message said to run 'sxstrace.exe'. I did this, but don't know how to use the results. An excerpt is show at the end of this post.

 

  Any suggestions on how to fix this? From the announcement of 3_44, I thought it was saying that an SP1 source was now o.k. to use.

 

  Thanks;

 

=================
Begin Activation Context Generation.
Input Parameter:
	Flags = 0
	ProcessorArchitecture = Wow32
	CultureFallBacks = en-US;en
	ManifestPath = X:\Program Files\LatencyMon\LatMon.exe
	AssemblyDirectory = X:\Program Files\LatencyMon\
	Application Config File = 
-----------------
INFO: Parsing Manifest File X:\Program Files\LatencyMon\LatMon.exe.
	INFO: Manifest Definition Identity is UACAwareApplication,processorArchitecture="*",type="win32",version="1.0.0.0".
	INFO: Reference: Microsoft.Windows.Common-Controls,language="*",processorArchitecture="*",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
INFO: Resolving reference Microsoft.Windows.Common-Controls,language="*",processorArchitecture="*",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0".
	INFO: Resolving reference for ProcessorArchitecture WOW64.
		INFO: Resolving reference for culture en-US.
			INFO: Applying Binding Policy.
				INFO: No publisher policy found.
				INFO: No binding policy redirect found.
			INFO: Begin assembly probing.
				INFO: Did not find the assembly in WinSxS.
				INFO: Attempt to probe manifest at X:\windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
				INFO: Did not find manifest for culture en-US.
			INFO: End assembly probing.
		INFO: Resolving reference for culture en.
			INFO: Applying Binding Policy.
				INFO: No publisher policy found.
				INFO: No binding policy redirect found.
			INFO: Begin assembly probing.
				INFO: Did not find the assembly in WinSxS.
				INFO: Attempt to probe manifest at X:\windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
				INFO: Did not find manifest for culture en.
			INFO: End assembly probing.
		INFO: Resolving reference for culture Neutral.

 

 

 

 



#820 wimb

wimb

    Platinum Member

  • Developer
  • 2679 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 29 March 2013 - 06:07 AM

There is SxS_7PE_SFX.exe in folder MULTI\SxS_Fix_Win7PE made by JFX

Should solve most Side by Side errors in Win7PE

 

Copy content of Make_PE3\MULTI folder to root of HDD or USB boot drive

Run SxS_7PE_SFX.exe after you booted into your 7PE

 

Apparently NetFrame is needed. Did you use the Checkbox NetFrame ?

If not then use it and Rebuild 7PE



#821 ktp

ktp

    Silver Member

  • Advanced user
  • 758 posts

Posted 29 March 2013 - 06:28 AM

Hello,

For information.
I change driver_fix.cmd to multitask call to audio_usb_fix.cmd and network_fix.cmd + run SxS.
By doing so I do not have to wait for the black window prompt screen installing drivers, and got
immediately access to the desktop to run utilities without loosing anything.                                                                                             
 

:: ==========================================================================================================================
:: ====================================== driver_fix.cmd ====================================================================
:: ==========================================================================================================================
TITLE driver_fix.cmd - Install of Drivers in PE3 - Wait ....
@ECHO OFF
CLS
 
SETLOCAL ENABLEEXTENSIONS
SETLOCAL ENABLEDELAYEDEXPANSION
 
    start "Audio driver fix PE3" /min "%SystemRoot%\System32\audio_usb_fix.cmd"
    start "Network driver fix PE3" /min "%SystemRoot%\System32\network_fix.cmd"
 
    IF EXIST %SystemRoot%\System32\SxS_7PE_SFX.exe (
    %SystemRoot%\System32\SxS_7PE_SFX.exe
    )
 
EXIT

 

 

:: ==========================================================================================================================
:: ====================================== audio_usb_fix.cmd ====================================================================
:: ==========================================================================================================================
TITLE audio_usb_fix.cmd - Install of audio and USB Drivers in PE3 - Wait ....
@ECHO OFF
CLS
 
SETLOCAL ENABLEEXTENSIONS
SETLOCAL ENABLEDELAYEDEXPANSION
 
 
:_install
 
ECHO.
ECHO  Install of Audio Drivers in PE3 - Wait ....
ECHO.
 
PnPutil.exe -i -a X:\Windows\inf\hal.inf
PnPutil.exe -i -a X:\Windows\inf\cpu.inf
pnputil.exe -i -a X:\Windows\inf\battery.inf
PnPutil.exe -i -a X:\Windows\inf\hdaudio.inf
 
ECHO.
ECHO  Install of USB Drivers in PE3 - Wait ....
ECHO.
 
drvload.exe X:\Windows\inf\usb.inf
drvload.exe X:\Windows\inf\usbstor.inf
drvload.exe X:\Windows\inf\msports.inf
 
exit

 

 

 

 

:: ==========================================================================================================================
:: ====================================== network_fix.cmd ====================================================================
:: ==========================================================================================================================
TITLE network_fix.cmd - Install of Network Drivers in PE3 - Wait ....
@ECHO OFF
CLS
 
SETLOCAL ENABLEEXTENSIONS
SETLOCAL ENABLEDELAYEDEXPANSION
 
 
:_install
 
 
ECHO.
ECHO  Install of Network Drivers in PE3 - Wait ....
ECHO.
 
for %%i in (X:\Windows\inf\oem*.inf) do drvload.exe %%i
for %%i in (X:\Windows\inf\net*.inf) do drvload.exe %%i
 
ECHO.
ECHO  Install RAS adapter and AsyncMac in PE3  for USB Modem - Wait ....
ECHO.
 
rundll32.exe streamci,StreamingDeviceSetup {eeab7790-c514-11d1-b42b-00805fc1270e},asyncmac,{ad498944-762f-11d0-8dcb-00c04fc3358c},X:\Windows\INF\netrasa.inf,Ndis-Mp-AsyncMac
 
 
ECHO.
ECHO  Start Broadband - Wait ...
ECHO.
 
cmd /c "netcfg.exe -e -c p -i MS_NDISWAN && netcfg.exe -e -c s -i MS_RASMAN && netcfg.exe -e -c p -i MS_PPPOE"
 
ECHO.
ECHO  Start tcpipreg and ms_ndiswanip - Wait ...
ECHO.
 
net start tcpipreg
netcfg.exe -e -c p -i ms_ndiswanip
 
ECHO.
ECHO  Start of WLAN Service - Wait ...
ECHO.
 
NET START Eaphost
NET START dot3svc
 
:: drvload.exe X:\Windows\inf\netvwifimp.inf
:: drvload.exe X:\Windows\inf\netvwififlt.inf
 
netcfg.exe -c s -i ms_vwifi
 
netcfg.exe -c s -i ms_nativewifip
 
NET START Wlansvc
 
exit

 

 

 



#822 wimb

wimb

    Platinum Member

  • Developer
  • 2679 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 29 March 2013 - 06:55 AM

I change driver_fix.cmd to multitask call to audio_usb_fix.cmd and network_fix.cmd + run SxS.

 

Sure it can be organised differently, but install of some drivers is generally in most cases needed e.g. for using Internet.

Alternatively you can also click on the black window and press C to Cancel if you just want to use direct simple Apps like Ghost.

 

In your case I miss searching for external DriverPacks e.g. video driver and LAN drivers in folder drv

Also pnp_fix.cmd (install all drivers in case of Media Version) and drv_del.cmd are not used.

Deleting added FileRepository folders in PE3 to free drive X:\ is useful to have more free space.

 

:cheers:



#823 Agent47

Agent47

    Frequent Member

  • Advanced user
  • 164 posts
  •  
    India

Posted 29 March 2013 - 10:50 AM

@gbohn

 

I use 32 bit PE always and i highly recommend it for general use. When compared to 64 bit counterparts 32 bit PE is small in size and so boot faster. Also you will face less dependency issues. If you only have a 64 bit DVD in hand you can always download 32 bit enterprise evaluation or any edition from Digital River without violating any license terms. 



#824 AtomicKitten

AtomicKitten

    Member

  • Members
  • 60 posts

Posted 29 March 2013 - 06:03 PM

Hi wimb, 

 

What is the best way to load usb 3 drivers in 7pe or pe3 so it can boot faster (if it's possible) or transfer files faster after fully loaded?

 

Thanks for your great work :)



#825 gbohn

gbohn
  • Members
  • 8 posts
  •  
    United States

Posted 29 March 2013 - 07:11 PM

> There is SxS_7PE_SFX.exe in folder MULTI\SxS_Fix_Win7PE made by JFX

> Should solve most Side by Side errors in Win7PE

 

 Thanks. I gave this a try, but it didn't work. I copied the /MULTI folder to the root (X:\MULTI) of the booted PE disk. When I tried to run the program, it gave me the error I'm trying to fix :-). It said it was unable to run because of a side-by-side error.

 

  Back with Make PE 3_42, I was only able to use the 64-bit Source without SP1 (because of booting issues with the created disk when I used the SP1 version). But, the disks I created (without SP1 source) seems to run o.k.

 

  The 3_44 version also seems to create a working disk too if I use the non-SP1 Win-7 source disk. So, it appears that using the Source disk with SP1 breaks something in this area (at least as compared to before).

 

  I was hoping to use the SP1 Win-7 source since I assumed this has at least some fixes compared to the older one...


Edited by gbohn, 29 March 2013 - 07:36 PM.






Also tagged with one or more of these keywords: 7pe, tutorial

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users