Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mailrus!csd4.milw.wisc.edu!uakari.primate.wisc.edu!ark1!nap1!asdcds!staatsvr
From: staatsvr@asdcds.cds.wpafb.af.mil (Vern Staats; ASD/SCED;)
Newsgroups: comp.sys.amiga
Subject: Re: Which SCSI interface???
Keywords: Xetec MaxTransfer
Message-ID: <253@nap1.cds.wpafb.af.mil>
Date: 6 Aug 89 16:30:16 GMT
References: <10467@boulder.Colorado.EDU> <795@medsys.UUCP>
Sender: news@nap1.cds.wpafb.af.mil
Reply-To: staatsvr@asdcds.UUCP (Vern Staats)
Organization: US. Air Force, ASD, Wright-Patterson AFB
Lines: 25

In article <795@medsys.UUCP> wendell@medsys.UUCP (bbs amiga user) writes:
>
>Simon, I also asked this question a while back, and in no uncertain terms
>was recommended away from the Xetec controller. Seems it dies on very large
>program loads. The fix is to make the Max Transfer value something like
>128K, so the drive has to load larger files in 2 or more requests. From
>what I've gathered, this fix would have to be run every time you boot up
>and is not a good fix at that. 
>--
>Wendell Dingus
>UUCP: uunet!medsys!wendell

MaxTransfer is normally set in the MountList.  Controllers using Rigid Disk
Blocks (RDB) (like Xetec and HardFrame) save mountlist type info on special
blocks on the harddrive and ignore the mountlist.  On these controllers, you
specify MaxTransfer once, when editing partitions and then forget about it.
You do not need to run a fix every time you boot.  I have heard of a problem
with multitasking while downloading files but have not been able to duplicate
it yet.  The controller's speed is mediocre -- just over 300K/s reads, using a
fast harddrive.

Boolean orthogonal(char *my_opinions, char *employer_opinions)  {return(TRUE);}
INET:  staatsvr@asd.wpafb.af.mil                          ///    Honey, I
UUCP:  nap1!asd!staatsvr                              \\\///   dereferenced
Vern Staats, ASD/SCED, WPAFB OH 45433, 513-255-2714    \XX/      the kids