aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJMM889901 <41163714+JMM889901@users.noreply.github.com>2024-07-06 22:27:16 +0100
committerGitHub <noreply@github.com>2024-07-06 23:27:16 +0200
commita69afc51e709c24f1fd22a16f89ac36e0c1a136f (patch)
treeff22430595ee6efcb5e31da8bcc9e07b5900442a
parentbfcaf444f6c4636f97a4b97640f6eb6d2b808c22 (diff)
downloadNorthstarWiki-a69afc51e709c24f1fd22a16f89ac36e0c1a136f.tar.gz
NorthstarWiki-a69afc51e709c24f1fd22a16f89ac36e0c1a136f.zip
Remove ~ that people keep putting in the system variable (#224)
For the record, `~0x20000000` clears the 29th bit of the result from cpuid, while `0x20000000` replaces the result with one with just the 29th bit set (OPENSSL_ia32cap.3). The 29th bit represents the Intel SHA Extensions. As such, if the second one (without the ~) works, the actual solution has nothing to do with the 29th bit; it's one of the others.
-rw-r--r--docs/installing-northstar/troubleshooting.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/installing-northstar/troubleshooting.md b/docs/installing-northstar/troubleshooting.md
index 91dd8e5..9fa10f3 100644
--- a/docs/installing-northstar/troubleshooting.md
+++ b/docs/installing-northstar/troubleshooting.md
@@ -80,9 +80,9 @@ On newer Intel CPUs you might see a message like this
If you are seeing this in the main menu of TF|2 and have a 10th generation or newer Intel CPU this is a bug which has a simple fix:
In the Windows Start menu on the bottom left search for "Edit the system environment variables" and open the program. In the "advanced" tab click on "Environment Variables..." near the bottom.\
-In System Variables (not user variables) click "New..." and add a new system variable where the variable name is `OPENSSL_ia32cap` and the value is `~0x200000200000000`. Make sure to click OK to apply the changes. Finally restart your device and you should be good to go.
+In System Variables (not user variables) click "New..." and add a new system variable where the variable name is `OPENSSL_ia32cap` and the value is `0x200000200000000`. Make sure to click OK to apply the changes. Finally restart your device and you should be good to go.
-If you're on Linux, you can set the appropriate environment variable via `env OPENSSL_ia32cap=~0x20000000 %command%`.
+If you're on Linux, you can set the appropriate environment variable via `env OPENSSL_ia32cap=0x20000000 %command%`.
**Note:** This issue is not exclusive to Northstar client but also affects the vanilla version, so if you only get it on Northstar there might be a different problem at hand as well. In fact it's not even unique to Titanfall 2 either.