blakec@pi3.local (Carl D. Blake) (09/14/90)
I have been looking for a floppy disk device driver that would allow you to change the track to track seek rate through the mountlist file. I have never heard of one and have been thinking about writing one myself (if I could ever find the time). However, this seems like something someone would have done a long time ago (seems too useful for words). So perhaps there is a problem with doing this. If anybody knows anything about this, please let me know. One reason I am so interested is that I have a 5 1/4" floppy disk drive out of an old IBM PC that has a much slower track to track seek time (probably 6 ms - I believe that the current trackdisk.device expects the drive to be able to handle 3 ms seek times) and I would like to get it working on my A1000. ============================================================================== Carl D. Blake | My opinions are my own. I do not blakec%tuva.sainet@ccc.nmfecc.gov | represent SAIC in any way. Science Applications International | Tucson, AZ 85711-3796 602-748-7400 ==============================================================================
johnhlee@svax.cs.cornell.edu (Johnny H. Lee) (09/14/90)
In article <30359@nigel.ee.udel.edu> blakec@pi3.local (Carl D. Blake) writes: >I have been looking for a floppy disk device driver that would allow >you to change the track to track seek rate through the mountlist file. [...] >One reason I am so interested is that I have a 5 1/4" floppy disk >drive out of an old IBM PC that has a much slower track to track >seek time (probably 6 ms - I believe that the current trackdisk.device >expects the drive to be able to handle 3 ms seek times) and I would >like to get it working on my A1000. 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. ------------------------------------------------------------------------------- The DiskDoctor threatens the crew! Next time on AmigaDos: The Next Generation. John Lee Internet: johnhlee@cs.cornell.edu The above opinions of those of the user, and not of this machine.
p554mve@mpirbn.mpifr-bonn.mpg.de (Michael van Elst) (09/18/90)
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."
blakec@pi3.local (Carl D. Blake) (09/20/90)
Michael van Elst writes: >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. That's exactly what I wanted to know. However, how do I use TDU_PublicUnit in the mountlist (I'm assuming you can)? ============================================================================== Carl D. Blake | My opinions are my own. I do not blakec%tuva.sainet@ccc.nmfecc.gov | represent SAIC in any way. Science Applications International | Tucson, AZ 85711-3796 602-748-7400 ==============================================================================