Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!unido!mpirbn!p554mve
From: p554mve@mpirbn.mpifr-bonn.mpg.de (Michael van Elst)
Newsgroups: comp.sys.amiga
Subject: Re: Track to Track seek times on floppy disk device driver.
Message-ID: <1172@mpirbn.mpifr-bonn.mpg.de>
Date: 18 Sep 90 14:36:01 GMT
References: <30359@nigel.ee.udel.edu> <45823@cornell.UUCP>
Reply-To: p554mve@mpirbn.UUCP (Michael van Elst)
Organization: Max-Planck-Institut fuer Radioastronomie, Bonn
Lines: 18

In article <45823@cornell.UUCP> johnhlee@svax.cs.cornell.edu (Johnny H. Lee) writes:
>Hmmm.  I'm not sure you need to do this.  I have a 360K IBM-compatible
>5-1/4" hooked up to my system right now (a Qumetrak 142) and it has
>track-to-track seek time of about 12 ms.  As long as the interface board
>does the 5-1/4" ID when the system queries the drive, I think that the
>trackdisk.device will automatically use a slower seek time.

That's true. The trackdisk.device will select 3ms for 3-1/2" drives
and 6ms for 5-1/4" drives. Nevertheless, under V1.2 and V1.3 of kickstart
you can change these parameters in the TDU_PublicUnit (see devices/trackdisk.h
for reference). I hope there's a hook for that in V2.0 too.

Regards,
-- 
Michael van Elst
UUCP:     universe!local-cluster!milky-way!sol!earth!uunet!unido!mpirbn!p554mve
Internet: p554mve@mpirbn.mpifr-bonn.mpg.de
                                "A potential Snark may lurk in every tree."