From:	Nate Eldredge <neldredge AT hmc DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Rebooting the PC
Date:	26 Sep 2000 10:44:34 -0700
Organization:	InterWorld Communications
Lines:	28
Sender:	nate AT mercury DOT st DOT hmc DOT edu
Message-ID:	<83vgvjavzx.fsf@mercury.st.hmc.edu>
References:	<Pine DOT LNX DOT 4 DOT 21 DOT 0009261821040 DOT 1365-100000 AT goatbeard DOT grendel DOT net>
NNTP-Posting-Host:	mercury.st.hmc.edu
Mime-Version:	1.0
X-Trace:	nntp1.interworld.net 969990275 44034 134.173.57.219 (26 Sep 2000 17:44:35 GMT)
X-Complaints-To:	usenet AT news DOT interworld DOT net
NNTP-Posting-Date:	Tue, 26 Sep 2000 17:44:35 +0000 (UTC)
User-Agent:	Gnus/5.0802 (Gnus v5.8.2) Emacs/20.5
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Kalum Somaratna aka Grendel <kalum AT lintux DOT cx> writes:

> On  26 Sep 2000, Prashant TR decided to enlighten us with,
> 
> > I wrote:
> > 
> > > You can try this one:
> > > 
> > > outportb (0x61, 0xfe);
> > > 
> > > It resets the CPU.
> > 
> > Sorry, there's yet another correction here apart from what Nate has
> > said. The port number is 0x64h, not 0x61h. Sorry again.
> 
> Shouldn't protected mode OS's like windoze trap this and prevent a CPU
> reset hapenning???

Of course they should.  But this would also break all the DOS programs
that tweak the hardware at low levels, so they don't.

Linux does forbid this manner of tomfoolery (except for root, and even
then it takes special measures).

-- 

Nate Eldredge
neldredge AT hmc DOT edu

- Raw text -