Update README.md

This commit is contained in:
jazir5 2024-08-30 14:47:43 -07:00 committed by GitHub
parent ddd8f47539
commit fbcfb0233a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -11,7 +11,7 @@ The Enable GamesDows batch script makes Windows boot straight into Steam Big Pic
**How the main functionality works: The enable Game Mode batch script sets steam big picture as the shell (in V2 a VBS script is set as the shell when the computer boots, and then it immediately set Steam as the Shell, then runs a powershell command to start Steam or Playnite as admin> but launches steam as lower privileged (so the virtual mouse and keyboard don't work on system prompts such as task manager yet (in V1), it needs to run as admin to fix that. One of the 4 remaining problems, which again may be solved with V2) The enable Game Mode batch script creates a second VBS script to suppress the command prompt window when Explorer.exe launches in the background > The VBS script launches a second batch script created by the enable script creates and launches the second batch script via a scheduled task after a 20 second delay > delayed explorer batch script resets the shell to to explorer.exe, then launches explorer in the background so that it's possible to exit big picture without running a shortcut (menu performs as expected and exits directly to desktop without manually launching a separate shortcut).**
After another delay once explorer.exe is started (it retains elevated permissions once started), the default shell is reset to Steam Big Picture so that it boots directly to Big Picture as expected upon reboot.
After another delay once explorer.exe is started (it retains elevated permissions once started), the default shell is reset to Steam Big Picture so that it boots directly to Big Picture as expected upon reboot. In V2, the script is reset to the first VBS script which resets the shell to Playnite/Steam Big Picture so the loop starts again every reboot.
The powershell commands are run directly via the batch script, so no secondary powershell script is needed. Everything in the script is done automatically when run as admin.