Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!gatech!rutgers!ucsd!orion.cf.uci.edu!oberon!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga.tech
Subject: Re: A2090 SCSI vs Video contention - here we go again!
Message-ID: <14154@oberon.USC.EDU>
Date: 19 Dec 88 19:38:55 GMT
References: <2453@antique.UUCP| <5496@cbmvax.UUCP> <14146@oberon.USC.EDU> <5524@cbmvax.UUCP>
Sender: news@oberon.USC.EDU
Reply-To: papa@pollux.usc.edu (Marco Papa)
Organization: Felsina Software, Los Angeles, CA
Lines: 20

In article <5524@cbmvax.UUCP| andy@cbmvax.UUCP (Andy Finkel) writes:
|In article <14146@oberon.USC.EDU| papa@pollux.usc.edu (Marco Papa) writes:
||My question is as follows:  what if you've one of the "autoboot" devices
||like the GVP board or the A2090A? With the GVP one can have a single
||partition, ALL of it FFS and still boot from it.  So the FFS is up 
||even before FastMemFirst can ever be run.
|
|There are 2 possible solutions to this:
|
|1) Set your GVP hard disk to automatically add a minimum number
|of buffers when it fire up; 5 would be about right.  Then
|add the rest of the buffers via your startup-sequence (Addbuffers).

I guess I should do AddBuffers FFS: AFTER FastMemFirst, right?

-- Marco Papa 'Doc'
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
uucp:...!pollux!papa       BIX:papa       ARPAnet:pollux!papa@oberon.usc.edu
 "There's Alpha, Beta, Gamma and Diga!" -- Leo Schwab [quoting Rick Unland]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=