I remember when they rolled out the Microsoft Mambo #5, it was so bad I had to leave the room so I wouldn't laugh in front of the customers. I don't know who thought this was a good idea, but they should be dragged to death behind a truck.
No, it gives an imposing illusion of "My managers dictate every action I take down to the smallest detail." Because only management things names that retarded and unpronounceable are a good idea. The first time someone tried to recite one of these over the phone to a new user it should have become apparent how useless it is.
That one big map is called a sectional chart. What's on the iPad are approach plates, which are a completely different product.
Sectional charts tell you how to get from airport A to airport B and what's in between to avoid or use as reference points. Approach plates are used by instrument-rated pilots to fly the approaches and departures for a given airport.
We didn't know NASA was patching the code; We thought they were just generating the trajectory constants. We asked IBM first; IBM Federal Systems transferred all their NASA stuff when they were divested, and they lost track of it.
Anyway, thanks for asking , and send my thanks to your father for the work he did. If you google for "Orbiter NASSP" you can find our project and its forums. You're more than welcome to check it out if you want.
Yeah, this kind of stuff is what we're banking on. NARA has the code somewhere, but they're so understaffed it'll take them decades before they can consider beginning to consider finding it.
We would be eternally grateful. Even something like the names of other people we could ask would be immensely useful. We have lots of hardware documentation so far, but nothing in the way of software or documentation for it. Pretty much anything is potentially useful, as leads for other things if nothing else.
We aren't the US government, and even if we were, we'd have to be in the right department to have access to pension check data. We're an open-source project working on systems level simulation of the Apollo spacecraft. Our goal is to simulate every aspect of the missions with the original checklists and software.
The technical term you want is "Apollo Guidance Computer". There were two AGCs, one in the Command Module, and one in the Lunar Module. These were the CMC and LGC respectively. We already have the software for both of these. The LM also had a backup computer of completely different design, called the Abort Guidance System. We have the software for that. We're missing the LVDC software and the software used by mission control. The LVDC flew the Saturn, and the ground control guys used lots of software for lots of things.
Does your father have any Saturn guidance software source code AT ALL, or any knowledge of where it might be? We have been desperately searching for the Saturn LVDC guidance software for years now, even to the extreme of obtaining core planes from a LVDC and trying to read them out. If your father has any prints at all, or any knowledge of where the software might be, we DESPERATELY need to hear from him!
...you're not playing with a full DEC! PDP-10 into eternity! ---- @info ver Bamboo Forest of the Lost, Eientei TOPS-20 Monitor 7.1(21733) PANDA TOPS-20 Command processor 7.1(4453)-4 @systat Tue 8-Feb-2011 07:43:09 Up 1958:51:50! 0+9 Jobs Load av 0.03 0.01 0.01
Maybe I worded it badly. The idea is to be prepared for the worst scenario each time, so that if it does come to pass you aren't surprised by it and maximize your chances of successfully handling the situation. Being complacent about it and assuming "It'll never happen to me" has a habit of biting people in the ass. Then again, the consequences of my being lazy up front are probably a lot more severe than the chances of your being lazy in the back...
Well, even if it does stop in the seat ahead of you and lose all of its energy, it'll still have injured your hands departing, and you need those to operate doors or remove debris from your path on your way out. In any event, that's just one of the points I made, there's plenty of other reasons to stow your stuff for takeoff and landing.
Because those who make the rules miss the point of the rules, which is why we have the interference boogeyman. It is part of the safety briefing to please stow all objects in the seatback or overhead bin for takeoff and landing. If you ignore us, we can't force the issue, it's not against the rules.
They never get mentioned as a reason because pilots get lousy press. I couldn't get this stuff in the news even if I mugged Dan Rather and wrote it on his chest in permanent marker. Anyway, it is part of the safety briefing (ours at least) to please stow all objects in the seatback or overhead bin. But since it's not against the FAA rules, we can't force the issue if you want to ignore us.
Besides, if there was interference, we'd know about it up front - We'd hear it in our radios or see it in the instruments. Then we'd just jump on the PA and ask everyone to turn off their stuff for a moment to see if it goes away. If it goes away, then it's simple process of elimination to find the interfering device, and then notify people to have it handled. It can't be -that- common, at least not in any remotely modern equipment.
I too earnestly wish for there to be less bullshit in flying. For some reason those government types seem really fond of it...
Slashdot Mirror
Vote for someone else? What someone else?
This is like saying "You can always pick up the turd by the clean end."
I remember when they rolled out the Microsoft Mambo #5, it was so bad I had to leave the room so I wouldn't laugh in front of the customers. I don't know who thought this was a good idea, but they should be dragged to death behind a truck.
TOPS-10 and TOPS-20 are vastly different.
TOPS-20 > VAX/VMS
Still runs as it did the day it was shipped.
Remember children, if it's not 36 bits, you're not playing with a full DEC!
You were at Moon's Laundromat?
No, it gives an imposing illusion of "My managers dictate every action I take down to the smallest detail."
Because only management things names that retarded and unpronounceable are a good idea.
The first time someone tried to recite one of these over the phone to a new user it should have become apparent how useless it is.
After his frontal lobotomy, he should fit in just fine!
That one big map is called a sectional chart.
What's on the iPad are approach plates, which are a completely different product.
Sectional charts tell you how to get from airport A to airport B and what's in between to avoid or use as reference points.
Approach plates are used by instrument-rated pilots to fly the approaches and departures for a given airport.
We didn't know NASA was patching the code; We thought they were just generating the trajectory constants.
We asked IBM first; IBM Federal Systems transferred all their NASA stuff when they were divested, and they lost track of it.
Anyway, thanks for asking , and send my thanks to your father for the work he did.
If you google for "Orbiter NASSP" you can find our project and its forums. You're more than welcome to check it out if you want.
Yeah, this kind of stuff is what we're banking on. NARA has the code somewhere, but they're so understaffed it'll take them decades before they can consider beginning to consider finding it.
We would be eternally grateful. Even something like the names of other people we could ask would be immensely useful.
We have lots of hardware documentation so far, but nothing in the way of software or documentation for it.
Pretty much anything is potentially useful, as leads for other things if nothing else.
We aren't the US government, and even if we were, we'd have to be in the right department to have access to pension check data. We're an open-source project working on systems level simulation of the Apollo spacecraft. Our goal is to simulate every aspect of the missions with the original checklists and software.
The technical term you want is "Apollo Guidance Computer". There were two AGCs, one in the Command Module, and one in the Lunar Module. These were the CMC and LGC respectively. We already have the software for both of these. The LM also had a backup computer of completely different design, called the Abort Guidance System. We have the software for that. We're missing the LVDC software and the software used by mission control. The LVDC flew the Saturn, and the ground control guys used lots of software for lots of things.
No, he gets all his stuff from the Iranians.
Does your father have any Saturn guidance software source code AT ALL, or any knowledge of where it might be?
We have been desperately searching for the Saturn LVDC guidance software for years now, even to the extreme of obtaining core planes from a LVDC and trying to read them out.
If your father has any prints at all, or any knowledge of where the software might be, we DESPERATELY need to hear from him!
N/T
Can we have a special moderation level for SEO spam that causes the links in their post to be deleted?
...you're not playing with a full DEC!
PDP-10 into eternity!
----
@info ver
Bamboo Forest of the Lost, Eientei TOPS-20 Monitor 7.1(21733)
PANDA TOPS-20 Command processor 7.1(4453)-4
@systat
Tue 8-Feb-2011 07:43:09 Up 1958:51:50!
0+9 Jobs Load av 0.03 0.01 0.01
No operator in attendance
Usually.
Of course they aren't. The current rules are about maximizing airphone profits. What makes you think the rules are about safety?
Maybe I worded it badly. The idea is to be prepared for the worst scenario each time, so that if it does come to pass you aren't surprised by it and maximize your chances of successfully handling the situation. Being complacent about it and assuming "It'll never happen to me" has a habit of biting people in the ass. Then again, the consequences of my being lazy up front are probably a lot more severe than the chances of your being lazy in the back...
Well, even if it does stop in the seat ahead of you and lose all of its energy, it'll still have injured your hands departing, and you need those to operate doors or remove debris from your path on your way out.
In any event, that's just one of the points I made, there's plenty of other reasons to stow your stuff for takeoff and landing.
Because those who make the rules miss the point of the rules, which is why we have the interference boogeyman.
It is part of the safety briefing to please stow all objects in the seatback or overhead bin for takeoff and landing. If you ignore us, we can't force the issue, it's not against the rules.
They never get mentioned as a reason because pilots get lousy press. I couldn't get this stuff in the news even if I mugged Dan Rather and wrote it on his chest in permanent marker.
Anyway, it is part of the safety briefing (ours at least) to please stow all objects in the seatback or overhead bin. But since it's not against the FAA rules, we can't force the issue if you want to ignore us.
Besides, if there was interference, we'd know about it up front - We'd hear it in our radios or see it in the instruments. Then we'd just jump on the PA and ask everyone to turn off their stuff for a moment to see if it goes away. If it goes away, then it's simple process of elimination to find the interfering device, and then notify people to have it handled. It can't be -that- common, at least not in any remotely modern equipment.
I too earnestly wish for there to be less bullshit in flying. For some reason those government types seem really fond of it...