Skip to content

Commit

Permalink
Add notinghardware->Windows section, redesigned previously added images
Browse files Browse the repository at this point in the history
  • Loading branch information
tammo03 committed Sep 22, 2024
1 parent 97fb554 commit 930d776
Show file tree
Hide file tree
Showing 15 changed files with 179 additions and 365 deletions.
24 changes: 12 additions & 12 deletions _configplist/02-AMD/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,30 +50,30 @@ Maybe you've already noticed that there isn't a single Mac with an AMD CPU. Ther
[AMDVanillaPatches](https://github.com/corpnewt/AMDVanillaPatches/) allows us to merge the required kernel patches without problems. It's pretty self-explanatory. However, you should read the ReadMe of the [kernel patches](https://github.com/AMD-OSX/AMD_Vanilla) to understand what is actually happening.
First of all, we have to get the tool itself. We can simply download the main branch or clone the repository.

<p align="center">
<img width="1583" height="1279" src="/assets/KernelPatches/AMDVanillaPatchesRepo.png">
</p>
<div style="text-align: center;" markdown="1">
[![AMDVanillaPatchesRepository](/assets/KernelPatches/AMDVanillaPatchesRepo.png)](/assets/KernelPatches/AMDVanillaPatchesRepo.png)
</div>

Once we have the repository (you may need to unzip it), we should see the following files.

<p align="center">
<img width="533" height="340" src="/assets/KernelPatches/AMDVanillaPatchesRepoFiles.png">
</p>
<div style="text-align: center;" markdown="1">
[![AMDVanillaPatchesRepository](/assets/KernelPatches/AMDVanillaPatchesRepoFiles.png)](/assets/KernelPatches/AMDVanillaPatchesRepoFiles.png)
</div>

You can now choose the appropriate script depending on your platform (Windows users should choose the ``.bat`` file).

We should now be greeted something like this.

<p align="center">
<img width="697" height="483" src="/assets/KernelPatches/AMDVanillaPatches.command.png">
</p>
<div style="text-align: center;" markdown="1">
[![AMDVanillaPatchesRepository](/assets/KernelPatches/AMDVanillaPatches.command.png)](/assets/KernelPatches/AMDVanillaPatches.command.png)
</div>

First we want to select option 1). We then choose option 2) and drag and drop our config.plist into it. We then confirm it with enter.
After that we choose option 3) - Here we have to enter the number of CPU cores of our target system (**NOT** threads).

<p align="center">
<img width="697" height="483" src="/assets/KernelPatches/CPUCores.png">
</p>
<div style="text-align: center;" markdown="1">
<[![AMDVanillaPatchesRepository](/assets/KernelPatches/CPUCores.png)](/assets/KernelPatches/CPUCores.png)
</div>

Now we can close the program and continue with the platform-specific configuration.

Expand Down
31 changes: 16 additions & 15 deletions _configplist/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,15 +60,15 @@ Do **NOT** use configurators. Every conceivable reason, apart from laziness, spe
## Downloading ProperTree
For those who want to use ProperTree, let's download it now. First of all, we have to get the tool itself. We can simply download the main branch or clone the repository.

<p align="center">
<img width="1583" height="1279" src="/assets/ProperTree/ProperTreeRepo.png">
</p>
<div style="text-align: center;" markdown="1">
[![Repository](/assets/ProperTree/ProperTreeRepo.png)](/assets/ProperTree/ProperTreeRepo.png)
</div>

Once we have downloaded ProperTree (and unpacked it if necessary), we will be greeted with the following files.

<p align="center">
<img width="492" height="340" src="/assets/ProperTree/ProperTreeFiles.png">
</p>
<div style="text-align: center;" markdown="1">
[![Files](/assets/ProperTree/ProperTreeFiles.png)](/assets/ProperTree/ProperTreeFiles.png)
</div>

We can now select the script according to our platform. Windows users should choose the ``.bat`` file, Mac users should choose the ``.command`` file. Users on all platforms, including Linux, can also use the ``.py`` file instead.

Expand All @@ -77,25 +77,26 @@ The difference between ``ProperTree.bat`` and ``ProperTreeQuiet.bat`` is that no

When you open ProperTree, you will be greeted with the following window:

<p align="center">
<img width="842" height="620" src="/assets/ProperTree/ProperTreeUntitled1.png">
</p>
<div style="text-align: center;" markdown="1">
[![Blank file](/assets/ProperTree/ProperTreeUntitled1.png)](/assets/ProperTree/ProperTreeUntitled1.png)
</div>

Now we want to open our previously renamed ``config.plist`` file. From now on we will just call it “plist”. You can do that by pressing ``Cmd/Ctrl+O`` and selecting the file. If you did it correctly, it should look something like this:

<p align="center">
<img width="1172" height="720" src="/assets/ProperTree/ProperTreePlist.png">
</p>
<div style="text-align: center;" markdown="1">
[![config.plist](/assets/ProperTree/ProperTreePlist.png)](/assets/ProperTree/ProperTreePlist.png)
</div>

{: .note }
You can remove the first 4 warning entries. They don't matter, we don't need them and they just don't look nice - Still, it is purely optional.

## Taking a snapshot
CorpNewts [OCSnapshot](https://github.com/corpnewt/OCSnapshot) is able to transfer the structure of your EFI folder into your config.plist. The OCSnapshot function is already integrated in ProperTree. All you have to do is open ProperTree, press ``Ctrl+R`` (or ``Cmd+R``) and select the ``OC`` folder. However, when you take a snapshot for the first time, it is highly recommended to take a so-called "clean snapshot". To do this, press ``Ctrl/Cmd+Shift+R`` and select the ``OC`` folder.

<p align="center">
<img width="310" height="418" src="/assets/ProperTree/ProperTreeSnapshot.png">
</p>
<div style="text-align: center;" markdown="1">
[![config.plist](/assets/ProperTree/ProperTreeSnapshot.png)](/assets/ProperTree/ProperTreeSnapshot.png)
</div>


Explained in more detail:
**OC Snapshot** updates the current values in ``ACPI -> Add``, ``Kernel -> Add``, ``Misc -> Tools``, and ``UEFI -> Drivers`` by only adding or removing entries as needed. **OC Clean Snapshot** clears these four sections completely and adds all entries from scratch.
Expand Down
35 changes: 0 additions & 35 deletions _notinghardware/01-Introduction/01-Windows/index.md

This file was deleted.

35 changes: 0 additions & 35 deletions _notinghardware/01-Introduction/02-Linux/index.md

This file was deleted.

76 changes: 76 additions & 0 deletions _notinghardware/02-Windows/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
---
layout: default
title: Windows
description: Getting to know your hardware on MS Windows
nav_order: 1
has_children: true
has_toc: false
---

<style>
.navigation-container {
display: flex;
justify-content: space-between;
align-items: center;
width: 100%;
}

.nav-button {
margin: 10px;
}

.windows-next-button-container {
text-align: right;
}

.windows-next-button {
margin: 10px;
top: 0px;
bottom: 0px;
left: 0px;
right: 0px;
}
</style>

<p align="center">
<img width="650" height="200" src="../../../assets/Header-KnowYourHardware.png">
</p>

<h2 align="center">Get ready to keep track of your info!</h2>
<br>

## What are we looking for?

Start by verifying that your CPU, motherboard, and GPU are supported by macOS. It’s essential to check that your storage devices, such as NVMe drives, are recognized and perform well with macOS.
Ensuring compatibility with network and audio components is also important for a smooth experience.
In many cases it still makes sense to check how old your firmware is.

## Gathering HWInfo64

In order to get the most information from our system, we want to use [HWiNFO64](https://www.hwinfo.com/download/). It's up to you if you want to get the installer or the portable version.
Once we downloaded HWiNFO64, we can open the program.

<div style="text-align: center;" markdown="1">
[![HWiNFO64 Summary](/assets/HWiNFO64/Summary.png)](/assets/HWiNFO64/Summary.png)
</div>

Now that we see the summary, we can check whether our hardware is supported. Please write down:
- The CPU model and codename
- The GPU model and codename
- Your chipset and BIOS date
- The models of your drives at the bottom right

After that we want to find out the Ethernet controller and, if you have one, the WiFi controller.
To do this, we look at the extended information from HWiNFO. Here we see the Audio and Network tabs.

<div style="text-align: center;" markdown="1">
[![HWiNFO64 Extended](/assets/HWiNFO64/Extended.png)](/assets/HWiNFO64/Extended.png)
</div>

<!---
To be swapped out with a real screenshot
--->

As we can see, this Ethernet controller is called Realtek RTL8125. The WLAN chip, on the other hand, is a Broadcom BRCM4360CD.

Now that we've written that down, we can now go ahead and see if the hardware is supported.
48 changes: 48 additions & 0 deletions _notinghardware/03-Linux/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,48 @@
---
layout: default
title: Linux
description: Getting to know your hardware on Linux
nav_order: 1
has_children: true
has_toc: false
---

<style>
.navigation-container {
display: flex;
justify-content: space-between;
align-items: center;
width: 100%;
}

.nav-button {
margin: 10px;
}

.windows-next-button-container {
text-align: right;
}

.windows-next-button {
margin: 10px;
top: 0px;
bottom: 0px;
left: 0px;
right: 0px;
}
</style>

<p align="center">
<img width="650" height="200" src="../../../assets/Header-KnowYourHardware.png">
</p>


<h2 align="center">
<br>

<div class="navigation-container">
<a class="nav-button" href="../../../docs/01-WelcomeArea/05-Instructs.html">&larr; Back Page</a>
<a class="nav-button" href="../02-Linux/index/">Linux &rarr;</a>
</div>
<br>
</h2>
36 changes: 0 additions & 36 deletions _notinghardware/08-BIOS/01-Intel/01-Placeholder.md

This file was deleted.

34 changes: 0 additions & 34 deletions _notinghardware/08-BIOS/01-Intel/index.md

This file was deleted.

Loading

0 comments on commit 930d776

Please sign in to comment.