Unreal mode: Difference between revisions
| Line 11: | Line 11: | ||
For efficiency reasons, the [[80286]] and all later x86 processors use the base address, size and other attributes stored in their internal [[segment descriptor]] cache whenever computing effective memory addresses, even in real mode. Contrary to simplified descriptions found in early Intel manuals, a "selector", i.e. a 16-bit "segment number" stored and kept in a (visible to the programmer) "segment register" is not used to calculate addresses. |
For efficiency reasons, the [[80286]] and all later x86 processors use the base address, size and other attributes stored in their internal [[segment descriptor]] cache whenever computing effective memory addresses, even in real mode. Contrary to simplified descriptions found in early Intel manuals, a "selector", i.e. a 16-bit "segment number" stored and kept in a (visible to the programmer) "segment register" is not used to calculate addresses. |
||
Some [[DOS extender]]s use this feature to address the [[high memory]]{{Citation needed|date=February 2011}}. It was used by many [[computer game]]s{{Citation needed|date=February 2011}} in the 1990-to-1995 time frame, because it allowed programmers to address more memory than in real mode (1 [[ |
Some [[DOS extender]]s use this feature to address the [[high memory]]{{Citation needed|date=February 2011}}. It was used by many [[computer game]]s{{Citation needed|date=February 2011}} in the 1990-to-1995 time frame, because it allowed programmers to address more memory than in real mode (1 [[megabyte|MB]] visible, however only first 640 [[kilobyte|KB]] usable on IBM PC-compatible machines), without losing access to the [[DOS]] operating system (which doesn't work in protected mode). After the introduction of [[Windows 95]], unreal mode quickly fell out of favor because programs using it cannot run in the DOS prompt of [[Microsoft Windows]]; they require a "Restart in MS-DOS mode" in Windows 95 and [[Windows 98|98]], and cannot be run at all on [[Windows NT|NT]] and later Windows systems. For those operating systems, an [[emulator]] such as [[DOSBox]] is the only way to run programs designed for unreal mode. Unreal mode is still extensively used by [[BIOS]] code{{Citation needed|date=February 2011}}. In particular the [[System Management Mode]] in Intel 386SL and later processors places the processor in unreal mode. |
||
==Enabling Unreal Mode== |
==Enabling Unreal Mode== |
||
Revision as of 23:25, 17 July 2014
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)
|
| Part of a series on |
| Microprocessor modes for the x86 architecture |
|---|
|
| First supported platform shown in parentheses |
In x86 computing, unreal mode, also big real mode, huge real mode, or flat real mode, is a variant of real mode, in which one or more data segment registers have been loaded with 32-bit addresses and limits. Contrary to its name, it is not a separate addressing mode that the x86-32 and x86-64 processors can operate in. It is used in the 80386 and later x86 processors.
Overview
For efficiency reasons, the 80286 and all later x86 processors use the base address, size and other attributes stored in their internal segment descriptor cache whenever computing effective memory addresses, even in real mode. Contrary to simplified descriptions found in early Intel manuals, a "selector", i.e. a 16-bit "segment number" stored and kept in a (visible to the programmer) "segment register" is not used to calculate addresses.
Some DOS extenders use this feature to address the high memory[citation needed]. It was used by many computer games[citation needed] in the 1990-to-1995 time frame, because it allowed programmers to address more memory than in real mode (1 MB visible, however only first 640 KB usable on IBM PC-compatible machines), without losing access to the DOS operating system (which doesn't work in protected mode). After the introduction of Windows 95, unreal mode quickly fell out of favor because programs using it cannot run in the DOS prompt of Microsoft Windows; they require a "Restart in MS-DOS mode" in Windows 95 and 98, and cannot be run at all on NT and later Windows systems. For those operating systems, an emulator such as DOSBox is the only way to run programs designed for unreal mode. Unreal mode is still extensively used by BIOS code[citation needed]. In particular the System Management Mode in Intel 386SL and later processors places the processor in unreal mode.
Enabling Unreal Mode
To put an 80386 or higher microprocessor into unreal mode, a program must first enter protected mode, find or create a flat descriptor in the GDT or LDT, load some of the data segment registers with the respective protected mode "selector", and then switch back to real mode. After returning to real mode, the processor will continue using the cached descriptors as established in protected mode, thus allowing access to 4 GiB of "extended" memory from real mode.
Huge versus Big real mode
As described above, unreal mode usually involves using one or more data selectors to address data in memory more efficiently. This has been common practice and often referred to as "big" real mode. "Huge" real mode is attained by, in addition, loading the code selector (CS) from a descriptor allowing access to the whole memory and having the 32-bit attribute ("D" bit) set to one. This rarely used "mode" presents some advantages but it is more difficult to set up, since real mode interrupts do not automatically preserve the high sixteen bits of the extended instruction pointer, EIP.