Path: utzoo!mnetor!uunet!nuchat!peter
From: peter@nuchat.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: Re: Semicoherent flame about Amigados.
Message-ID: <662@nuchat.UUCP>
Date: 20 Feb 88 18:38:33 GMT
References: <644@nuchat.UUCP> <5220@well.UUCP>
Organization: Public Access - Houston, Tx
Lines: 34

In article <5220@well.UUCP>, ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab) writes:
> Either I'm leading a blessed life, or Peter's drives may be a teensy bit off
> spec.  Realize that I'm just guessing, however.

Well, it doesn't seem to care what drive I'm using... and I think it unlikely
that both of my drives would be off by the same amount. 

> 	And now, the real point of this posting:

> In article <644@nuchat.UUCP> peter@nuchat.UUCP (Peter da Silva) writes:
> >Finally, I have a suggestion for the multitasking shuffle. Have LoadSeg keep
> >a semaphore for each floppy, and single-thread itself. Make Copy respect it.
> >And publish how to use it so that we can make our utilities do the same
> >thing.

> 	(Motion of hand moving rapidly over head whilst uttering, "Whoosh!")

> 	Huh??  Could you clarify that one; you lost me completely.

The multitasking shuffle is what happens when you accidentally try to load
two programs from the same floppy at one time. You get:

	Read 1 block from c:FOO
	Grind/seek.
	Read 1 block from c:BAR
	Grind/seek.
	Read 1 block from c:FOO...

If LoadSeg was an atomic (or single-threaded) operation this wouldn't be a 
problem.
-- 
-- a clone of Peter (have you hugged your wolf today) da Silva  `-_-'
-- normally  ...!hoptoad!academ!uhnix1!sugar!peter                U
-- Disclaimer: These aren't mere opinions... these are *values*.