Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83 (MC840302); site boring.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!mcvax!boring!jack
From: jack@boring.UUCP
Newsgroups: net.micro.68k,net.micro.16k
Subject: Re: Re: PDP11s vs the micros
Message-ID: <6598@boring.UUCP>
Date: Mon, 26-Aug-85 12:39:46 EDT
Article-I.D.: boring.6598
Posted: Mon Aug 26 12:39:46 1985
Date-Received: Wed, 28-Aug-85 21:16:48 EDT
References: <1617@hao.UUCP> <847@mako.UUCP> <2422@sun.uucp> <223@uthub.UUCP> <5900@utzoo.UUCP>
Reply-To: jack@boring.UUCP (Jack Jansen)
Organization: AMOEBA project, CWI, Amsterdam
Lines: 13
Xref: watmath net.micro.68k:1083 net.micro.16k:376
Apparently-To: rnews@mcvax.LOCAL

In article <5900@utzoo.UUCP> henry@utzoo.UUCP (Henry Spencer) writes:
>
>It should also be possible to get a similar effect by using the SETCFG
>instruction to tell the cpu "no floating point", which will produce a
>trap when the user tries to use floating point.  Save the state and then
>turn floating point on again.  When I asked the local National man about
>this, he said it would work.  Beware that I have *not* tried it on real
>hardware yet.
Well, I didn't try it either, but NS uses the code in their 4.1
release, so I guess it works.
-- 
	Jack Jansen, jack@mcvax.UUCP
	The shell is my oyster.