Xref: news-dnh.mv.net comp.os.msdos.djgpp:2089 Path: news-dnh.mv.net!mv!news.sprintlink.net!news.onramp.net!news.tcst.com!op.net!news.fyionline.com!newsfeed.internetmci.com!howland.reston.ans.net!cs.utexas.edu!news.cs.utah.edu!lal.cs.utah.edu!larsen From: larsen AT lal DOT cs DOT utah DOT edu (Steve Larsen) Newsgroups: comp.os.msdos.djgpp Subject: Re: DPMI question Date: 18 Sep 1995 21:52:32 GMT Organization: University of Utah Computer Science Department Lines: 26 References: <4355ve$hj2 AT news DOT mountain DOT net> Reply-To: larsen AT sunset DOT cs DOT utah DOT edu Nntp-Posting-Host: lal.cs.utah.edu To: djgpp AT sun DOT soe DOT clarkson DOT edu Dj-Gateway: from newsgroup comp.os.msdos.djgpp grinch AT access DOT mountain DOT net (ShermPendley) wrote: : > mat AT ardi DOT com (Mat Hostetter) writes: : > >>>>> "Steve" == Steve Larsen writes: : > Steve> P.S. Another quick one. Today while trying to get this : > Steve> working, I was hitting an interesting problem. I was : > Steve> getting a protection fault while loading a segment register : > Steve> (es). Are the segment registers somehow protected while in : > Steve> protected mode? : > : > Yes. Only load legitimate selector values into segment registers. : This deserves some elaboration. Loading an invalid value into a segment : selector shouldn't cause a GP fault. Attempting to access a segment : through a selector which contains an invalid value does cause a fault. Yeah, that is what I thought. However, according to the information presented at the GPF, it is dying on the instruction that loads the segment register. Very strange, I thought. -- Steve Larsen larsen AT sunset DOT cs DOT utah DOT edu I don't like stuff that sucks! B&B