Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!agate!shelby!neon!pescadero.Stanford.EDU!philip
From: philip@pescadero.Stanford.EDU (Philip Machanick)
Newsgroups: comp.sys.mac.system
Subject: Re: ROM Disk
Keywords: ROM, Classic, Disk
Message-ID: <1990Nov5.045238.20127@Neon.Stanford.EDU>
Date: 5 Nov 90 04:52:38 GMT
References: <5932@munnari.oz.au>
Sender: news@Neon.Stanford.EDU (USENET News System)
Reply-To: philip@pescadero.stanford.edu
Organization: Computer Science Department, Stanford University
Lines: 21

In article <5932@munnari.oz.au>, iand@mullian.ee.mu.OZ.AU (Ian Robert DOBSON) writes:
|> 
|> Has anybody out there started using the Classic ROM disk as the active system
|> folder?  IMHO, it all sounds fairly useless - if the system folder is in ROM,
|> you wouldn't be able to add INIT's, fonts, DA's, etc. etc. etc.  Would anybody
|> really tolerate this for more than five minutes?  Or is there a way around
|> it that I am overlooking?
|> 
|> How about a ROM disk with hooks to the hard disk, so you can add all those
|> extras that we all need and keep the main System on ROM?
|> 
Some good points here. The whole thing only makes sense if you want a minimal
system capable of switching to a system on a server after booting. Of course,
System 7 is allegedly going to make it easier to handle things like fonts
without requiring installation in the System file, but the system stuff in the
ROM disk isn't version 7.0. Next question: is there some way of configuring
a Classic so it will boot off its ROM disk, look for a server, present a
signon dialog and switch to the System it finds on the server?
-- 
Philip Machanick
philip@pescadero.stanford.edu