Xref: utzoo comp.sys.amiga.tech:7555 comp.sys.amiga:41540
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!agate!ucbvax!ucdavis!iris!rogers
From: rogers@iris.ucdavis.edu (Brewski Rogers)
Newsgroups: comp.sys.amiga.tech,comp.sys.amiga
Subject: More dos questions
Keywords: dos,sod,dso,osd
Message-ID: <5599@ucdavis.ucdavis.edu>
Date: 13 Oct 89 01:58:53 GMT
Sender: uucp@ucdavis.ucdavis.edu
Reply-To: rogers@iris.ucdavis.edu (Brewski Rogers)
Organization: U.C. Davis - Department of Electrical Engineering and Computer Science (moo!)
Lines: 25

Hi, I'd like to thank everyone who responded to my earlier question on
speeding up file reading. Now I have a few more:

1.	How exactly is Seek() implemented? If I Seek 200K forward, will dos
read through all the data until it gets there, or does it have some way of 
figuring out where to move the head to? If it does have a way of knowing
where to move the head to, is the information easily found, or does it
have to move the head to find it?

2.	What are the effects of Read()ing small chunks? (say 2-6K) will
AddBuffers speed things like this up? (assuming more than one chunk is
on the same track.)

3.	Are there any disk optimizers that will write a file so it can
be read with maximum efficiency? I know BAD optimizes for directory
scanning or info files, but that's not what I need. (maybe I could
rename my big data file to .info and BAD would optimize it? :-)

helpful replies are eagerly awaited!

------------------------------------------------------          Quantum _\/_
2727 Eel                   Bruce (6502 RULES!) Rogers        |\  Duck  ( 0 0)
Davis, Ca 95616            Quantum Duck Software,           |\ \______/ / \\\
916-756-2684               rogers@iris.ucdavis.edu         |\ <  <     |   \/
"It's better to be the real thing than the right thing."     \________/  Quark!