Don't bother. End of this year the government has a new tax package and special user fees that will increase the costs by over 400% (proceeds going to fund tax breaks for the airlines, of course) and "increase security" for private airfields as well. It was nice while it lasted but the party's over.
My high school had a calculator policy of "You may bring any calculator you like to calculator-allowed tests." So one day I decided that my calculator was GLAXIA, my PDP-11/44 which ran RSTS/E (V8 or V7, I forget which...) I packed the whole thing on a cart; the system (Two BA11s), RA81 disk, and LA-120 teletype, and wheeled it into the classroom. The teacher asked me what it was - "It's my calculator." The look on his face was priceless. It was loud as hell, but the teacher allowed me to complete the test with it. I forget what I scored. Thereafter the calculator policy was changed to read "You may bring any calculator you like to calculator-allowed tests, provided it does not dim the lights when powered on."
Not necessarily - We have a lot more ground to cover, and the TSA would get involved and screw the whole thing up. We'd need a complete change of government to eliminate the TSA and all the homeland security BS, and a loco about 50% faster than Shinkansen. (Unobtainium.) That might stand a chance.
Don't delude yourself, suing Microsoft would be suicidal to the point of stupidity. Microsoft has more cash on hand right now than RedHat can make in the next ten years, and probably the next fifty years. Even if you had an airtight case, MS has enough money and power to stall the case until you go bankrupt. How many years has the SCO thing been going on? Now imagine if SCO had one thousand times more money for their corporate war-chest, and the influence of many senators and congressmen. MS would crush RedHat like a bug, then use that judgement to go after all of the other distributions. They'd just love it if RedHat tried to sue them, it would be like getting out of the safari car and kicking the lions.
It is still the only heavy-return-from-orbit vehicle we have. This capability should not be forgotten. Once we abandon the shuttle for the CEV nobody will have this capability. It's one thing to get stuff into orbit, but another to manufacture things in orbit and send them down to Earth.
Without the FCC, I can also set up a large broadcasting station that transmits many signals throughout the FM broadcast band, strategically placed over the top of any existing stations, for the purpose of promoting Scientology. All it takes is one person with a few hundred dollars to talk over the top of any station they want for a few block radius. One guy with a few hundred dollars doing this trick in the HF spectrum can ruin use of a frequency for an entire continent. Don't like it if the guy down the street decides to put a hardcore gangsta rap station over the top of your low-power talk station? TOUGH.
Not really. The DSKY was just an IO device. The CM had two and the LM had one. There was also a sort of "virtual" DSKY in both vehicles that was used from the ground. The ground sent DSKY keystroke codes as commands and got DSKY display codes in the downlinked data.
The IU was the Instrument Unit that was in the Saturn. The IU contained all of the instruments of the Saturn, and two small computers. The "main" computer was called the LVDC, or Launch Vehicle Digital Computer. It was attached to a specialized IO adapter called the LVDA, which fed attitude error signals to an analog computer called simply the Flight Control Computer. The FCC moved the engines to null the error signals. This was all designed by IBM, who has since lost much of the documentation.
The CM and LM computers were designed by MIT and called AGC or Apollo Guidance Computer. They were entirely separate, save for a provision for the CM AGC to provide manually-generated take-over error signals to the FCC via the LVDA in the event of a LVDC failure in the third stage. The take-over was never used.
(I work on a project that is reverse-engineering Apollo as a GPLed software simulation, so I know way more than my fair share. My current project is reverse-engineering the Saturn LVDC, since the original source code was lost. I am watching this with great interest, since if this is true it means the last two years of my work will be a total waste.)
Remember that the kernel is C, not C++. The goto here is safe. The deal with GOTO was that it was not supposed to be used to jump from one function to another or to replace functions. (C will not allow you to do this.) That was the point of the "go to considered harmful" paper - That explicit jumps would cause people to avoid writing properly structured code. Inside a function a go-to is entirely legal and sometimes allows you to save clocks by skipping things you don't need. In kernel code, saving clocks is entirely worth it, since your function may possibly be re-entered at a high rate, and your code blocks all other code in the system (you're the kernel). In an application, it's less worth it and the goto is probably unnecessary.
Personally I use whatever the language gives me wherever I can to make things as computationally short as possible. Sacrificing performance for programmer comfort does not make sense. If the code looks ugly, but it works (and works fast!), that's all it needs to do. For every one programmer you have thousands of users, and the users don't care if the source is pretty or not.
I spotted this when I was trying to get one of the Touhou shooting games to work and couldn't update the DLLs. I even mentioned it in the Wine IRC channel. I *KNEW* something was up!
I'm uninstalling it and demanding a refund, I refuse to support thieves.
There were a few BASICs available for the 2020. If you wanna try it for as real as you can get, there's a few 10 emulators running around now that will do the job. Visit http://www.aracnet.com/~healyzh/pdp10emu.html and pick whatever one looks good.
They have an ad for a KL10 DECSYSTEM-20; I have a KS10 in my living room. It still runs like the day it was shipped, unlike most of the PCs I have bought over time... They don't make em like they used to!
Slashdot Mirror
Don't bother. End of this year the government has a new tax package and special user fees that will increase the costs by over 400% (proceeds going to fund tax breaks for the airlines, of course) and "increase security" for private airfields as well. It was nice while it lasted but the party's over.
Does "Hello Kitty" count?
Reply to cancel erroneous moderation
My high school had a calculator policy of "You may bring any calculator you like to calculator-allowed tests."
So one day I decided that my calculator was GLAXIA, my PDP-11/44 which ran RSTS/E (V8 or V7, I forget which...)
I packed the whole thing on a cart; the system (Two BA11s), RA81 disk, and LA-120 teletype, and wheeled it into the classroom.
The teacher asked me what it was - "It's my calculator." The look on his face was priceless.
It was loud as hell, but the teacher allowed me to complete the test with it. I forget what I scored.
Thereafter the calculator policy was changed to read
"You may bring any calculator you like to calculator-allowed tests, provided it does not dim the lights when powered on."
Old hardware rocks!
It's supposed to "defeat" people who use mythtv/tivo/etc to remove ad segments when timeshifting.
Not necessarily - We have a lot more ground to cover, and the TSA would get involved and screw the whole thing up.
We'd need a complete change of government to eliminate the TSA and all the homeland security BS, and a loco about 50% faster than Shinkansen. (Unobtainium.)
That might stand a chance.
I think that's an intentional joke. It has to be, otherwise nobody can read it.
The cake is a lie! The Cube is your friend!
Don't delude yourself, suing Microsoft would be suicidal to the point of stupidity. Microsoft has more cash on hand right now than RedHat can make in the next ten years, and probably the next fifty years. Even if you had an airtight case, MS has enough money and power to stall the case until you go bankrupt. How many years has the SCO thing been going on? Now imagine if SCO had one thousand times more money for their corporate war-chest, and the influence of many senators and congressmen. MS would crush RedHat like a bug, then use that judgement to go after all of the other distributions. They'd just love it if RedHat tried to sue them, it would be like getting out of the safari car and kicking the lions.
Other options:
Combine city police from Half-Life 2
HAL-9000
Gilbert Gottfried (for telemarketers)
Stephen Hawking
The "Whisper" voice from MacinTalk
Oh, and the option to have any of these with a user-selectable amount of reverb/echo.
It is still the only heavy-return-from-orbit vehicle we have. This capability should not be forgotten. Once we abandon the shuttle for the CEV nobody will have this capability. It's one thing to get stuff into orbit, but another to manufacture things in orbit and send them down to Earth.
Without the FCC, I can also set up a large broadcasting station that transmits many signals throughout the FM broadcast band, strategically placed over the top of any existing stations, for the purpose of promoting Scientology. All it takes is one person with a few hundred dollars to talk over the top of any station they want for a few block radius. One guy with a few hundred dollars doing this trick in the HF spectrum can ruin use of a frequency for an entire continent. Don't like it if the guy down the street decides to put a hardcore gangsta rap station over the top of your low-power talk station? TOUGH.
So, basically, something like an iPhone, but bigger and without the phone?
Not really. The DSKY was just an IO device. The CM had two and the LM had one. There was also a sort of "virtual" DSKY in both vehicles that was used from the ground. The ground sent DSKY keystroke codes as commands and got DSKY display codes in the downlinked data.
The project I work with is at http://nassp.sourceforge.net/
Needs moderation "+5 Terrible".
I'm going to hell for laughing at this... Good show!
The IU was the Instrument Unit that was in the Saturn. The IU contained all of the instruments of the Saturn, and two small computers. The "main" computer was called the LVDC, or Launch Vehicle Digital Computer. It was attached to a specialized IO adapter called the LVDA, which fed attitude error signals to an analog computer called simply the Flight Control Computer. The FCC moved the engines to null the error signals. This was all designed by IBM, who has since lost much of the documentation.
The CM and LM computers were designed by MIT and called AGC or Apollo Guidance Computer. They were entirely separate, save for a provision for the CM AGC to provide manually-generated take-over error signals to the FCC via the LVDA in the event of a LVDC failure in the third stage. The take-over was never used.
(I work on a project that is reverse-engineering Apollo as a GPLed software simulation, so I know way more than my fair share. My current project is reverse-engineering the Saturn LVDC, since the original source code was lost. I am watching this with great interest, since if this is true it means the last two years of my work will be a total waste.)
To Steer a MIR you Clearly Need a Beer! (Have comrades got it?)
Slashdot, I am honestly ashamed that none of you has posted this yet!
Slashdot groupthink hates the shuttle. Anything pro-STS is flamebait.
Remember that the kernel is C, not C++. The goto here is safe. The deal with GOTO was that it was not supposed to be used to jump from one function to another or to replace functions. (C will not allow you to do this.) That was the point of the "go to considered harmful" paper - That explicit jumps would cause people to avoid writing properly structured code. Inside a function a go-to is entirely legal and sometimes allows you to save clocks by skipping things you don't need. In kernel code, saving clocks is entirely worth it, since your function may possibly be re-entered at a high rate, and your code blocks all other code in the system (you're the kernel). In an application, it's less worth it and the goto is probably unnecessary.
Personally I use whatever the language gives me wherever I can to make things as computationally short as possible. Sacrificing performance for programmer comfort does not make sense. If the code looks ugly, but it works (and works fast!), that's all it needs to do. For every one programmer you have thousands of users, and the users don't care if the source is pretty or not.
I spotted this when I was trying to get one of the Touhou shooting games to work and couldn't update the DLLs.
I even mentioned it in the Wine IRC channel.
I *KNEW* something was up!
I'm uninstalling it and demanding a refund, I refuse to support thieves.
Because the US terrorists keeps it from happening! Duh.
It's all our fault anymore, where have you been?
There were a few BASICs available for the 2020. If you wanna try it for as real as you can get, there's a few 10 emulators running around now that will do the job. Visit http://www.aracnet.com/~healyzh/pdp10emu.html and pick whatever one looks good.
You weren't the only weird kid...
They have an ad for a KL10 DECSYSTEM-20; I have a KS10 in my living room.
It still runs like the day it was shipped, unlike most of the PCs I have bought over time...
They don't make em like they used to!
Nope, two fingers on pad plus a click means a right-click in Boot Camp.
Oh my God, bear is driving! How can that be?