| Revision as of 13:21, 15 September 2011 editMatthiaspaul (talk | contribs)Autopatrolled, Extended confirmed users, Page movers, New page reviewers, Pending changes reviewers, Rollbackers, Template editors137,490 editsm Moved into sub-category← Previous edit | Revision as of 02:03, 8 April 2012 edit undoArx Fortis (talk | contribs)Extended confirmed users, Pending changes reviewers6,751 editsm punctuationNext edit → | ||
| Line 1: | Line 1: | ||
| {{Unreferenced|date=March 2010}} | {{Unreferenced|date=March 2010}} | ||
| {{lowercase}} | {{lowercase}} | ||
| '''Loadhigh''' (abbreviated 'lh') is an internal ] ] that is used to load a program into the ] (UMA) instead of ]. Due to design of the ] MS-DOS suffered from what was known as the ]. The size of this memory area, known as ] was fixed and independent of the amount of system memory actually installed. Various schemes were developed to support extra memory (see also ], ] and ]), 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 ] programs like the ] driver or the ] 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. | '''Loadhigh''' (abbreviated 'lh') is an internal ] ] that is used to load a program into the ] (UMA) instead of ]. Due to design of the ], MS-DOS suffered from what was known as the ]. The size of this memory area, known as ] was fixed and independent of the amount of system memory actually installed. Various schemes were developed to support extra memory (see also ], ] and ]), 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 ] programs like the ] driver or the ] 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 ]s is DEVICEHIGH (usable only within ]). | The equivalent of loadhigh for ]s is DEVICEHIGH (usable only within ]). | ||
Revision as of 02:03, 8 April 2012
 | 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. Various schemes 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).
Operating systems other than MS DOS run in protected mode, support an unsegmented (flat) memory model and do not have a 640 kB constraint. Loadhigh and other methods of freeing conventional memory have become obsolete. This command is no longer available in the command interpreter of newer Windows operating systems.
See also
 | This DOS software-related article is a stub. You can help Misplaced Pages by expanding it. |