CompuServe Messages

Hi Vic, What does timeslicing have to do with preemptive? Well, it sometimes causes the preemption 🙂 But I agree with you, my wording used (what I thought was obviously) a shorthand form. It's too easy to get used to a discussion on one net and carry the same abbreviated phraseology over to another <sigh>. I figured everyone would know what I meant. Heck, even the Commodore engineer was using "preemptive" as shorthand to mean tasks got to reschedule every so often because of a constant trigger. But that's okay, I admire nitpicking, being a nitpicker myself <grin>. So change… "allowed fairly normal preemptive multitasking", to… "allowed the timesliced, preemptive, priority-based, interrupt-driven multitasking scheduling to operate fairly closely, but not exactly, to what was always defined as normal operation by the Exec manuals." Whew. Shorthand is much easier than being deliberately obtuse, I assure you! Thanks for pointing out the need for more exact phrasing. cheers – kevin