The EDGAR story reminds me of my first job out of college. We used Nova 3s for the test stations and every software engineer carried their own operating system on (yes really) 5M removable disks. On particularly unique engineer had modified most of the commands and prompts on his version of the OS to some VERY rude alternatives. Well you knew it was bound to happen sooner or later, sales was escorting a potential new customer around the labs and ran across a system running Dave's OS (fake name). The attempts by the salesman to highlight system features were to say the least very PROVOCATIVE.. Next day a memo went out (yes, no emails then only hard copy paper) indicating to all staff that ONLY the standard OSes would be allowed due to a public relations problem caused by a "rogue" OS installation.
I have been one of those who are lucky to have worked on RSX-11M. I was responsible to install a PDP-11 with RSX-11M based control system in India for a German Robotic Welding machine for a mini-truck chassis. The RSX-11m based system with the control software worked so well that we had our first maintenance call 5 years after the system was commissioned and the fault was not with the basic computer system but with one of the associated I/o cards. Later I got so much fascinated with RSX-11M as an OS ( with a very good documentation from DEC) that I designed an RTOS based upon the data structures of RSX-11M and used it in the embedded products of my company.
I don't actually remember what EDGAR stood for, but knowing the engineers responsible for this prank, it was something we couldn't print anyway. But the suggestions are great.
One of the best "retaliations" for this individual came when he was away on a business trip. The engineers ducted the packing material chute from production to his office and filled it to the top with stryofoam peanuts. He had to get a ladder, pull up the ceiling tiles and shovel his way in from the top just to get the door open.
Please stop casting derision on the venerable PDP11 and RSX 11. I recently retired a PDP11, RSX 11M system that ran a conveyor system that had been installed back in the early 1980's. The PDP11 was not the point of failure, obtaining parts for the controls systems long out of production was the problem. The Senior Engineer's password was "NotAPC".
As for EDGAR - Enter Dave, Get Accumulated Results
Locking a cat in a filing cabinet and scaring the secretary to death (being the sixties, we had secretaries, not administration assistants). Just a little multivibrator oscillator with regen/saturation as I recall. No live cats were used in this operation.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.