They tried replacing it with a 5 1/4" drive and messed-up the address jumpers.Maybe the 8” floppy disk failed?
Explains this message:
The incident was introduced by an issue during an earlier network capacity upgrade
They tried replacing it with a 5 1/4" drive and messed-up the address jumpers.Maybe the 8” floppy disk failed?
The incident was introduced by an issue during an earlier network capacity upgrade
I'm a contrarian. I'm selling. And coming out waay ahead!This is how zombie movies start.
Buy ammo.
Psst. Hey, kid. I've got some 7.62x39 if you're up for it. Or are you more of a 9MM guy? I can help you there too.I'm a contrarian. I'm selling. And coming out waay ahead!
Indeed. I read the root cause statement this morning and rolled my eyes.Well, it's not like I expect Microsoft to say "We got hacked by Russian bots" even if that was what happened.
It was responding to queries when I checked just prior to posting the post you quoted, but nothing on the ground stop. ATCSCC is partially responding but gives no indication that it's down other than an empty query response. If they can't put in some kind of fault detection or even a heartbeat to report when their sole means of disseminating something as <supposedly> important as a nationwide ground stop takes a dump then the system is not trustworthy. Start an effing call tree for all I care, and if you're not going to tell me about it through what we are led to believe are 'official channels' then don't hammer me for not following your unwritten double-secret probation rules.FAA's NOTAM system is down last I checked... As is the ATCSCC Advisories database server apparently.