Jump to content











Photo
- - - - -

[SHELL] EZxplorer

shell pe

  • Please log in to reply
No replies to this topic

#1 alebcay

alebcay
  • Members
  • 3 posts
  •  
    United States

Posted 11 July 2013 - 07:53 PM

EZxplorer is a shell made for WinPE 4.0 and above (whenever 4.5 etc comes out...).

 

***THIS PROGRAM ONLY WORKS ON WinPE 4! DO NOT try it on any vanilla PE built on lower version. If there's a way to get .NET 4.0 onto some Winbuilder/MakePE etc. PE build, this will work also.**

 

Features:

-Quick access to File Explorer, Task Manager, RegEdit, etc. Also has shutdown functionality

-File Explorer functionality provided by Explorer++ (released under GPL), www.explorerplusplus.com

 

Upcoming/planned features:

-Lock computer function

 

Requirements:

- WinPE 4.0 (any version less than 4.0 does not support .NET4, and therefore cannot run the application), assuming you are building with WAIK/WADK

-.NET4.0 package must be included in the WinPE source (use DISM to add package)

 

Installation instructions:

1. Extract all files from the ZIP file provided at the download link here: http://reboot.pro/fi.../330-ezxplorer/

 

2. Set up a PE working directory.

copype.cmd x86 c:\winpe_x86

Our working directory will be C:\winpe_x86, and we will be making it in the x86 architecture.

 

3. Mount the WIM file of the PE installation In this example, we will mount to the directory "C:\Mount".

imagex /mountrw c:\winpe_x86\winpe.wim 1 C:\Mount

/mountrw signals ImageX to give us Read and Write access to the contents of the image, specifically index number "1" of the image. A WIM file stores multiple versions of files called indices, each of which may be a different version of Windows (that is how one install DVD can contain every version of Windows).

 

4. Cut/copy files into any directory of the source tree of the mounted WIM file. Make sure that all of the files in the ZIP archive remain together in the same directory.

 

5. Update winpeshl.ini in the System32 folder to point to the EZxplorer.exe file:

[LaunchApp]
AppPath = <path_to_EZxplorer.exe>

6. Using DISM from the Deployment Tools Command Prompt of the ADK, add .NET4 (and it's dependency, WMI) to the installation. This is the step that needs WinPE 4 (if you don't have WinPE 4, then this step will fail):

dism /image:C:\Mount /add-package /packagepath:"WinPE-WMI.cab"
dism /image:C:\Mount /add-package /packagepath:"en-us\WinPE-WMI_en-us.cab"
dism /image:C:\Mount /add-package /packagepath:"WinPE-NetFx4.cab"
dism /image:C:\Mount /add-package /packagepath:"en-us\WinPE-NetFx4_en-us.cab"

(assuming your mountpoint is C:\Mount, and you may have to modify your packagepath attribute to reflect your current/working directory)

 

7. Close any File Explorer windows that are navigated to the mount folder (or inside it). Commit and unmount the WIM file.

Imagex /unmount /commit C:\Mount

8. Build the media. Here, we will be building an ISO file.

makewinpemedia.cmd /ISO C:\winpe_x86 C:\winpe_x86\winpe_x86.iso

9. Burn the ISO file to a CD, or mount it to a VM. Hopefully, this works.

 

Any problems with installation? Let me know. It's been a while since I've worked with PE and even Microsoft's own documentation is messed up.


  • Nuno Brito likes this





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

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users