yes.. iRMX
even catastrophic hardware failures don't crash that thing.. Has a funny way of working. Kernel is sealed in the first page of the PC ( first 64K ) . All remaining memory is essentially a ramdrive.
A program is simply copied from disk and executed. Each program is allowed a scratchfile ( in the ramdrive ) the Os sets the max size of this ramdrive. Any variables used by the program reside in this scratchfile. If a program crashes it is simply reloaded into a different 'sector' and the link is restored to its scratchfile. This scratchfile also includes a stack , heap and all other constructs. Essentially this scratchfile acts as a VM.
I had an ion-implanter (made by Eaton) running on a 386 with a full windowed graphical user interface ( There is a graphical shell on top of iRMX ) Each button or menu is essentially a standalone program that interacts with others. All of a sudden the system console pops up : Memory error at address .. (i forgot the actual addres sbut it was in the high memory ). Reloading affected elements..
and a few seconds later the system was fully operational as if nothing happened.
The fault was a defective DIMM. iRMX had trapped an unstability , moved the corrupted programs to a different 'sector' and marked that portion of the 'ramdrive' as bad. After reloading fresh copies of the affected elemetns it simply pointed them back to their runtime file and they happily took of where the previous instance failed.
The machine kept on running for many more weeks until we shut it down for a scheduled maintenance at which point the faulty dimm was replaced.
As long as the first 64K of memory does not get corrupted by physical damage you cannot crash iRMX.
iRMX lives on as InTime, a concurrent RTOS that can coexist with other OS's and runs simultaneously on multicore processors. It is used for things such as medical equipment, machine control and other 'critical' applications. the critical portion runs on a dedicated core under iRMX. this communicates with a non critical host OS and lets the host do the visualisation and user interface. Even if the host Os fails the iRMX portion remains running and maintains integrity on the system to be controlled.