Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!bbn!rochester!cornell!batcomputer!riley
From: riley@batcomputer.tn.cornell.edu (Daniel S. Riley)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Faster Bootup (was: Suggestion for 1.4)
Message-ID: <5200@batcomputer.tn.cornell.edu>
Date: 17 Jun 88 16:57:18 GMT
References: <611@myrias.UUCP> <62300007@hobbiton> <56624@sun.uucp> <2425@amiga.UUCP> <1249@csuna.UUCP>
Reply-To: riley@tcgould.tn.cornell.edu (Daniel S. Riley)
Organization: Cornell Theory Center, Cornell University, Ithaca NY
Lines: 24

In article <1249@csuna.UUCP> swalton@solar.stanford.edu (Stephen R. Walton) writes:
>Yes, 1.2 Execute always uses :T for its temporary.  However, there is
>a real problem with doing this, as I found out: it results in a very
>slow revalidation of your entire hard disk if your Startup-Sequence
>does a LoadWB.  I can email the details (or you can read 'em on B$X),

I haven't read the thread on BIX, but this seems a little extreme.  As
I understand the situation, LoadWB does something equivalent to pulling
a disk out and sticking it back in (ACTION_something, diskchange or
inhibit, I guess), so you just need to avoid anything that you wouldn't
want to be happening when you pull out a disk.  Most people get burnt
by doing something like "date >now" followed by loadwb, which gets them
because of the 3 second DOS delay in updating the disk.  I would think
that as long as you wait longer than 3 seconds after the last write, and
don't have any files open for write (like .key temporary files from
execute), you should have no problems.  This certainly seems to be true
on floppies, and I would expect it to be the same with a hard disk.
Two questions:
  1.  Am I missing something here?  (I'm about to get a hard disk, so
      I'm interested.
  2.  Why does LoadWB do whatever it does?

-Dan Riley (dsr@lns61.tn.cornell.edu, dsr@crnlns.bitnet)
-Wilson Lab, Cornell U.