Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!orion.oac.uci.edu!ucivax!ucla-cs!ewa.cs.ucla.edu!michael
From: michael@ewa.cs.ucla.edu (michael gersten)
Newsgroups: comp.sys.amiga.applications
Subject: Re: Kickstart 2.0
Message-ID: <1991May7.015249.27337@cs.ucla.edu>
Date: 7 May 91 01:52:49 GMT
References: <21070@cbmvax.commodore.com> <1991May1.200820.46421@vaxb.acs.unt.edu>
Sender: usenet@cs.ucla.edu (Mr. News Himself)
Organization: UCLA Computer Science Department
Lines: 38
Nntp-Posting-Host: ewa.cs.ucla.edu

In article <1991May1.200820.46421@vaxb.acs.unt.edu> wright%etsuvax2@ricevm1.rice.edu writes:
>Yes, there are ways to run 2.0 on a machine without an MMU, but not with very
>much stability.  One wild program and your Kickstart is trashed.  Not a good

Really? Lets take a look at that.

I used to use RAD:. I have used VD0: for a long time.

I have never had VD0: wiped out by a wild program. I've lost
my clock a couple of times. I've even had to reboot to
play some games, and VD0: was still there later when
I came back. I've had my screen go kapui. I've gotton
machine lock ups with nothing working.

The only time that VD0 goes away on me is when I say
deleteramdisk or power off.

RAD: was almost as reliable as this -- the 1.3
double reboot bug lost it a few times, it got
wiped by a runaway program once. Incompatibilities
with two other programs made me stop using it.
(I hope these have been fixed by now--one was
aztec C 3.6, the other was word perfect, about 2
years old at this point.)

The point? Both VD0 and RAD use a simple feature of CHECKSUMS
to insure that the data hasn't changed. Why not just have the
RAM version do a checksum of itself, and if it finds it different,
go back to the default kickstart? (I think the kickstart code
does this already, I know that my old 1000 would checksum kickstart
at each reboot).

This is plenty of stability. Let me put it to you very simple.
Either I get 2.0 in RAM legally, or illegally.

I've never liked the idea of a ROM'd O/S. I like kickstart.

		Michael