Skip to content

Commit

Permalink
Docs: Update Configuration
Browse files Browse the repository at this point in the history
  • Loading branch information
Andrey1970AppleLife authored Oct 26, 2019
1 parent 5c3c1d6 commit 76e0b0c
Show file tree
Hide file tree
Showing 4 changed files with 13 additions and 13 deletions.
Binary file modified Docs/Configuration.pdf
Binary file not shown.
6 changes: 3 additions & 3 deletions Docs/Configuration.tex
Original file line number Diff line number Diff line change
Expand Up @@ -1791,7 +1791,7 @@ \subsection{Properties}\label{miscprops}

Designed to be filled with \texttt{plist\ string} entries containing
absolute UEFI paths to customised bootloaders, for example,
\texttt{\textbackslash EFI\textbackslash Microsoft\textbackslash bootmgfw.efi}
\texttt{\textbackslash EFI\textbackslash Microsoft\textbackslash Boot\textbackslash bootmgfw.efi}
for Microsoft bootloader. This allows unusual boot paths to be automaticlly
discovered by the boot picker. Designwise they are equivalent to predefined blessed path, such as
\texttt{\textbackslash System\textbackslash Library\textbackslash CoreServices\textbackslash boot.efi},
Expand Down Expand Up @@ -3813,7 +3813,7 @@ \subsection{Windows support}\label{troubleshootingwin}
\item MBR (Master Boot Record) installations are legacy and will not be supported.
\item To install Windows, macOS, and OpenCore on the same drive you can specify
Windows bootloader path
(\texttt{\textbackslash EFI\textbackslash Microsoft\textbackslash bootmgfw.efi})
(\texttt{\textbackslash EFI\textbackslash Microsoft\textbackslash Boot\textbackslash bootmgfw.efi})
in \texttt{BlessOverride} section.
\item All the modifications applied (to ACPI, NVRAM, SMBIOS, etc.) are supposed
to be operating system agnostic, i.e. apply equally regardless of the OS booted.
Expand All @@ -3823,7 +3823,7 @@ \subsection{Windows support}\label{troubleshootingwin}
\href{https://github.com/acidanthera/bugtracker/issues/327}{workaround}
for this, it is highly recommend not to rely on it and install properly.
\item Windows may need to be reactivated. To avoid it consider
leaving SystemUUID field empty, so that the original firmware UUID is used. Be warned,
setting SystemUUID to the original firmware UUID. Be warned,
on old firmwares it may be invalid, i.e. not random. In case you still have issues,
consider using HWID or KMS38 license. The nuances of Windows activation are out of the
scope of this document and can be found online.
Expand Down
Binary file modified Docs/Differences/Differences.pdf
Binary file not shown.
20 changes: 10 additions & 10 deletions Docs/Differences/Differences.tex
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
\documentclass[]{article}
%DIF LATEXDIFF DIFFERENCE FILE
%DIF DEL PreviousConfiguration.tex Thu Oct 24 08:31:58 2019
%DIF ADD ../Configuration.tex Thu Oct 24 19:17:41 2019
%DIF DEL PreviousConfiguration.tex Thu Oct 24 09:22:44 2019
%DIF ADD ../Configuration.tex Sat Oct 26 15:45:30 2019

\usepackage{lmodern}
\usepackage{amssymb,amsmath}
Expand Down Expand Up @@ -1862,7 +1862,7 @@ \subsection{Properties}\label{miscprops}

Designed to be filled with \texttt{plist\ string} entries containing
absolute UEFI paths to customised bootloaders, for example,
\texttt{\textbackslash EFI\textbackslash Microsoft\textbackslash bootmgfw.efi}
\texttt{\textbackslash EFI\textbackslash Microsoft\textbackslash \DIFaddbegin \DIFadd{Boot\textbackslash }\DIFaddend bootmgfw.efi}
for Microsoft bootloader. This allows unusual boot paths to be automaticlly
discovered by the boot picker. Designwise they are equivalent to predefined blessed path, such as
\texttt{\textbackslash System\textbackslash Library\textbackslash CoreServices\textbackslash boot.efi},
Expand Down Expand Up @@ -3804,11 +3804,10 @@ \subsection{Quirks Properties}\label{uefiquirkprops}
\textbf{Type}: \texttt{plist\ boolean}\\
\textbf{Failsafe}: \texttt{false}\\
\textbf{Description}: macOS bootloader requires GOP (Graphics Output Protocol)
to be present on console handle. This option will install it if missing\DIFaddbegin \DIFadd{.
}
to be present on console handle. This option will install it if missing.

\item
\texttt{\DIFadd{ReconnectOnResChange}}\\
\DIFaddbegin \texttt{\DIFadd{ReconnectOnResChange}}\\
\textbf{\DIFadd{Type}}\DIFadd{: }\texttt{\DIFadd{plist\ boolean}}\\
\textbf{\DIFadd{Failsafe}}\DIFadd{: }\texttt{\DIFadd{false}}\\
\textbf{\DIFadd{Description}}\DIFadd{: Reconnect console controllers after changing screen resolution.
Expand All @@ -3821,10 +3820,11 @@ \subsection{Quirks Properties}\label{uefiquirkprops}

\emph{\DIFadd{Note}}\DIFadd{: On several boards this logic may result in black screen when launching
OpenCore from Shell and thus it is optional. In versions prior to 0.5.2 this option
was mandatory and not configurable. Please do not use this unless required}\DIFaddend .
was mandatory and not configurable. Please do not use this unless required.
}

\item
\texttt{ReleaseUsbOwnership}\\
\DIFaddend \texttt{ReleaseUsbOwnership}\\
\textbf{Type}: \texttt{plist\ boolean}\\
\textbf{Failsafe}: \texttt{false}\\
\textbf{Description}: Attempt to detach USB controller ownership from
Expand Down Expand Up @@ -3888,7 +3888,7 @@ \subsection{Windows support}\label{troubleshootingwin}
\item MBR (Master Boot Record) installations are legacy and will not be supported.
\item To install Windows, macOS, and OpenCore on the same drive you can specify
Windows bootloader path
(\texttt{\textbackslash EFI\textbackslash Microsoft\textbackslash bootmgfw.efi})
(\texttt{\textbackslash EFI\textbackslash Microsoft\textbackslash \DIFaddbegin \DIFadd{Boot\textbackslash }\DIFaddend bootmgfw.efi})
in \texttt{BlessOverride} section.
\item All the modifications applied (to ACPI, NVRAM, SMBIOS, etc.) are supposed
to be operating system agnostic, i.e. apply equally regardless of the OS booted.
Expand All @@ -3898,7 +3898,7 @@ \subsection{Windows support}\label{troubleshootingwin}
\href{https://github.com/acidanthera/bugtracker/issues/327}{workaround}
for this, it is highly recommend not to rely on it and install properly.
\item Windows may need to be reactivated. To avoid it consider
leaving SystemUUID field empty, so that the original firmware UUID is used. Be warned,
\DIFdelbegin \DIFdel{leaving SystemUUID field empty, so that }\DIFdelend \DIFaddbegin \DIFadd{setting SystemUUID to }\DIFaddend the original firmware UUID\DIFdelbegin \DIFdel{is used}\DIFdelend . Be warned,
on old firmwares it may be invalid, i.e. not random. In case you still have issues,
consider using HWID or KMS38 license. The nuances of Windows activation are out of the
scope of this document and can be found online.
Expand Down

0 comments on commit 76e0b0c

Please sign in to comment.