Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!emory!att!linac!mp.cs.niu.edu!ux1.cso.uiuc.edu!midway!gsbsun!valley
From: valley@gsbsun.uchicago.edu (Doug Dougherty)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Protected mode/Real mode switching
Message-ID: <1991May1.131818.27612@midway.uchicago.edu>
Date: 1 May 91 13:18:18 GMT
References: <1991Apr15.160333.8107@msuinfo.cl.msu.edu> <37390009@hpopd.pwd.hp.com> <3199@bimacs.BITNET> <1448@balrog.ctron.com> <281@altos86.Altos.COM>
Sender: news@midway.uchicago.edu (NewsMistress)
Organization: University of Chicago
Lines: 19

rcollins@altos86.Altos.COM (Robert Collins) writes:

>LOADALL is available on both the '286 and '386.  However, it is
>implemented as different op codes on each processor.  '286 LOADALL
>is op code 0F 05, and '386 LOADALL is op code 0F 07.  In the October
>issue of 'TECH SPECIALIST' is an article I wrote discussing LOADALL 
>for both the '286 and '386.  Included in the article is a detailed
>description of the instruction, and source code examples showing how
>to use it on each processor.  Also included is a LOADALL emulation
>TSR written for the '386.  This routine will use '386 LOADALL to
>emulate '286 LOADALL.

>The '486 has LOADALL, but is not accessible via an op code.

Then how, pray tell (given your .signature, this cliche seems appropriate)
is it accessed?  Magic?  (IN/OUT ?)
--

	(Another fine mess brought to you by valley@gsbsun.uchicago.edu)