elie/PhoenixPE
1
0
Fork 0
mirror of https://github.com/PhoenixPE/PhoenixPE.git synced 2025-09-17 18:48:04 +02:00
Code Issues Packages Projects Releases Wiki Activity

Updated FAQ (mediawiki)

Jonathan Holmgren
2022-07-08 23:46:25 -05:00
parent 1ba9f0d75a
commit b1e29fbd3a
1 changed files with 10 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
FAQ.mediawiki

@@ -8,15 +8,17 @@ No. Winbuilder is no longer developed an contains numerous bugs that have not be
==Is PhoenixPE a clone/fork of Win10PE_SE/Win10XPE/ETC...== ==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. Win10XPE was released in March of 2018. 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 [https://github.com/pebakery/PEBakery PEBakery engine], providing me with the opportunity and challenge of coding a project from scratch without Winbuilder bug workarounds, hacks, and bloat built up over a decade of Vista/7/8/8.1/10 WinPE evolution. It also assisted greatly in the testing, documentation, and development of the PEBakery engine.
Win10XPE was released several years later, in March of 2018.
==Is PhoenixPE a replacement for Win10XPE?== ==Is PhoenixPE a replacement for Win10XPE?==
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. 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.
PhoenixPE on the other hand targets advanced users and developers that what more control over how and what goes into their PE. It strives to be simple for both users to build, and for developers to contribute/maintain. PhoenixPE on the other hand targets basic/advanced users as well as developers looking for more control over how and what goes into their PE. It strives to be simple for both users to build, and for developers to contribute/maintain.
'''TL;DR: No. It's an alternative. The developers of both projects are part of a vibrate community that works together and shares their knowledge and experience. Use the one that best meets your needs. You can't go wrong.''' '''TL;DR: No. It's an alternative. The developers of both projects are part of a vibrate community that works together and shares their knowledge and experience. Use the one that best meets your needs. You can't go wrong.'''
@@ -30,4 +32,8 @@ Due to changes to Explorer.exe with Win11 to support the redesigned start menu a
== Bluescreen/Issues testing with VMWare/VirtualBox == == Bluescreen/Issues testing with VMWare/VirtualBox ==
It's important to remember when testing with VMWare/VirtualBox you need to take into account the memory and CPU requirements of the PE you will be testing. WinPE is RAM intensive. Remember that just because you configure a VM with 2 CPU's and 4GB RAM, it doesn't mean that it's available to the VM. These resources are shared with the host, and must be free in order to be used by the VM. Errors such as a bluescreen "System Thread Exception Not Found", or hang on PreShell Configuration are almost always caused by too little RAM or not enough CPU resources. Try increasing the resources and/or closing CPU/RAM intensive applications (Web Browsers, games, video streaming, etc.) on the host. Ramdisk size and the size of your boot.wim file all need to be taken into account when determining memory requirements. It's important to remember when testing with VMWare/VirtualBox you need to take into account the memory and CPU requirements of the PE you will be testing. WinPE is RAM intensive. Remember that just because you configure a VM with 2 CPU's and 4GB RAM, it doesn't mean that it's available to the VM. These resources are shared with the host, and must be free in order to be used by the VM. Errors such as a bluescreen "System Thread Exception Not Found", or hang on PreShell Configuration are almost always caused by incorrect virtualization settings, too little RAM, or not enough CPU resources. Try increasing the resources and/or closing CPU/RAM intensive applications (Web Browsers, games, video streaming, etc.) on the host. Ramdisk size and the size of your boot.wim file all need to be taken into account when determining memory requirements.
== My Anti-Virus software says PhoenixPE contains a virus ==
Please refer to [[Security#false-positives|False Positives]].