Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!cbmvax!cbmehq!babylon!rbabel
From: rbabel@babylon.rmt.sub.org (Ralph Babel)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: GVP 3001 HD-Installation
Message-ID: <05621.AA05621@babylon.rmt.sub.org>
Date: 28 Dec 90 04:10:58 GMT
References: <3802@rwthinf.UUCP>
Reply-To: cbmvax.commodore.com!cbmehq!babylon!rbabel (Ralph Babel)
Lines: 52

In article <3802@rwthinf.UUCP>
helmutn@cip-s02.informatik.rwth-aachen.de (Helmut Neumann) writes:

> Now i have the Kit Version 2.3 and a second HD, a 211 MB
> Rodime. The software works great with Rodime and has no
> problem with the modem anymore.

So far, so good ...

> But the Toshiba still refuses to work with big files.

Don't know the Toshiba, but I have a Seagate that behaves in
a similar way: Sometimes it won't accept two large chunks of
data (say, 256 sectors each) in a row. I assume there must
be a bug somewhere in the drive's firmware.

> Besides the Faaast-Prep-Prog. i found the gvpprepat in the
> gvputils-dir. This software allows to set the maxtransfer.
> I tested some values and found that 100000 is to high and
> 70000 works.

I knew someone might find this useful one day ... :-)

> The only Problem is, that this prep-software limits the
> Buffers to 256

That's more than 128K just for buffers! Do you really want
to waste that much RAM? The RAM-disk would probably be
faster then! You could still use AddBuffers in your
startup-sequence, though.

> and you cannot set the synchronous/asynchronous transfer.

This switch doesn't have any meaning for the AT interface.
Ignore it!

> The questions are, how do i have to set the Jumpers of the
> Toshiba to work correctly as a slave to the Rodime, i
> found a setting that both drives work correctly together,
> but i don't know if its correct ?

Don't worry! If it works, I'd assume it's correct.

> Is it normal that i have to set the Maxtransfer for the
> Toshiba (Conner) or is the drive broken ?

Normally, the driver will split all I/O-requests larger than
128K (256 sectors w/ 512 bytes each, the maximum an AT drive
can handle) into separate AT-requests, so it shouldn't be a
problem. I assume something is wrong with the drive.

Ralph