Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!ames!ncar!boulder!sunybcs!bingvaxu!leah!itsgw!steinmetz!uunet!cs.dal.ca!aucs!840445m
From: 840445m@aucs.UUCP (Mic Mac)
Newsgroups: comp.sys.amiga
Subject: Multitasking example
Keywords: amiga,multitasking
Message-ID: <1564@aucs.UUCP>
Date: 12 Feb 89 19:17:23 GMT
Organization: School of Computer Science, Acadia Univ., Nova Scotia
Lines: 25

This is in reply to the fellow who wanted a nice simple example of why a 
multitasking Amiga blows the doors off of other machines:

You have called up a BBS in (some far away place) to download a PD game.  The
game is very large and you expect it to take 20 minutes or so.  You realize
that the long distance charges for the call will be expensive, but you want
the game so you will make the call.

After 20 minutes of transferring, the system tells you that your disk is full.
On most machines, you have to abort, get a new disk and try again, thus wasting
the money on that 20 minutes worth of phone call.  Luckily, those of us with
*TRUE* multitasking machines like the Amiga just have to call up a CLI, delete
a few files, then click on the 'RETRY' button in which case the transfer 
continues where it left off.

The only time wasted is the time it takes to delete a few unwanted files
(2 minutes worse case) instead of wasting the whole 20 minutes of LD time.

How's that?

-- 
% Alan W. McKay     %                                             %
% Acadia University %   " The world needs more Socrates'          %
% Wolfville N.S.    %     walking the streets today "             %
% CANADA            %                       - S. Corbett          %