Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!pasteur!cory.Berkeley.EDU!navas
From: navas@cory.Berkeley.EDU (David C. Navas)
Newsgroups: comp.sys.amiga.applications
Subject: Re: WorkBench 2.0
Message-ID: <12680@pasteur.Berkeley.EDU>
Date: 11 Apr 91 21:52:08 GMT
References: <20515@cbmvax.commodore.com> <cwN9Z5w164w@graphics.rent.com> <20556@cbmvax.commodore.com>
Sender: news@pasteur.Berkeley.EDU
Reply-To: navas@cory.Berkeley.EDU
Lines: 14

In article <20556@cbmvax.commodore.com> peter@cbmvax.commodore.com (Peter Cherna) writes:
>In article <cwN9Z5w164w@graphics.rent.com> bobl@graphics.rent.com (Bob Lindabury - SysAdm) writes:
>>Well, obviously Peter should know what Workbench 2.0 will require but
>>at the moment it *doesn't* require Kickstart 2.0 in ROM.  The ROM is
>I presume (and hope) you're describing an Amiga 3000.  The question

Actually, even in an A3000, 2.0 needs to be in ROM -- it's just not the 2.0
you eventually end up using.

Something has to access those harddrives to get the OS off!

David Navas                                   navas@cory.berkeley.edu
	2.0 :: "You can't have your cake and eat it too."
Also try c186br@holden, c260-ay@ara and c184-ap@torus