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

update FAQ

Homes32
2025-01-12 17:41:20 -06:00
parent d1f7d3e5ac
commit 877ee97b35
1 changed files with 23 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
FAQ.mediawiki

@@ -82,13 +82,33 @@ Keep in mind that depending on the software, the process may be different, and/o
You can also check the master branch on github to see if the script has already been updated but has not yet made it into a release package. Scripts in the master branch are considered stable and ready for general use.
== What is `Run from RAM` and when should I use it? ==
Many scripts you encounter when configuring and building PhoenixPE will have a '''''Run from RAM''''' checkbox on the script interface. Enabling the option changes where the program will be '''installed''' in PhoenixPE.
If you select '''''Run from RAM''''' the program will be installed in '''''X:\Program Files'''''. (Packed in boot.wim)
If you do not select '''''Run from RAM''''' the program will be installed in '''''Y:\Programs'''''. (Accessible on the CD/DVD/USB boot media)
The answer to this question depends on what you are doing and what the program needs.
In order to maximize the available resources You should avoid '''''Run from RAM''''' unless one of the following conditions are met:
* You are booting from the network (PXE). Run from Ram is required in this instance.
* If the program needs run from a writable directory because it writes log files or config files to its own directory and you are intending to run from read-only media such as CD/DVD. In this case Run from RAM provides a writable environment.
* If the program has drivers or shell extensions installed (these will stop working if the boot media is removed or unmounted).
* You want any logs/files created by the program to be discarded on shutdown so the program always starts from a default state.
Reasons '''not''' to use '''''Run from RAM''''':
* You need access to the program files when you are not booted into PhoenixPE. For example you want to be able to run them from the boot media or update the program files without rebuilding PhoenixPE.)
* Are the program files large (several hundred megabytes)? Including these in RAM reduces the amount of system RAM available to PhoneixPE. This can cause memory exhaustion on systems with inadequate resources.
* You are using writable media such as a USB drive and want any logs/files/config created by the program to persist on each boot.
= Win11 Support =
== Building from a Win11 source with explorer shell causes blackscreen on boot. ==
Due to changes to Explorer.exe with Win11 to support the redesigned start menu and taskbar, the Win11 explorer.exe desktop crashes in WinPE. This is due to the new taskbar using WinRT API's that are not supported in WinPE. Win11 '''10.0.22000.0''' and prior versions allow you to work around this issue by using explorer.exe from a Win10 source or HostOS. Due to Microsoft's EULA we cannot distribute explorer.exe with PhoenixPE, however the Explorer shell script will allow you to provide explorer.exe from either your Win10 Host or another source.
'''Update:''' As of Win11 22H2 (10.0.22621.382) the explorer.exe shipped with the ISO no longer causes a blackscreen.
Due to changes to Explorer.exe with Win11 to support the redesigned start menu and taskbar, the Win11 explorer.exe desktop crashes in WinPE. This is due to the new taskbar using WinRT API's that are not supported in WinPE. Make sure you are using a Windows version that is tested and supported by the project.
= Common Issues =