🚀 go-pugleaf

>> 	Given these constraints, it should be posible to implement a
>> multi-tasking O/S without having to hassle with a MMU.

True; it's been done (as many have pointed out). However, if you're
doing C or assembler development, loose pointers, mis-typed parameters
for calls, and other things will cause the system to die. This is
enough of a pain that ASDG is marketing a ram-disk driver that tries
to recover what was in memory before the crash when it comes up.

For interpreted Pascal, or Lisp, this won't be a problem. But
someone's gotta put up with porting those things (and editors, and
compilers, and etc.) in the first place.

Even under such conditions, the result is _still_ better than an
unprotected single-tasking OS.

	<mike