Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!usc!apple!altos!altos86!rcollins From: rcollins@altos86.Altos.COM (Robert Collins) Newsgroups: comp.os.msdos.programmer Subject: Re: 80286 protected mode programming Message-ID: <3803@altos86.Altos.COM> Date: 9 Aug 90 15:35:33 GMT References: <1990Jul31.024249.1328@water.waterloo.edu> Reply-To: rcollins@altos86.UUCP (Robert Collins) Distribution: comp Organization: Altos Computer Systems, San Jose, CA Lines: 26 In article <1990Jul31.024249.1328@water.waterloo.edu> nmouawad@water.waterloo.edu (Naji Mouawad) writes: >In article bianco@cs.odu.edu >(David J. Bianco) writes: > >>How does one kick the 286 chip into protected mode? I'm using TC++ (but >>only, as of yet, in TC mode, not TC++ mode), and was hoping to get out >>of this segmented architecture via the protected mode. Since I dont >>really care if my program will run in the background of a multitasker >>or anything, I thought this would be a good solution. > Don't try and use the '286 to circumvent the necessity for segmentation. The '286 in protected mode enforces segmentation much stronger than in real mode. I would recommend getting a good book that discusses protected mode, and read it. I just finished writing two magazine articles on how to enter and leave protected mode, along with lots of undocumented goodies about the '286 and '386. At this point I don't know if they will be accepted for publication (as each article is 8-10 pages, and includes 20 or more pages of figures and source code). If the articles are accepted, you can read them in TECH SPECIALIST in a couple of months. If they are rejected, then I will post them to the net. Robert Collins