Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!pa.dec.com!rust.zso.dec.com!shlump.nac.dec.com!sousa.enet.dec.com!bombe.enet.dec.com!moore
From: moore@bombe.enet.dec.com (W. Bruce Moore)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Speed of HardFrame/Q105S (problem) 'Revision' 2
Message-ID: <1990Dec4.172353@bombe.enet.dec.com>
Date: 4 Dec 90 22:38:13 GMT
References: <4120.660191024@lemsys.UUCP>
Sender: newsa@sousa.enet.dec.com
Reply-To: moore@bombe.enet.dec.com (W. Bruce Moore)
Organization: Digital Equipment Corporation, Littleton MA
Lines: 20

In article <4120.660191024@lemsys.UUCP>, clemon@lemsys.UUCP (Craig Lemon)
writes:
|>
|>>> MaxTransfer : 131072 
|>>MaxTransfer = 130560
|>>
|>>You'll be a little safer to drop this down to 130560 to prevent possible
|>>problems.
|>
|>	I will give this a try shortly.  I really don't see how less than
|>1K difference in MaxTransfer can make such a difference.  BTW, the 131072
|>value was a software (RDPrep) default.

The 131072 value is *KNOWN* to cause severe problems!  This was acknowledged
by Microbotics as a bug in the original RDPrep program, later versions have
been
corrected to use the lower value.  Contact Microbotics for an update.
--
    W. Bruce Moore
    Moore@bombe.pa.dec.com