Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!lll-winken!lll-tis!ames!ncar!boulder!sunybcs!rutgers!gatech!gitpyr!dsking
From: dsking@pyr.gatech.EDU ( David King)
Newsgroups: comp.sys.amiga
Subject: Re: GURU!!!
Summary: But first!
Keywords: FFS Pacific-Peripherals First-posting ever
Message-ID: <6647@pyr.gatech.EDU>
Date: 26 Oct 88 00:35:33 GMT
Article-I.D.: pyr.6647
References: <7966@j.cc.purdue.edu> <2837@sugar.uu.net> <8810170648.AA10653@esplanade.csri.toronto.edu> <9790@swan.ulowell.edu> <2933@utah-g
Reply-To: dsking@pyr.UUCP ( David King)
Organization: Georgia Institute of Technology
Lines: 27

In article <74559@sun.uucp> cmcmanis@sun.UUCP (Chuck McManis) writes:
>In article <2933@utah-gr.UUCP>(Jason Leigh) writes:
>>Does anyone know what this guru is?
>>	8700000B.265F48F1
>
>Disk corrupt. This means the file system saw something really ugly on 
>your disk and threw up it's hands. You can fix the problem with a disk
>editor and some patience.

               First, I have a Pacific Peripherals OverDrive and
a Fuji 30 meg disk.  This system is nice except for one minor (major!)
flaw - FFS has problems with it.  I would format a section and not be able
to use it:  executables would be corrupt and crash the disk.  The solution
was mentioned by jdow (thanks!)- use the MaxTransfer option to limit the
controller to only grabing a block at a time.  At first I tried limiting
it to 2048 bytes (4 blocks) and I had problems booting up.  After a random
period of my bootup, Persephone (my Amiga) would give that GURU.  I solved
the problem by lowering the MaxTransfer rate WITHOUT disk munging.  Try 
this first!

	BTW, MaxTransfer expects the maximum number of BYTES it can transfer,
not BLOCKS as the documentation says. 

				Good luck,  
				- David
----
  David King
  dsking@pyr.gatech.edu