From 23fc9e7b0473f9b78df7ca437c741d46ac20dcb7 Mon Sep 17 00:00:00 2001 From: nmlgc Date: Tue, 9 Jul 2024 04:44:16 +0200 Subject: [PATCH] [Readme] Discover another potential workaround for the TLINK `Loader error` OK, *one* more for modern 32-bit Windows before the support tiers go into effect, bringing this delivery to a nice 69 commits. Completes P0285, funded by [Anonymous] and iruleatgames. --- README.md | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index c0af994a..7b4d2adf 100644 --- a/README.md +++ b/README.md @@ -187,17 +187,21 @@ On 64-bit x86, the build process uses Tup for minimal parallel rebuilds, but all * TLINK fails with `Loader error (0000): Unrecognized Error` on 32-bit Windows ≥Vista - This can be fixed by configuring the NTVDM DPMI driver to be loaded into conventional memory rather than upper memory, by editing `%WINDIR%\System32\autoexec.nt`: + Two known causes: - ```patch - REM Install DPMI support - -LH %SystemRoot%\system32\dosx - +%SystemRoot%\system32\dosx - ``` + * Try configuring the NTVDM DPMI driver to be loaded into conventional memory rather than upper memory, by editing `%WINDIR%\System32\autoexec.nt`: - Requires a reboot after that edit to take effect. + ```patch + REM Install DPMI support + -LH %SystemRoot%\system32\dosx + +%SystemRoot%\system32\dosx + ``` - ([Source](http://oshow.txt-nifty.com/blog/2008/11/loader-error-00.html)) + Requires a reboot after that edit to take effect. + + ([Source](http://oshow.txt-nifty.com/blog/2008/11/loader-error-00.html)) + + * Try building in a regular `cmd.exe` shell instead of PowerShell or Bash. ## Contribution guidelines