elie/PhoenixPE
1
0
Fork 0
mirror of https://github.com/PhoenixPE/PhoenixPE.git synced 2025-09-16 10:08:05 +02:00
Code Issues Packages Projects Releases Wiki Activity

added log rotation to project options

Browse Source
This commit is contained in:
Homes32
2022-05-11 19:03:46 -05:00
parent 42e4f7fa02
commit 69a575a0af
3 changed files with 19 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@@ -18,7 +18,7 @@ Download the [latest release]() and unpack it in the desired location. Please re
## Building PhoenixPE
1. Mount or Extract your Win10 ISO to a location of your choice. If you don’t have a Win10 ISO you may use the links on the 'Source Config' script to download the most recent version.
1. Using the 'Source Config' script, select the location of your source you provided in Step 1 and press the 'Save' button.
1. Using the 'Source Config' script, select the location of your source you provided in Step 1.
1. Select the Source `install.wim` image. We recommend using the Pro image.
1. Enable the Apps you wish to include in your build. Note that some Apps require additional files or config. **Do not blindly enable all apps and expect to get a successful build**.
1. Tweak any settings you wish.
@@ -36,11 +36,11 @@ No. Winbuilder is no longer developed an contains numerous bugs that have not be
### Is PhoenixPE a clone/fork of Win10PE_SE/Win10XPE/ETC...
No. PhoenixPE development started around 2014 as a Winbuilder project and was originally envisioned as a replacement for the Win10PE_SE project, which had become bloated and hard to maintain. In 2016 PhoenixPE was re-written from the ground up for use with the PEBakery engine, providing me with the challenge of coding a project from scratch without Winbuilder bug workarounds or resorting to messy .cmd stuff. It also assisted greatly in testing and documentation during PEBakery development.
No. PhoenixPE development started around 2014 as a Winbuilder project and was originally envisioned as a replacement for the Win10PE_SE project, which had become bloated and hard to maintain. In 2016 PhoenixPE was re-written from the ground up for use with the PEBakery engine, providing me with the challenge of coding a project from scratch without Winbuilder bug workarounds or resorting to messy .cmd stuff. It also assisted greatly in testing and documentation during PEBakery development. Win10XPE was released in March of 2018.
### Is PhoenixPE a replacement for Win10XPE?
No. It's an alternative. Both produce a very similar environment based on decades of community members working together. We aren't in competition.
It's an alternative. Both produce a very similar environment based on decades of community members working together. We aren't in competition.
In my option the 2 projects have different goals. Win10XPE states that _"it's main objective is to be simple, user-friendly and to be as fast as possible"_. This caters well to user that just want to press a button and get a working PE without much fuss. Win10XPE does great at providing a simple, pre-packaged experience, however it's core codebase is cumbersome and inconsistent and in an effort to provide a simple user experience, it loses the flexibility and ease of customization advanced users crave.