Loading Yarn High-- Some Advantages

From: Howard Schwartz (theo@ncal.verio.com)
Date: Sun, 28 Jun 1998 23:59:02 -0700 (PDT)

I number of subscribers complained that, when they ran the program:

mem <RETURN>

they get no difference in memory when they start yarnx with:

lh yarnx

Loading yarnx high does not change the Amount of memory yarnx uses,
it changes where in memory yarnx is put. If you run mem with the
classify switch thus,

mem /c /p <RETURN>

and you do not load yarnx high, you will see a display something like:

Name Total = Conventional + Upper Memory
-------- ---------------- ---------------- ----------------
MSDOS 16,397 (16K) 16,397 (16K) 0 (0K)
HIMEM 1,168 (1K) 1,168 (1K) 0 (0K)
EMM386 3,120 (3K) 3,120 (3K) 0 (0K)
POWER 80 (0K) 80 (0K) 0 (0K)
COMMAND 3,712 (4K) 3,712 (4K) 0 (0K)
DOSCLIP 10,480 (10K) 10,480 (10K) 0 (0K)
SNIPPER 4,208 (4K) 4,208 (4K) 0 (0K)
YARN 76,896 (75K) 76,896 (75K) 0 (0K)
COMMAND 4,144 (4K) 4,144 (4K) 0 (0K)
POWER 4,672 (5K) 0 (0K) 4,672 (5K)
MOUSE 17,824 (17K) 0 (0K) 17,824 (17K)
NANSI 3,184 (3K) 0 (0K) 3,184 (3K)
TDSK 448 (0K) 0 (0K) 448 (0K)
IFSHLP 3,936 (4K) 0 (0K) 3,936 (4K)
SMARTDRV 29,024 (28K) 0 (0K) 29,024 (28K)
UNDELETE 13,616 (13K) 0 (0K) 13,616 (13K)

Here yarn is shown as residing in low, conventional memory. If you
then load yarnx high, you should notice that yarn is listed as
residing in upper memory (but still taking up about 75K --or whatever).