lOADHIGH - Misplaced Pages

This is an old revision of this page, as edited by Wtshymanski (talk | contribs) at 21:07, 14 March 2011 (copyeidt; not an 8088 limitation, but an IBM PC limitation). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Revision as of 21:07, 14 March 2011 by Wtshymanski (talk | contribs) (copyeidt; not an 8088 limitation, but an IBM PC limitation)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

This article does not cite any sources. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "LOADHIGH" – news · newspapers · books · scholar · JSTOR (March 2010) (Learn how and when to remove this message)

Loadhigh (abbreviated 'lh') is an internal MS-DOS command that is used to load a program into the upper memory area (UMA) instead of conventional memory. Due to design of the IBM PC MS-DOS suffered from what was known as the 640 KiB barrier. The size of this memory area, known as conventional memory was fixed and independent of the amount of system memory actually installed. Later, as DOS-based configurations came to be equipped with more and more memory, various schemas were developed to support extra memory (see also XMS, EMS and DOS extender), but conventional memory was still an issue due to compatibility issues. It was a scarce resource as many applications demanded a large part of this basic memory fragment at run-time. Therefore, it was often necessary to move some TSR programs like the mouse driver or the SMARTDRV disk caching driver prior to running a memory-hungry application. This was achieved by using loadhigh called with the program's name as the parameter.

The equivalent of loadhigh for device drivers is DEVICEHIGH (usable only within CONFIG.SYS).

After the introduction of modern operating systems (stemming from MS-DOS) which run in protected mode, support an unsegmented (flat) memory model and do not ultimately suffer from the 640 kB constraint, loadhigh and other methods of freeing conventional memory have become obsolete and this command is no longer recognized within the command interpreter of newer Windows operating systems.

See also