Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!nrl-cmf!ukma!rutgers!att!whuts!homxb!antique!cjp
From: cjp@antique.UUCP (Charles Poirier)
Newsgroups: comp.sys.amiga
Subject: Re: 2090A problem
Summary: prep <= 63 blocks/track?
Message-ID: <2487@antique.UUCP>
Date: 21 Dec 88 22:35:22 GMT
References: <oXefiHy00VsNEE8nlw@andrew.cmu.edu> <2746@hplabsz.HPL.HP.COM> <14164@oberon.USC.EDU> <5541@cbmvax.UUCP>
Reply-To: vax135!cjp (Charles Poirier)
Organization: AT&T Bell Labs, Holmdel, NJ
Lines: 16

In article <5541@cbmvax.UUCP> jesup@cbmvax.UUCP (Randell Jesup) writes:
>get R/W errors.  The trick with unusual drives is to figure out how many
>blocks there are on the drive, then feed prep (and the mountlist) figures
>that add up to the right number of blocks.  Note that doesn't doesn't like
>more than 63 blocks per track currently, so don't tell it you have more
>than that, use heads and cylinders.

I used 2 surfaces, 95 blocks/track, 823 cylinders to prep my Quantum Q280
SCSI drive and prep did not complain.  Am I in for a surprise when I
exceed 63/95 of my disk's capacity?  How would that 63 block limit
express itself if it was going to be a problem?

	Thank you,
-- 
	Charles Poirier   (decvax,ucbvax,mcnc,attmail)!vax135!cjp

   "Docking complete...       Docking complete...       Docking complete..."