Xref: utzoo comp.sys.amiga.applications:629 comp.sys.amiga.misc:2556
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!news.cs.indiana.edu!widener!netnews.upenn.edu!msuinfo!convex.cl.msu.edu!jap
From: jap@convex.cl.msu.edu (Joe Porkka)
Newsgroups: comp.sys.amiga.applications,comp.sys.amiga.misc
Subject: Re: Boot disk optimizer?
Message-ID: <1991Apr12.183527.29143@msuinfo.cl.msu.edu>
Date: 12 Apr 91 18:35:27 GMT
References: <41207@cup.portal.com>
Sender: news@msuinfo.cl.msu.edu
Organization: Michigan State University
Lines: 34

Chris_F_Chiesa@cup.portal.com writes:

>Hello All.

>   Had to edit the mountlist on the floppy-I-boot-from, last night, and 
>now the disk seems to "grind" back and forth a lot more than it used to,
>and take longer to boot.  (Well, it did last night when I first DID this
>editing; this morning it seemed okay.  Is my mind playing tricks on me?)

Your mind aint playing tricks - its our computer.
What you probly did was to "Save" the file, the reboot immediatly, right?
If so, then you probly forgot to wait 2-secs after the drive light
goes out before rebooting - therefor the computer did not get a chance
to clean up the disk (write out the sector bitmap), and so the
next time the OS saw the disk (right after reboot) it had to validate
the disk - as well as booting from it, causeing lots of disk seeks
and a SLOW reboot. Try rebooting again, and it should be quick like
your second try.

>years ago that the disk could get "fragmented" causing the head to have
Yes, disks can get fragmented. Its no likely that editing one file
would cause a noticable difference. It could cause a slight difference
if you made the file significantly larger.

>   2) If there is no such animal as (1), can anyone suggest a workaround
>      for (cringe, cringe) HAND reorganization of the disk?  Or other so-
>      lutions to the problem? (Example: on the old Atari 800 you could
>      recover certain disk-space wastage by copying all the files, one at
>      a time, to another disk.  Is there an equivalent strategy here?)

Yes this too will work, but you can do something like:
	copy df0: to df1: all clone
to do the single-file at a time copy, but with nly one command.
Assumeing that you have two floppy drives (or lots of memory, or a hard disk)