From c53197d2db1dae76cbfdb0b7b412cd126a820a0b Mon Sep 17 00:00:00 2001 From: "Zed A. Shaw" Date: Sun, 1 Mar 2026 12:15:46 -0500 Subject: [PATCH] Update the instructions. --- README.md | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 9a5b9f5..fd83266 100644 --- a/README.md +++ b/README.md @@ -9,10 +9,24 @@ in the language you choose. The scripts are based on [Chris Titus' Winutil](htt > Microsoft. This does mean though that we have to deal with Microsoft employees doing weird things > with the PATH so please read about `pathfixer.ps1` below. -## How to Use It +## Pre-Work -First, you run the `base.ps1` script to get an initial setup of basic things all other languages -need. This allows you to then install any other languages very quickly: +1. Make sure you are fully updated by running `Check for Updates` from your `START` menu. Hit the + win-key and type `updates` to run that. Do a _full_ update and reboot your machine. +2. Start a new PowerShell by typing `PowerShell` in the `START` menu. +3. Confirm that your `winget` is also upgraded with `winget upgrade --all` in this `PowerShell`. +4. Install `which` to test that your `winget` works and to agree to any licenses: `winget install + which`. +5. Once again, exit `PowerShell`, start a new one, and type: `which`. + +> __WARNING__: These instructions assume that everyone has `winget` by default now. If your computer +> does not then email me at help@learncodethehardway.com so I can find out why. It's suposed to be +> the default now. + +## Installing the Basics + +First, you run the `base.ps1` script in `PowerShell` to get an initial setup of basic things all +other languages need. This allows you to then install any other languages very quickly: ```shell irm https://git.learnjsthehardway.com/learn-code-the-hard-way/lcthw-windows-installers/raw/branch/master/base.ps1 -outfile base.ps1 @@ -28,6 +42,7 @@ reports from WinGet developers regarding the PATH they claim you have to have Ad and create symlinks just to put things in the PATH. Yet, here's 2 lines of PowerShell that does it: ```shell +# DO NOT RUN THIS IT'S ONLY AN EXAMPLE $newPath = $env:PATH + ";$winlibsPath\mingw64\bin" [Environment]::SetEnvironmentVariable("Path", $newPath, "User") ```