Xref: utzoo comp.sys.atari.st:6663 comp.sys.amiga:12261 Path: utzoo!mnetor!uunet!husc6!bloom-beacon!coplex!jim From: jim@coplex.UUCP (Jim Sewell) Newsgroups: comp.sys.atari.st,comp.sys.amiga Subject: Re: Multi-tasking? A nightmare... Message-ID: <161@coplex.UUCP> Date: 29 Dec 87 07:00:10 GMT References: <3256@umn-cs.cs.umn.edu> <2598@killer.UUCP> Organization: Copper Electronics, Louisville, Ky. Lines: 30 Summary: Real example I ran into today. In article <2598@killer.UUCP>, elg@killer.UUCP (Eric Green) writes: [conversation ommitted] > 2) Most of us are notoriously short on foresight, like I was when I > thought that 64K and a floppy drive was the epitomy of computing (after all, I > can do everything you can, right? I can process words, play games, etc.?). > -- > Eric Lee Green elg@usl.CSNET Snail Mail P.O. Box 92191 > {cbosgd,ihnp4}!killer!elg Lafayette, LA 70509 > "There's someone in my head, but it's not me...." -PF Speaking of being short on foresight, it was only today that I was modifying my handy dandy disk re-organizer program (Devices are a pain!) and guess what? I was trying to ^XF (save and finish up) out of Emacs and was out of disk space. How many of you have ever told an editor you were finished, fallen short of disk space, and lost everything because the editor was not taught social graces? I'm sure I'm not the only one. Solution? Use my MULTITASKING Amiga to clean out some disk space before I clicked on the retry block of the requestor. Result? I didn't kill my entire family due to the frustration of losing my program. Moral? Even though nearly anything can be simulated with proper programming on a non M-T system, it rarely is. Many programmers take short cuts which do not allow for mistakes. M-T'ing systems are like insurance in case your favorite program has problems. ================================================================================ Jim Sewell "Make knowledge free!" <*> <*> Code: 1-1A /