8086 memory space was: The Soul of Barb's New Machine 1153
8086 memory space was: The Soul of Barb's New Machine 1154
Ok, let me go a little further. How are you going to load the code memory from the I-O device...
And what about (curse, spit) segmented architectures *wasn't* "interesting"?
Also, as we all recall from Intel's marketing material - Nobody would ever program these amazing new processors at the machine level -- we'd all be writing code in Pascal or PL-M.
Back In The Day, I took one look at the 8086 ISA and the 68000 and said, "One of these sucks. It will surely succeed. I'll take the road less traveled."
Over the subsequent years, I'd had to do a few 8086 based projects - and every time I sat down at one, I was reminded how much it sucked. (The plethora of programmer-exposed memory manipulation in compiled languages should be a flaming waving bright red flag that 'something about this architecture is broken beyond usability). (Sudden flashback strikes of a project where we had to swallow the bitter pill and go from large to huge memory model, and watch performance go down the toilet. -- and what could ever make huge NECESSARY? I can't imagine a case now, but it seemed inescapable back then ... )
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Computer software consists of only two components: ones and zeros, in roughly equal proportions. All that is required is to sort them into the correct order.
Alt Folklore Computers Newsgroups