🚀 go-pugleaf

My company is considering using Windows 3.1 (W3.1) for a mission
critical application.  Mission critical in general are applications
such as nuclear reactor systems, air traffic control systems, and
manned space flight systems.  Mission critical in our application
means real-time, multiply concurrent applications consisting of
custom-built W3.1 applications, commercially-off-the-shelf (COTS)
products, ethernet LAN programs with both incoming and outgoing
traffic, older custom-built DOS applications, and X-Windows
displays exported from X-applications on the LAN for monitoring and
controlling a fleet of up to 25 publicly used communications
satellites.  This W3.1 user station is the only access point into
a distributed computing environment of over 40 server machines; if
the user station malfunctions there is no other alternative access
available.  Our design is primarily using W3.1 as a client to
several UNIX servers over the ethernet LAN.

We are searching for people or organizations who currently are, or
are planning to, use W3.1 for mission critical projects to share
with us their key reasons for deciding on W3.1.  We are also
looking for groups that have investigated W3.1 and decided not to
use it for mission critical applications and the reasons why.

We know that many people have strong opinions about W3.1 and we
respect those opinions; however, we are looking for cases that
actually evaluated W3.1 and have made a go/no-go decision for using
it.  Also if there are report/articles/studies on using W3.1 for
mission critical projects -- either pro or con -- we would be
interested in knowing about such.

Thanks in advance for any and all assistance.
-- 
Randolph C. Nicklas                                nicklas@digex.com
Ground Networks Engineering Department             202.944.6938
International Telecommunications Satellite Organization (Intelsat)