@@ -28,7 +28,7 @@ Nasm works different with this files. So, I strongly advise to use
2828
2929# RLINK
3030
31- RLINK support EMS/XMS memory or can work with temporary files .
31+ RLINK can generate huge files. To speed up RLINK - point your TMP/TEMP directory to ramdrive .
3232So, don't be confused with dos 16-bit application - RLINK known how to handle more then 64kb and 640kb :).
3333
3434## Supported output formats
@@ -54,26 +54,6 @@ If you need viewer for RDF, please visit to https://github.com/DosWorld/objview
5454
5555"Make" utility available at https://github.com/DosWorld/smallmake
5656
57- ## Memory usage
58-
59- Memory using strategy could be changed with /emem=val parameter:
60-
61- | /emem | Memory used (per one file) |
62- | :-----:| :-------------------------------------------------------|
63- | 0 | Use temporary files, 16k buffer in conventional memory |
64- | 1 | Use temp files, 16k buffer + 256k cache in EMS/XMS |
65- | 2 | No temp files, binary image will be build in EMS/XMS |
66-
67- by default: emem is 1
68-
69- RLink will use many temporary files in process (1 for code segment, 1 for
70- data segment, one more - for relocation data and header, etc).
71-
72- EMS/XMS have restriction - 64mb per one handler, RLink will allocate
73- multiple handlers for one file, so 64mb is not a limit for binary image.
74-
75- Place for temporary files could be configured via TEMP, TMP env variables.
76-
7757# How to use
7858
7959See MAKEFILE in TEST directory.
0 commit comments