From 7b646242b1d79b271932e65549813e8e26d207b9 Mon Sep 17 00:00:00 2001 From: Jonathan Holmgren Date: Sat, 21 May 2022 11:59:34 -0500 Subject: [PATCH] Updated FAQ (markdown => mediawiki) --- FAQ.md => FAQ.mediawiki | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) rename FAQ.md => FAQ.mediawiki (57%) diff --git a/FAQ.md b/FAQ.mediawiki similarity index 57% rename from FAQ.md rename to FAQ.mediawiki index 58bc91c..0357285 100644 --- a/FAQ.md +++ b/FAQ.mediawiki @@ -1,16 +1,16 @@ Frequently Asked Questions -# General +=General= -## Can I use Winbuilder to build PhoenixPE? +==Can I use Winbuilder to build PhoenixPE?== No. Winbuilder is no longer developed an contains numerous bugs that have not been fixed, some of which are critical. Winbuilder bugs aside PhoenixPE also makes use of PEBakery exclusive features and additional commands that are not present in Winbuilder. -## 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. -## 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. @@ -18,4 +18,10 @@ In my option the 2 projects have different goals. Win10XPE states that _"it's ma 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. -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. \ No newline at end of file +'''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.''' + += Common Issues = + +== 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. Modern OS such as Win11 require at least 4GB RAM, where with Win10 you could sometimes get away with 2GB. \ No newline at end of file