Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!wuarchive!uunet!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.advocacy Subject: Re: 8-bit death (was Re: What the heck IS "Interactive TV"?) Message-ID: <1991Apr26.221002.24745@sugar.hackercorp.com> Date: 26 Apr 91 22:10:02 GMT References: <1991Apr21.152513.23054@sugar.hackercorp.com> <02J7020m07rC01@JUTS.ccc.amdahl.com> Organization: Sugar Land Unix -- Houston, TX Lines: 18 In article <02J7020m07rC01@JUTS.ccc.amdahl.com> kls30@DUTS.ccc.amdahl.com (Kent L. Shephard) writes: > Just because MS-DOS doesn't allow swapping and virtual memory directly > does not mean it is not 16-bit. What is your definition of a 16-bit > OS? Mine is one that directly supports 16-bit integers, data formats, if > it is segmented - allows at least 16-bit segments for memory addressing. CP/M allows all those things. My definitions: "8-bit O/S" written for memory on the order of 64K, single user, single tasking. "16-bit O/S" written for memory > 64K, multitasking. "32-bit O/S" written for memory >> 64K, sophissticated VM. > So is NeXT Os 2.0 which, BTW is what my other machine runs. Wish I had that sort of disposable income. -- Peter da Silva. `-_-' .