Path: utzoo!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!pasteur!ucbvax!kepler.Berkeley.EDU!me128-aw
From: me128-aw@kepler.Berkeley.EDU (me128 student)
Newsgroups: comp.sys.amiga.tech
Subject: Re: quiche-eater questions...
Message-ID: <27418@ucbvax.BERKELEY.EDU>
Date: 7 Jan 89 22:31:54 GMT
References: <780003@hpcilzb.HP.COM>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: me128-aw@kepler.Berkeley.EDU (me128 student)
Organization: University of California, Berkeley
Lines: 32

In article <780003@hpcilzb.HP.COM> tedj@hpcilzb.HP.COM (Ted Johnson) writes:
>These are probably quiche-eater questions, but I'm a Mac-a-phile
>helping out a friend who has an Amiga (but no access to Usenet)...
>
>Question #1:  can an Amiga 2000 be made to automatically boot from
>              internal hard disk? 
>

Yes, it can be done, but you need 1.3 Roms and an autobooting controller
like a 2090A or GVP hardcard.

>Question #2:  what is the magical incantantation you have to put in your
>              startup-sequence script to get it to look at the "Preference"
>              settings?  We changed the colors, but it insisted on coming up
>              in the old colors.  When we fired up Preference and choose the
>              "old colors" (or whatever it was called), it used our new color
>              scheme.

When you boot up, the system looks for a file devs:system-configuration, where
devs: is a logical which defaults to the devs/ directory on your boot disk
upon boot-up.  The problem is, that your startup-script probably re-assigns
devs: to stand for the devs/ directory on the hard disk.  Since preferences
writes to the current devs:, your changes go to the hard disk and are never
seen at boot-up.  What you need to do is type in the following at a cli:

  Copy devs:system-configuration df0:devs

to copy the changed config file to your boot disk.  Alternately, the 1.3
enhancement package has an icon you can double-click to do just this.  Make 
sure your boot disk is in df0:, however

-Vince Lee