Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!mailrus!uflorida!beach.cis.ufl.edu!mjm From: mjm@beach.cis.ufl.edu (Michael Murphy) Newsgroups: comp.sys.amiga Subject: Re: SupraMount and FFS (or mount for that matter) Summary: FastMemFirst after SupraMount Message-ID: <19447@uflorida.cis.ufl.EDU> Date: 29 Nov 88 04:10:06 GMT References: <1773@scolex> <11729@cup.portal.com> <6721@xanth.cs.odu.edu> Sender: news@uflorida.cis.ufl.EDU Reply-To: mjm@beach.cis.ufl.edu (Michael Murphy) Organization: UF CIS Department Lines: 22 In article <6721@xanth.cs.odu.edu> manes@cs.odu.edu (Mark Manes) writes: [quotes of other articles deleted] >Tell me, do you use FastMemFirst? We *HAVE* version 5.1a. It does not work >on our 2000. We have a 30 meg drive, with FastMemFirst, version 5.1a dies a >horrible death. I have a 1000, so this may not be related to you at all, but i have the Supra 4x4 connected to an ST277N, and i do run FastMemFirst, but it's near the end of my startup-sequence, after SupraMount and mount vd0: . It's always been in that position, so i don't know how any other arrangement acts, but this one has never had any problems. When i first connected the stuff up and booted with the Supra disk, i let it do the formatting, and then i modified the startup sequence, moving FastMemFirst and a lot of other stuff to startup-dh0 (although it was after SupraMount in the original startup). I have been booting with this for about a week now. -Michael mjm@beach.cis.ufl.edu