Lit. Buffer overruns 1714
Among the wreckage we found a fragment on which Peter Flbutt had scratched: DEC PDP-11 and VAX were little-endian, although the PDP could exhibit odd mid-endian...
(They don't but I'm only there, I don't have time for afc, sorry.)
RT-11 didn't, and couldn't because it ran (mostly?) on models without memory management (hence protection) or U-(E)-K modes. I probably couldn't (and certainly don't want to) count the number of times I wiped my RMON image and had to reboot.
I'm pretty sure no official -8 had modes, although they did have addressing limitations that meant a wild pointer access by itself probably wouldn't clobber the system, you had to actually try. I heard about a 3rd-party addon, I forget who, that locked-down I-O which included the MMU 'change field' operation and hence allowed you to protect memory on a whole-4KW-field basis, but the system I used was single-user only so it wasn't considered justified.
Although I didn't use a 1620 myself, it was notorious as the machine where the user (program) could redefine addition to be wrong -- that doesn't sound like much defense to me! AIUI in those days the primary defense against malfunctioning programs was to mount the input tapes without write-enable rings, and retain multiple generations.
For what Win3.1 was designed to be -- a display-UI manager -- that wasn't so bad. Xwindows isn't much better. The real security and integrity problem was using MSDOS and-or making Windows an OS.
Morten Reistad have lots of banks have gone to single queue for multiple servers (bank tellers) ... frequently there are more tellers than concurrent long...
- David.Thompson1 at worldnet.att.net
Alt Folklore Computers from Newsgroups