home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Club Amiga de Montreal - CAM
/
CAM_CD_1.iso
/
files
/
552.lha
/
FO
/
FO.doc.pp
/
FO.doc
Wrap
Text File
|
1991-09-08
|
4KB
|
82 lines
Fabien Campagne
805, Rue des Gentianes
39000 Lons Le Saunier
France
Lons Le Saunier le 31/07/91
FO COPYRIGHT Notice and Doc.
FO is Freeware as I mentioned it in help text. I allow distribution by
Fred Fish in is Library. Other Libraries must obtain authorization from
me. This one will be delivered only if no exaggerate profit is made with
the distribution.
Now the doc:
FO is very simple to use:
ex FO df0: df1: [-w/-c] [-nfo] [-FDir]
1st arg is source disk. 2nd is destination disk.
The both may be equal (this does -NO- slow down optimization).
-w if Workbench optimization is needed.
-c if Cli optimization is needed.
default is -w
The difference between -w & -c is that when -w is selected, data blocks
for *.info files are moved in the area used by management-blocks.
If you use the disk a lot with WB , that mean if you often open the drawer
of the disk (and wait a long time until icons are displayed) you will
appreciate this option.
Else, use -c.
-nfo means fo No Format:
if the disk you want to use for destination has already been formatted
and is still on good AmigaDos format, you can use this option to save
a lot of time ( in fact, less filled is the disk, more time you can
save with -nfo). Don' t select -nfo if you want to clean really
destination disk.
NEVER use -nfo with unformatted disk in destination:
trying to modify the disk later (adding some files or dir) will cause
write errors.
-C will allow FO to perform a test of the dos structure of the source
disk before to optimize. If error(s) is (are) encountered, FO abort.
Obviously, you can use this function only for checking a disk (cntrl C
during "optimizing..." ).The check is not 100% sure because I do not
have implemented tests for:
> link between two Data blocks.
> "dog that bite himself his tail" (or if you prefer:
a block that point to a block that precede himself in the hash chain.)
-FDir:
I included this option as an experiment to see how AmigaDos will react
when the File List Blocks are placed just near the data block they point
to. I thought that this must improve loading time for very long files.
I was wrong : I really does not understand how loading was made. I have
some ideas but my english is too poor to develop them here.
Do Not Use this option unless you use a Fast Dir ( a Dir with smart
buffering routines, not the standard one) with that disk because -FDir
option slow down directory when a disk contains files which size is more
than 35136 bytes (72*488). If you are interested, try TrackMon on a
'optimized' with -FDir disk when you load a big file.
The source is partially included as an example, not totally because
I don't want to see some modifications made to FO without my agreement.
If you think you are able to add some new features, send me modified
code with a good description of what you made for agreement or make your
own optimizer, it' s a question of 2 weeks (a good experience).
Bug Report : I don't think there 's bugs but if you find some, write !.
Just one thing: FO add a '.' after the name of the disk on destination
because modifying the date of last change does not satisfy WB 1.3
which continue thinking disks are the same and then crash the system.
The next version will (may be) include an intuition interface. Don' t
hesitate if you find FO useful to send your contribution : even little
are welcomed and greatly encouraged. My address is on the top of this doc.