It's hard for me to imagine the navy allowing itself to get into a
situation where the operation of the ship's main engines and steering
would be completely
subject to some PC, or number of PC's on a network within the ship.
I put just shy of 3yrs. in an engine room aboard a navy ship, back in
the 1960's. The ship had redundancy built into practically every piece
of equipment that was
needed to maintain steerage, even down to manual pumps to pump hydraulic
fluid thru the steering gear. If you are dead in the water, you are a
sitting duck.
They just don't build 'em like that. They may have waited some period
of time before going to manual systems to get underway, but I doubt
seriously if
a network crash would would have prevented complete movement.
--Dave
On 4/6/2012 1:54 PM, Mike Schwab wrote:
http://en.wikipedia.org/wiki/USS_Yorktown_(CG-48)
On 21 September 1997, while on maneuvers off the coast of Cape
Charles, Virginia, a crew member entered a zero into a database field
causing a divide by zero error in the ship's Remote Data Base Manager
which brought down all the machines on the network, causing the ship's
propulsion system to fail.[5]
[deleted[
Atlantic Fleet officials also denied the towing, reporting that
Yorktown was "dead in the water" for just 2 hours and 45 minutes.[6]
[deleted]
On Fri, Apr 6, 2012 at 8:32 AM, McKown, John
<john.mck...@healthmarkets.com> wrote:
Probably, given how we do things anymore, it would likely run Windows. I dread the day
that we lose a war because our weapons "blue screened".
--
John McKown
Systems Engineer IV
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
