It's been a nice sunny day, and all that; and I've been out enjoying it; and got back to find myself wondering where the word "geek" comes from (dunno why). So on to Wikipedia. Excerpt:
"Formerly, the term referred to a carnival performer often billed as a wild man whose act usually includes biting the head off a live chicken, bat, snake or bugs."
Well, yeah, "bugs" connects. But I hadn't been aware that my very first OS, CP/M, might stand for "Chicken Post/Mortem".
Just a thought. And it's still nice and sunny out there, chicks. Ted.
-------------------------------------------------------------------- E-Mail: (Ted Harding) Ted.Harding@manchester.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 21-Mar-10 Time: 17:23:52 ------------------------------ XFMail ------------------------------
On Sun, 21 Mar 2010 17:23:55 -0000 (GMT) (Ted Harding) Ted.Harding@manchester.ac.uk allegedly wrote:
Well, yeah, "bugs" connects. But I hadn't been aware that my very first OS, CP/M, might stand for "Chicken Post/Mortem".
Ah yes, CP/M, the wonders of PIP destination = source.
Mick ---------------------------------------------------------------------
The text file for RFC 854 contains exactly 854 lines. Do you think there is any cosmic significance in this?
Douglas E Comer - Internetworking with TCP/IP Volume 1
http://www.ietf.org/rfc/rfc854.txt ---------------------------------------------------------------------
On 21-Mar-10 20:53:53, mick wrote:
On Sun, 21 Mar 2010 17:23:55 -0000 (GMT) (Ted Harding) Ted.Harding@manchester.ac.uk allegedly wrote:
Well, yeah, "bugs" connects. But I hadn't been aware that my very first OS, CP/M, might stand for "Chicken Post/Mortem".
Ah yes, CP/M, the wonders of PIP destination = source. Mick
It was amazingly good, for what it was designed for. In my 64K-of-RAM Sharp MZ-80B (with 2 floppy drives, cassette drive, and a graphics-capable screen -- 16K Graphics RAM), the whole CP/M "kernel" lived in the top 16K of RAM (plus a little bit at the bottom end), leaving a bit less than 48K, and I could run a FORTRAN compiler (and later a C compiler) on it. Lots of swappy-to-floppy involved at times, and perpetual reading on of "overlays" from floppy, but it worked, and did some quite heavy stuff.
Where Microsoft made their most far-reaching design error, in my view, was in emulating CP/M as their base structure for DOS, with a few bits (and not the really important ones) pinched from Unix (e.g. a hierarchical directory structure). One side-effect of this was the pestilential "" separator for directory paths, since CP/M used "/" as the options flag for commands (where Unix uses "-"), and MS kept this.
Ted.
-------------------------------------------------------------------- E-Mail: (Ted Harding) Ted.Harding@manchester.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 21-Mar-10 Time: 21:30:51 ------------------------------ XFMail ------------------------------
(Ted Harding) wrote:
Where Microsoft made their most far-reaching design error, in my view, was in emulating CP/M as their base structure for DOS, with a few bits (and not the really important ones) pinched from Unix (e.g. a hierarchical directory structure). One side-effect of this was the pestilential "" separator for directory paths, since CP/M used "/" as the options flag for commands (where Unix uses "-"), and MS kept this.
I believe that isn't 100% accurate, it was more a lack of foresight and not really on Microsoft's part. MS didn't write DOS (in fact they have never written a PC operating system from the ground up and by themselves)*
When they bought 86-DOS (originally qdos) from SCP it was already an x86 CPM clone and already had the / as options flag as per CP/M. All MS did was fix it to run on the 8088 as well as the 8086, change the copyright notice in command.com and ship to be bundled with the new IBM PC's. Version 1 did not have support for hierarchical file systems.
By version 2 they needed Hard Disk support which meant hierarchical file systems. So they did a partial rewrite of 86-DOS and then oops...we already used "/". They couldn't very well make version 2 totally incompatible with version 1 so they elected to use "" as the separator and we have been stuck with it ever since.
* In fact in recent history nobody has, the last one I can think of that was truly ground up is BeOS.
-
mick -
Ted.Harding＠manchester.ac.uk -
Wayne Stallwood