Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!mcvax!unido!sns!space
From: space@sns.UUCP (Lars Soltau)
Newsgroups: comp.sys.amiga
Subject: Re: A HD controller review
Summary: Some dirty tricks
Message-ID: <48@sns.UUCP>
Date: 28 Oct 88 22:40:56 GMT
Article-I.D.: sns.48
References: <8810201315.AA19782@decwrl.dec.com> <42@sns.UUCP> <13363@cisunx.UUCP> <5116@cbmvax.UUCP>
Reply-To: space@sns.UUCP (Lars Soltau)
Organization: Stuttgart Net System, FRG
Lines: 27

In article <5116@cbmvax.UUCP> andy@cbmvax.UUCP (Andy Finkel) writes:
>In article <13363@cisunx.UUCP> ejkst@unix.cis.pittsburgh.edu (Eric J. Kennedy) writes:
>>on the drive must be the old filesystem.  Now, is this really true for
>>all cases or is it only true for the A2090?  I have a C.LTD SCSI
>>controller and hard disk on my A1000, and the FFS appears to work OK,
>
>It's only true if your first partition is automounted.  If you fire
>up your hard disk by using the Mount command (rather than binddrivers)
>you can make the whole thing ffs.

Even with an A2090 you can use your whole HD with FFS, it ain't clean, but it
works:
Prep your HD with the first (automounted) partition using only track 2. Then
set up your Mountlist with the next partition starting at track 2. Format this
partition with FFS.
If you now access the automounted partition, you get a "not a dos disk"
requester. Don't care, just hit cancel. As long as you don't reformat this
partition, the FFS partition is completely safe.
When I still had an ST506 HD, I even had a program written by a friend of mine
called RenameHD which renames all DHX: devices into HDX:, so that I could still
install the FFS partition as DH0:. Now I have an SCSI HD and the automounted
partition is called DH2:, so I don't need RenameHD any longer.
-- 
Lars Soltau	UUCP: ...uunet!unido!sns!space		BIX: -- no bucks --

Here's looking at you, kid!
		-- the Medusa