Xref: utzoo comp.sys.ibm.pc:28890 comp.sys.amiga:33892
Path: utzoo!attcan!uunet!cs.utexas.edu!sun-barr!rutgers!uwvax!tank!ncar!boulder!unicads!les
From: les@unicads.UUCP (Les Milash)
Newsgroups: comp.sys.ibm.pc,comp.sys.amiga
Subject: Re: OS/2 vs AmigaDOS
Message-ID: <448@unicads.UUCP>
Date: 16 May 89 15:33:30 GMT
References: <2948@rti.UUCP> <6876@cbmvax.UUCP>
Reply-To: les@unicads.UUCP (Les Milash)
Followup-To: comp.sys.ibm.pc
Organization: Unicad  Boulder, CO
Lines: 17

In article <6876@cbmvax.UUCP> daveh@cbmvax.UUCP (Dave Haynie) writes:
>Well, my 68030 Amiga with memory resident C Compilers was getting so
>fast, I didn't have time to[...]
>a beer without wasting any useful time.  For the moment, I've solved this
>problem by [...], which should last me until the 68040.

if this is a widespread problem, i'm fairly sure i could whip up a
"application decellerator" that'd fit between the 68xxx and its socket.
it'd draw a wee bit of 5v, and it'd have a trim-pot to adjust the
doodoo cycle, so you could make your machine arbitrarily slow.

on most machines you can do this in software.  in fact i've got some
rays you could trace for me... i'm trying to animate a ray-traced
grand-canyon fly-thru with kajya-style diffuse reflections.  let's see,
4000000 polygons times 12800 rays times 16 for antialiasing times 30 frames 
a second times 60 seconds a minute...  yeah that should do it.  i'll mail 
you a few floppies and...