Re:KSP2 is spamming the Windows Registry until the game stop...
by pests on Monday September 25, 2023 @09:18PM
(#37653098)
> you've got essentially a single GUI application and CLI or programmatic access
You can export a registry path as a text file, make changes in perferred editor, then import it again. It's annoying but I've done it before when needed.
Re:KSP2 is spamming the Windows Registry until the game stop...
by uxp8u61q on Tuesday September 26, 2023 @01:31AM
(#37654842)
Or you can use powershell that allows you to browse the registry as if it were a filesystem.
PS> cd HKLM:\Software\Microsoft\Windows\CurrentVersion
PS> ls
[...bunch of stuff...]
PS> gp Themes DesktopBackground
DesktopBackground : c:\windows\web\wallpaper\[...default system wallpaper...]
Re:KSP2 is spamming the Windows Registry until the game stop...
by imtringued on Tuesday September 26, 2023 @03:33AM
(#37655745)
That kind of defeats the purpose, doesn't it?
Re:KSP2 is spamming the Windows Registry until the game stop...
by uxp8u61q on Tuesday September 26, 2023 @07:46AM
(#37657881)
How so? I don't follow. It's still the same optimized, global, secure key-value store. It just has a different interface if you cannot possibly fathom using different tools than the ones you use to deal with the filesystem.
Pwsh is pretty neat in that regard. Besides the actual filesystems drives, many systems have "providers" that allow you to treat their objects as files: the registry, environment variables, the functions defined in your session, the variables, the aliases... Unix's "everything is a file" became "everything is an item".
Editing, sure, you've got essentially a single GUI application and CLI or programmatic access. Your options are certainly more limited than the plethora of text editors available.