Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!emory!hubcap!ncrcae!ncr-sd!se-sd!cns!dltaylor
From: dltaylor@cns.SanDiego.NCR.COM (Dan Taylor)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: (was RAMSEY) 2nd SCSI controller
Message-ID: <920@cns.SanDiego.NCR.COM>
Date: 26 Apr 91 21:23:19 GMT
References: <20874@cbmvax.commodore.com> <41588@cup.portal.com> <20912@cbmvax.commodore.com> <2554@swrinde.nde.swri.edu>
Organization: NCR Corp. SE-San Diego
Lines: 23

In <2554@swrinde.nde.swri.edu> kent@swrinde.nde.swri.edu (Kent D. Polk) writes:

>While we are talking about multiple controllers, I have a 2090a and a
>new 2091.  I would like for my 2090a to not autoboot, as I would like
>for it to be FFS partitioned without that extra, little, useless OFS
>boot partition that I now have.

>I understand that I need to pull my roms & put a copy of hddisk.device
>in my expansion drawer to accomplish this. What is the latest version
>of it, & how may one obtain a disk-based copy of it?

I wouldn't pull ROMs, just yet.  When you set up the 2091, give a boot
priority just less than the floppy, say 2 or 3.  When you repartition
the 2090, set it up with FFS, and declare it non-bootable.  Personally,
I'd put a VERY small boot partition on it, but with a lower priority
than the 2091, then you can boot it, if the 2091 goes down, or you change
the drive.  You can then recover, or reinstall the 2091, from an HD boot,
rather than floppy.  I have a pair of 2091s, and I have a "WorkBench" on
DH0: and a "BackBench" on BH0:.  Both drives are further partitioned into
"Applications" and DH1: and "MSDOS" on BH1: (this has the support programs
for my A2088, as well as an MS-DOS bootable virtual drive).

Dan Taylor