Re: handling exceptions in msdos

From: Ivan Korotkov (koroNOSPAMtkov2_at_ztelDOT.ru)
Date: 01/03/04 

Date: Sat, 3 Jan 2004 21:33:13 +0000 (UTC)

> In the "realest" possible mode. CPU context is the same as after power-up.

Well, re-reading this post I understood that I expressed myself with
ambiguity. Following a power-up, CPU is not in "true" real mode but the
first JMP FAR instruction in BIOS resets CS.Limit to its correct value and
when CPU executes our code at rm_handler, it's already "in the realest
possible mode".

Ivan

Relevant Pages

  • Re: First instruction executed after RESET and A20 cache consistency
    ... > On CPU reset the descriptor cache for CS is loaded with 0xffff0000 and ... > normal real mode addressing rules will apply. ... Does the MB know that CPU got a reset? ... As I were steeping thru BIOS loader, it first turned A20 on - so it were off ...
    (comp.arch)
  • Re: First instruction executed after RESET and A20 cache consistency
    ... But in the case where a system did not care about real mode, ... > Does the MB know that CPU got a reset? ... > As I were steeping thru BIOS loader, it first turned A20 on - so it were off ...
    (comp.arch)
  • Re: PUSH instruction family
    ... and not in real mode. ... After running MASM all segment limits were 00000FFFFh excepting DS,ES ... thing I found was that either the BIOS or the CPU on the test machine ...
    (alt.lang.asm)
  • Re: handling exceptions in msdos
    ... Following a power-up, CPU is not in "true" real mode but the ... first JMP FAR instruction in BIOS resets CS.Limit to its correct value and ...
    (comp.lang.asm.x86)
  • Re: Seeing VERSIONINFO under Vista?
    ... The reasoning, of course, from the CPU designers' POV was that if you were ... and would not /need/ to go back to real mode except for a full ... processor reset, it started up in real mode. ... invalid address and then cause an interrupt the CPU then causes another ...
    (microsoft.public.vc.mfc)