home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.hardware
- Path: sparky!uunet!sun-barr!ames!haven.umd.edu!darwin.sura.net!jvnc.net!yale.edu!ira.uka.de!math.fu-berlin.de!news.netmbx.de!Germany.EU.net!mcsun!sunic!seunet!enea!tope
- From: tope@enea.se (Tommy Petersson)
- Subject: Re: A3000,1.3,2.0 HELP!!!
- Message-ID: <1992Nov11.164657.2206@enea.se>
- Organization: Enea Data AB
- X-Newsreader: Tin 1.1 PL3
- References: <1dimaeINNqqk@gap.caltech.edu>
- Date: Wed, 11 Nov 1992 16:46:57 GMT
- Lines: 30
-
- jsurace@cco.caltech.edu (Jason A. Surace) writes:
- :
- :
- : Well, basically you're out of luck. Only the early A3000's
- : (like mine) had the option to boot 1.3. This was included
- : because the machines were shipped with a beta version of WB 2.0,
- : which I can certainly testify was very buggy and crashed frequently,
- : and had very little compatability. Once 2.0 was stabilized as
- : 2.04, they were shipped with 2.04 only.
-
- You can, however, use SetCPU and kick in 1.3 (it's on your 2.0
- KickStart disk). Check the script Update_2.x and call th same program
- as it does, but with the parameter 1.3 instead of 2.0. This will
- give you a kickstart file in the devs directory.
-
- By calling SetCPU with parameters KICKROM and devs/kickfile, you will
- kick in 1.3. You can't use the HD in 1.3, though. Make a small script
- that calls SetCPU, give it a project icon with IconX as tool, and you'll
- only need to double-klick this icon to kick 1.3.
-
- I've also heard/read that there's work going on (I beleive by Simon Cope)
- to make better versions of SetCPU (SetA3000 and Rekick) that gives you
- access to the HD as well, but I haven't managed to get hold of the
- programs.
-
- --
- =============================================================================
- Tommy Petersson tope@enea.se Enea Data AB, Sweden
- =============================================================================
-
-