Earlier quoted context omitted.
At a previous job I was a developer on a medical instrument that used Windows to run the UI. Before everyone gets all up in arms about it, Windows/Linux UI & database with external microcontrollers handling real-time control is a very common architectural choice for medical and industrial equipment. To the point where many Systems-on-Module (SoMs) come with a Linux-capable ARM processor and a separate, smaller proces…
Isn't this what Embedded Windows was always for, like for use in medical equipment, ATMs, POS, PLC, oscilloscopes, etc? Basically stuff that's supposed to be fire-and-forget, run 24/7 and that the user shouldn't be able to tinker with. And also what group policies were for, that can disable the user from installing any software? Am I wrong to assume that the fuckup was on your end, for using the wrong tool and not co…
The biggest annoying complaint was "we want to run our EHR software on it!" but because of the FDA requirements, we weren't allowed to install anything on the box. Yet somehow providing AV could be OK in some cases, and in other cases installing Citrix? And then we'd somehow find out someone managed to install the EHR client onto it anyways and it became a big old mess to have to have Philips come send a tech out of their own to reimage a PC we couldn't "legally" service.
It was a big messy pain for a while back in the day. Was happy when we finally got to upgrade to the newer IntelliSpace software on our own PCs in the ward. (Also got to meet a support engineer that came out rocking an Agilent badge, so that was super cool on its own right of history...)