[comp.sys.amiga.misc] 2.0 availability and requirements

jms@vanth.UUCP (Jim Shaffer) (03/18/91)

(I know you're all sick of this, and I'm sick of it too, but when half a
dozen people tell me the same thing I have to consider the possibility that
they're right.)

I heard at a user group meeting today, from quite a few people, that
several dealers (none around here though) have 2.0 ROMs in stock (of course
none of them bought one yet.)

This same group of people tried to tell me that 2.0 will absolutely,
positively require the 1-meg Agnus to run at all.

I don't know where they're getting their information, but does anyone know
FOR SURE if they're right or wrong?

--
*  From the disk of:  | jms@vanth.uucp		     | "Speeding through the
Jim Shaffer, Jr.      | amix.commodore.com!vanth!jms | universe, Thinking is
37 Brook Street       | uunet!cbmvax!amix!vanth!jms  | the best way to travel."
Montgomery, PA 17752  | 72750.2335@compuserve.com    |	  (The Moody Blues)

GHGAQZ4@cc1.kuleuven.ac.be (03/18/91)

They are wrong. I've seen AmigaDOS 2.0 on a normal old Amiga 500 with
NO new agnus (just the old 512K agnus).

   Jorrit Tyberghein

manes@vger.nsu.edu ((Mark D. Manes), Norfolk State University) (03/19/91)

In article <jms.3491@vanth.UUCP>, jms@vanth.UUCP (Jim Shaffer) writes:
> (I know you're all sick of this, and I'm sick of it too, but when half a
> dozen people tell me the same thing I have to consider the possibility that
> they're right.)
> 
> I heard at a user group meeting today, from quite a few people, that
> several dealers (none around here though) have 2.0 ROMs in stock (of course
> none of them bought one yet.)
> 
> This same group of people tried to tell me that 2.0 will absolutely,
> positively require the 1-meg Agnus to run at all.
> 
> I don't know where they're getting their information, but does anyone know
> FOR SURE if they're right or wrong?
> 

They're wrong. :-)  Completely!

> --
> *  From the disk of:  | jms@vanth.uucp		     | "Speeding through the
> Jim Shaffer, Jr.      | amix.commodore.com!vanth!jms | universe, Thinking is
> 37 Brook Street       | uunet!cbmvax!amix!vanth!jms  | the best way to travel."
> Montgomery, PA 17752  | 72750.2335@compuserve.com    |	  (The Moody Blues)

 -mark=
     
 +--------+   ==================================================          
 | \/     |   Mark D. Manes   "Mr. AmigaVision,  The 32 bit guy"
 | /\  \/ |   manes@vger.nsu.edu                                        
 |     /  |   (804) 683-2532    "Make up your own mind! - AMIGA"
 +--------+   ==================================================
                     

jms@vanth.UUCP (Jim Shaffer) (03/20/91)

In article <91077.125218GHGAQZ4@cc1.kuleuven.ac.be> GHGAQZ4@cc1.kuleuven.ac.be writes:

>They are wrong. I've seen AmigaDOS 2.0 on a normal old Amiga 500 with
>NO new agnus (just the old 512K agnus).

That's good to hear.  Does that also mean the ROM is available now?

--
*  From the disk of:  | jms@vanth.uucp		     | "Speeding through the
Jim Shaffer, Jr.      | amix.commodore.com!vanth!jms | universe, Thinking is
37 Brook Street       | uunet!cbmvax!amix!vanth!jms  | the best way to travel."
Montgomery, PA 17752  | 72750.2335@compuserve.com    |	  (The Moody Blues)

rick@tmiuv0.uucp (03/29/91)

In article <jms.3523@vanth.UUCP>, jms@vanth.UUCP (Jim Shaffer) writes:
> In article <91077.125218GHGAQZ4@cc1.kuleuven.ac.be> GHGAQZ4@cc1.kuleuven.ac.be writes:
> 
>>They are wrong. I've seen AmigaDOS 2.0 on a normal old Amiga 500 with
>>NO new agnus (just the old 512K agnus).
> 
> That's good to hear.  Does that also mean the ROM is available now?

As far as I know, as of this date, there is no 2.0 ROM.  Not even in 3000s.
In my 2500, I "ZKick" the 2.0 KickStart from a "kickfile" on the hard disk
(or floppy, if that's what you have).  You tweak up your Startup-Sequence to
allow 1.3.2 or 2.0 bootstraps.

On the 3000, it boots the KickStart off of a special HD partition at startup.
If you want 1.3.2, then you have to turn off the 3000, hold down both mouse
buttons, then turn on the 3000.  Keep holding down the buttons until you get
the KickStart boot screen, which looks sorta like:

        Boot 2.0 from Hard Disk
        Boot 2.0 from Floppy Disk

        Boot 1.3.2 from Hard Disk
        Boot 1.3.2 from Floppy Disk

You click on one of them, and away you go.

.--------------------------------------------------------------------------.
|[- O] Rick Stevens                                                        |
|  ?   EMail: uunet!zardoz!tmiuv0!rick -or- uunet!zardoz!xyclone!sysop     |
|  V               (rick@tmi.com)                (sysop@ssssc.com)         |
|      CIS: 75006,1355 (75006.1355@compuserve.com from Internet)           |
|                                                                          |
|           "If it's stupid and it works, it ain't stupid!"                |
`--------------------------------------------------------------------------'

stevek@amiglynx.UUCP (Steve Krulewitz) (04/07/91)

While you are on the subject of ZKick, how can I make the computer recognise
the HD on startup?  I have a Supra HardCard w/WordSync, and durring boot under
2.0, it plays a little with the HD, but dosent use it - and no hard drive
icons appear on the workbench (not even my auto mounting DH0:).  I think this
may be due to that the drive dosent use MOUNT DH0: or MOUNT DH1:, it has its
own special SUPRAMOUNT 0 (to mount DH1:, DH0: mounts automaticly).  Any help??

  -=+ Steve Krulewitz +=- -=+ Fair Lawn, NJ +=- -=+
                                     UUNET!tronbox!amiglynx!stevek.UUCP +=-

wwarner@en.ecn.purdue.edu (Art Warner) (04/09/91)

In article <stevek.4292@amiglynx.UUCP> stevek@amiglynx.UUCP (Steve Krulewitz) writes:
>While you are on the subject of ZKick, how can I make the computer recognise
>the HD on startup?  I have a Supra HardCard w/WordSync, and durring boot under
>2.0, it plays a little with the HD, but dosent use it - and no hard drive
>icons appear on the workbench (not even my auto mounting DH0:).  I think this
>may be due to that the drive dosent use MOUNT DH0: or MOUNT DH1:, it has its
>own special SUPRAMOUNT 0 (to mount DH1:, DH0: mounts automaticly).  Any help??
>
>  -=+ Steve Krulewitz +=- -=+ Fair Lawn, NJ +=- -=+
>                                     UUNET!tronbox!amiglynx!stevek.UUCP +=-
This may help:
  Make SURE that the partition device names are:
                "WB_2.x" and "WB_1.3"

You can "relabel" it anything you want, but remember that there is a difference
between "device name" and "partition label".  If you don't have the right name
for the device then the bootup WILL NOT recognize either partition for bootup.
I found this out the hard way!
 

-- 
Art Warner
wwarner@en.ecn.purdue.edu
Amiga makes it happen.......IBM, Mac, Sun, and Next make it expensive!