Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!news.cs.indiana.edu!noose.ecn.purdue.edu!en.ecn.purdue.edu!wwarner
From: wwarner@en.ecn.purdue.edu (Art Warner)
Newsgroups: comp.sys.amiga.misc
Subject: Re: Upgrading to 2.03
Message-ID: <1991Jun5.062648.2839@en.ecn.purdue.edu>
Date: 5 Jun 91 06:26:48 GMT
Article-I.D.: en.1991Jun5.062648.2839
References: <1991Jun1.023836.8994@msuinfo.cl.msu.edu>
Organization: Purdue University Engineering Computer Network
Lines: 22

In article <1991Jun1.023836.8994@msuinfo.cl.msu.edu> yurkon@CYCVAX.NSCL.MSU.EDU writes:
>Upgrading up through 2.02 seemed painless, but now I've seemed to have forgotten
>how to upgrade now.   2.x -> xx seems to only update kickstart.  I'm reluctant
>to run installHD.  I don't wish to have to reinstall almost 200 megs of
>harddisk space.  It looks like it'll change my partions if I run it.  Is it ok?
>
>	John
Be VERY careful when doing this upgrade.  You are correct in saying that
"update 2.x" is the only way to upgrade the kickstart file in the "devs"
drawer.  The thing that is not mentioned anywhere is that if you continue after
updating your kickstart, it then copies ALL the new files OVER your old ones.
Now, for many people that may not be a problem.  BUT, if any of you have
modified your startup-sequence (to name just one) then you'll be UNPLEASANTLY
surprised to find that your modified files have been replaced!  

I now leave startup-sequence alone and modify just user-startup.  The update
program leaves that file alone!  Thank God!

-- 
William "Art" Warner                 //\
CBM Amiga Student Rep.             \X/--\miga makes it happen..........
wwarner@en.ecn.purdue.edu          IBM, Apple, Sun, & Next make it expensive!