From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: CWSDPMR0: system crash on INVD Date: 28 Mar 2001 18:22:06 GMT Organization: Aachen University of Technology (RWTH) Lines: 23 Message-ID: <99ta4e$r99$1@nets3.rz.RWTH-Aachen.DE> References: <99t5g6$m5r$1 AT murdoch DOT acc DOT Virginia DOT EDU> <99t7j4$7ce$1 AT node17 DOT cwnet DOT frontiernet DOT net> <99t91t$rgg$1 AT murdoch DOT acc DOT Virginia DOT EDU> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 985803726 27945 137.226.32.75 (28 Mar 2001 18:22:06 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 28 Mar 2001 18:22:06 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Clark L. Coleman wrote: > In article <99t7j4$7ce$1 AT node17 DOT cwnet DOT frontiernet DOT net>, > Alexei A. Frounze wrote: [...] >>INVD is a PL#0 instruction and must be invoked only by a OS software, not >>user applications. > I thought that was what CWSDPR0.EXE was all about -- providing access > to such instructions. Not exactly "providing", but rather "allowing" it, in principle. CWSDPR0.exe is a DPMI server that doesn't force the DPMI client (i.e. the DJGPP application) into Ring 3. But for that to work, CWSDPR0.exe itself needs to run at Ring 0. If the DOS environment you're running it in restricts it to Ring 3, there's nothing it can do about that. I.e. I'd suspect your DOS (DrDOS, wasn't it) to be the real culprit, here. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.