[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.
This commit is contained in:
nmlgc 2024-07-09 04:44:16 +02:00
parent 5356d0e5b6
commit 23fc9e7b04
1 changed files with 12 additions and 8 deletions

View File

@ -187,7 +187,9 @@ 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 * 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:
* Try configuring the NTVDM DPMI driver to be loaded into conventional memory rather than upper memory, by editing `%WINDIR%\System32\autoexec.nt`:
```patch ```patch
REM Install DPMI support REM Install DPMI support
@ -199,6 +201,8 @@ On 64-bit x86, the build process uses Tup for minimal parallel rebuilds, but all
([Source](http://oshow.txt-nifty.com/blog/2008/11/loader-error-00.html)) ([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 ## Contribution guidelines
See [`CONTRIBUTING.md`](CONTRIBUTING.md). See [`CONTRIBUTING.md`](CONTRIBUTING.md).