Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!olivea!isc-br!ewu!mpierce
From: mpierce@ewu.UUCP (Mathew Pierce)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: NeXT/Amiga Flamage: Get a life.
Message-ID: <1525@ewu.UUCP>
Date: 15 Apr 91 04:17:28 GMT
References: <2802B127.21121@orion.oac.uci.edu> <$8cG!_ko1@cs.psu.edu>
Organization: Eastern Washington Univ. Cheney WA
Lines: 26

In article <$8cG!_ko1@cs.psu.edu>, melling@cs.psu.edu (Michael D Mellinger) writes:
> 
> In article <1991Apr13.155008.28917@sbcs.sunysb.edu> dtiberio@eeserv1.ic.sunysb.edu (David Tiberio) writes:
> 
[stuff deleted for brevity]
> 
>      And all this talk about memory protection....just use a RAD drive (I know
>    you all have it). Or even better, run WB 2.0. It GURUS less and kills
>    tasks instead. Or get SetTask, which lets you kill or freeze tasks!
> 
> What is a RAD drive?  And you can only run WB 2.0 on the A3000.
> 
 RAD drive is a chunk of memory set up as a ramdom access drive (RAD).  The one
included with AmigaDos uses a static size, but will survive reboots and system
crashes.  I use the ASDG RAD which dynamically allocates and deallocates 
memory as it needs it, and also survives the harshest crashes that I have 
been able to produce.  You can configure your startup-sequence to initially
boot from the HD, and perform all warm-boots from the RAD, whch saves much 
time.  I have mine configured to hold my C-compiler, all includes and libs, 
and my editor.  That way when I do something really screwy, the system is back
up in less than 30 seconds, and at the place that I left off before the crash!

And WB2.0 can run on any Amiga with ZKick, but it's only shipped commercially 
on the A3000.  Just wait a little longer, it'll soon be out for >A3000 
officially.
> -Mike