An apology in diplomatic matters such as these is the same as pleading guilty to a criminal offense. By apologizing, Bush would be proclaiming to the world that the spy plane should not be there in the first place, that the fighter pilot had the right to be buzzing an American plane in international air-space, and that China would have free go to continue such behavior in the future.
Very true, people should realize apologizing in this situation not like saying you are sorry when you bump into someone; which is just common courtesy. But it comes closest to apologizing after a fender bender. Unless you feel that the accident was entirely your fault and are about to agree to have your insurance cover everything you don't start out by apologizing to the other driver because that can be taken as an admission of fault and can be used by them or their lawyer to force you to pay for everything even if it was a situation where both parties were equally at fault, or even a case where the other driver appeared to be at fault.
This type of formal apology carries with it the implication of responsibility and it is by no means clear that the US is primarily responsible for this accident. No apology should be given.
They [the Chinese] probably don't even have all those nukes they keep whispering about. Have we ever seen them detonate one? Well have we? NO! They don't exist.
Ah, that would explain the newspaper articles about the non-existent explosion of china's imaginary nuclear weapons, for example here is one from cnn. And here is a link from greenpeace (not my favorite people) that contains a history of Chinese nuclear testing. How about a CIA paper on ICBM threats to the US that covers China's ICBMs.
If you thing we've never seen China set off a nuclear weapon then you just haven't been paying attention!
Re:Oh for God's sake: Rand and Robyn Miller
on
Godfathers Of Gaming
·
· Score: 1
Not to mention that Myst was bundled with almost every cd-rom drive and multimedia PC for the first 3 or 4 years they existed and its not surprising it moved huge numbers of copies.
>Picks and Shovels! The people who made out during the gold rush were the ones selling picks and shovels!
Don't forget selling beer, but you are right. The people who make most of the money in a gold rush are the suppliers. Because it is more reliable to outfit and equip most of the miners than it is to sit out there with a pick and hope to hit the motherload. Better to let others do that and just sell more to the succesfull ones.
>Note that I'm not talking about specifying this >per project; I mean the WHOLE THING. NASA should >be a dozen people in an office in Washington, >most of 'em accountants, a couple engineers and >scientists.
Not quite; if you want to cut back NASA it should be cut to a bunch of researchers and engineers who basically do experimental research and testing. Along the lines of the x-plane program. Think up something, build a prototype, use the prototype, collect data points, and refine. Then once they work out the bugs license the tech off to intertested parties and begin again. And not just one big thing, like the X-33, but a bunch of different tests at once. Try a bunch of things, don't get fixated on the one true way (TM)
Contract out full scale development and launching. Then follow your suggestion on holding contractors to their bids, and keep NASA from being the aerospace wellfare agency.
Also, this should minimize friction between parts of NASA. Prevent what happened to the DC-X. What a waste. McDonald Douglas built on their own nickle a protoype single stage to orbit vehicle (note the protype was never expected to reach orbit, too heavy, it was just to gather operational data) tested it, validated parts of the flight envelope, had plans to build a follow on the DC-Y, which would be capable of sub orbital ballistic flight, and the after gathering data on that, build the final single stage to orbit vehicle. They turned the DC-X prototype over to NASA, who tested it for a while, but declined to have anything to do with a followup, becuase it conflicted with their X-33 program.
I ran into this. I had a pair of 366 Celerons on a BP-6, payed a bit extra to get pre-tested at 550 chips (before Celerons were availble at 550) and they ran great for months. No problems. Then I tried to run a render on them (actually they were part of a mosix cluster that I ran the render on) and every singe time they would crash the render process. Dropped them back to stock 366 and they ran fine. The render process obviously hit a slow timing path that normal operation didn't.
AFAIK noone has released a comprehensive stress test program that attempts to stress all possible timeing paths in an inplace CPU, which is what you would have to do, since OCers don't have the timeing info worked out by the engineers.
Not really. A weapon, or object may be more or less capable of causing death. For example the star trek phasor on stun, which is frequently sited by proponents of non lethal weaponry as the holy grail can still cause death in some situations. i.e. stun someone who is speeding down the highway, or for a more military situation stun someone right after they pull the pin on a grenade. Pretty much anything could be used to cause death if someone tried hard enought. slightly lethal in this contex mean that in normal use there is a low possibility of causing death, as opposed to highly lethal like an M-16 which has a high possiblity of causing death. Not a certainty, someone could live through being hit with a burst from an assult rifle.
The first calculator I ever used my my dad's HP-21, which he bought when he was in college. The calcualator is older than I am and still works fine, I have it sitting on my desk right now.
Of course since I learned RPN first I can't stand to use a brain dead 'normal' calcuator.
Now an enemy knows that the US has 747's used to shoot down missiles. Doesn't that suddenly make every 747 in the sky a suspect?
Someone, please correct me if I'm wrong, but this seems likely in stressful times to make civilian airliners a legitimate target.
The US already uses aircraft based on civilan models, such as the E-3 AWACS, the JSTARS, and the KC-135 all of which are based off the popular 707 aircraft. Having 747s wouldn't add to the problem, they have to have prominent military marking on them, and civilan airliners route away from war zones anyway, so they are unlikely to be mistaken for a ABL and shot down.
I always liked the ornithopters from the game DuneII. You can't see them really well, but they look sort of like a dragon fly, large thin rounded wings that can flap and a jet thrust for propultion. Those scaled up and shot on screen would look amazing.
Actually a good, non destructive one is to walk up to a win9x box and open the run dialog and enter program.exe. Run it and maximize, (it is the win3.1 program manager interface) then ask the sales guy why this computer has win3.1 and not win9x on it.
Except that with cell phones that functionality changes a bit. Figure out how to power on this model of phone. Oh, type is some security code. Dial the phone number. Is it calling? No. OK now what button do I push on this phone to make it dial. OK, Send, Talk, Pound?
It's not hard to use a cell phone, even someone else's, but it is hardly standard.
I believe the previous poster is refering to the fact that the math co-processor chip (487 ?) you could buy to give a 486sx the math capabilitys of a 486dx was in fact a 486dx chip in a new package which totaly bypassed the original 486sx.
The point of using xor is not so much to keep them from knowing the value, as to keep them from finding the location of the value. Assuming you have the speed right, they could test a given 16 bit memory location in 1 second, but that doesn't help because they don't know which memory location to test. You are trying to make it harder to do a memory scan to locate variables, not place unbreakable(TM) encryption on them.
Assuming that they could restrict their scan to a 20 meg foot print, they would have about 2^20 16 bit addresses to scan, so it given your statement that it would take 1 second to break a 16 bit address it would only take 2^20 seconds, or about 12 days, to brute force the 20 megs. Of course this would probably generate a ton of false positives, so you would have to do this many times to watch for changes.
This would seem to be effective at deterring simple brute force memory scans to locate important variables.
>How recent are your copies of Smith's "Lensman" series?
hmm, about 3-4 years old. I preordered the whole series in early 96 and waited for months to get them. Finally got the last couple sometime in 97.
Of course I'd read the entire series before, it is nice to have a father whoe keep old fiction.
I seem to recall that states have controll over how their electoral votes are allocated, and I think that Maine has a proportional system, where if the vote split 40, 40, 20 then their electoral votes would be spread around 40%, 40%, 20%, subject to rounding of course.
So if we don't want a winners take all system for the electoral college then try to the states to change their allocation schemes.
I imagine it will do exactly what a F1 driver would do if his tire blew out or his vision was totally blocks. Probably crash... F1 cars run close enough to the edge that if something goes wrong they tend to go into the wall.
And remember in production, the comparison isn't with perfect its with the alternative. They would just have to be better not godlike.
I think thats a quote from some police dept, after they got flak for stopping an armed man with a non-lethal weapon causing him some injuries instead of restraining him without harming him. They pointed out that the alternative by the book method would have been to shoot him because he was threatening the shoot bystanders.
Actually with quicktime 4 the annoying nag screen it shows, asking you to upgrade to pro, is itself a quicktime movie. It you delete its.mov file then the free version doesn't nag you anymore and works normally.
I've got a AMD 386 DX 40 that except for ~10 hours of down time for moves and kernel upgrades has been running 24x7 for the last 4 years. I've never had problems with AMDs burning out if run with proper cooling. (I also have a K6-3 400, and a 800 Mhz Athlon.)
All the comments about fungus from outer space attacking the Mir and possibly satellites is amusing but the fungus in the article is _inside_ the space station, not outside. It was brought up from earth and lives on normal nutrients. It only damages metal and plastic as a by-product of its metabolism.
From the space.com article about this which is more informative:
"All the space microorganisms found inside spaceships originated on Earth," she said. "Most of them got into spacecraft on Earth and some of them were brought aboard with the visiting crews
...
Subsistence for the microorganisms was certainly not the metal, glass and plastic of those devices, said Natalia Novikova, a deputy chief of the Department at the Institute of Biomedical Problems (IBMP) in Moscow.
"They consume organic stuff which consists of skin epithelia, lipids and other products of human activity," Novikova said. "These products get into the station atmosphere from human breath, sweat etc....and stick to the station's surfaces."
I think your time scale is a bit off. In the 1870s the US had been an independant country for almost 100 years and had already fought its civil war. I'd say wide scale colonization was brought about by advances in sail powered ships, not steam propultion. Steam ships also somewhat predate the 1870s.
In 1864? 5? the Great Eastern steam ship was in New York harbor. That this was a double hulled all iron steam ship with enought range to cruise from England to Australia around the tip of Africa without refuelling. It was also about 7/8th the size of the Titanic.
Early steam ships had to predate this by quite a bit. But they didn't have the range to cross the atlantic under steam until the Great Western (a precurser to the Great Eastern). Actually the USS Atlanta was the first steam powered ship to cross the atlantic, but it also had sails which it used for about half the trip.
Slashdot Mirror
An apology in diplomatic matters such as these is the same as pleading guilty to a criminal offense. By apologizing, Bush would be proclaiming to the world that the spy plane should not be there in the first place, that the fighter pilot had the right to be buzzing an American plane in international air-space, and that China would have free go to continue such behavior in the future.
Very true, people should realize apologizing in this situation not like saying you are sorry when you bump into someone; which is just common courtesy. But it comes closest to apologizing after a fender bender. Unless you feel that the accident was entirely your fault and are about to agree to have your insurance cover everything you don't start out by apologizing to the other driver because that can be taken as an admission of fault and can be used by them or their lawyer to force you to pay for everything even if it was a situation where both parties were equally at fault, or even a case where the other driver appeared to be at fault.
This type of formal apology carries with it the implication of responsibility and it is by no means clear that the US is primarily responsible for this accident. No apology should be given.
They [the Chinese] probably don't even have all those nukes they keep whispering about. Have we ever seen them detonate one? Well have we? NO! They don't exist.
Ah, that would explain the newspaper articles about the non-existent explosion of china's imaginary nuclear weapons, for example here is one from cnn. And here is a link from greenpeace (not my favorite people) that contains a history of Chinese nuclear testing. How about a CIA paper on ICBM threats to the US that covers China's ICBMs. If you thing we've never seen China set off a nuclear weapon then you just haven't been paying attention!
Not to mention that Myst was bundled with almost every cd-rom drive and multimedia PC for the first 3 or 4 years they existed and its not surprising it moved huge numbers of copies.
>Picks and Shovels! The people who made out during the gold rush were the ones selling picks and shovels!
Don't forget selling beer, but you are right. The people who make most of the money in a gold rush are the suppliers. Because it is more reliable to outfit and equip most of the miners than it is to sit out there with a pick and hope to hit the motherload. Better to let others do that and just sell more to the succesfull ones.
>Note that I'm not talking about specifying this >per project; I mean the WHOLE THING. NASA should >be a dozen people in an office in Washington, >most of 'em accountants, a couple engineers and >scientists.
Not quite; if you want to cut back NASA it should be cut to a bunch of researchers and engineers who basically do experimental research and testing. Along the lines of the x-plane program. Think up something, build a prototype, use the prototype, collect data points, and refine. Then once they work out the bugs license the tech off to intertested parties and begin again. And not just one big thing, like the X-33, but a bunch of different tests at once. Try a bunch of things, don't get fixated on the one true way (TM)
Contract out full scale development and launching. Then follow your suggestion on holding contractors to their bids, and keep NASA from being the aerospace wellfare agency.
Also, this should minimize friction between parts of NASA. Prevent what happened to the DC-X. What a waste. McDonald Douglas built on their own nickle a protoype single stage to orbit vehicle (note the protype was never expected to reach orbit, too heavy, it was just to gather operational data) tested it, validated parts of the flight envelope, had plans to build a follow on the DC-Y, which would be capable of sub orbital ballistic flight, and the after gathering data on that, build the final single stage to orbit vehicle. They turned the DC-X prototype over to NASA, who tested it for a while, but declined to have anything to do with a followup, becuase it conflicted with their X-33 program.
I ran into this. I had a pair of 366 Celerons on a BP-6, payed a bit extra to get pre-tested at 550 chips (before Celerons were availble at 550) and they ran great for months. No problems. Then I tried to run a render on them (actually they were part of a mosix cluster that I ran the render on) and every singe time they would crash the render process. Dropped them back to stock 366 and they ran fine. The render process obviously hit a slow timing path that normal operation didn't.
AFAIK noone has released a comprehensive stress test program that attempts to stress all possible timeing paths in an inplace CPU, which is what you would have to do, since OCers don't have the timeing info worked out by the engineers.
Not really. A weapon, or object may be more or less capable of causing death. For example the star trek phasor on stun, which is frequently sited by proponents of non lethal weaponry as the holy grail can still cause death in some situations. i.e. stun someone who is speeding down the highway, or for a more military situation stun someone right after they pull the pin on a grenade. Pretty much anything could be used to cause death if someone tried hard enought. slightly lethal in this contex mean that in normal use there is a low possibility of causing death, as opposed to highly lethal like an M-16 which has a high possiblity of causing death. Not a certainty, someone could live through being hit with a burst from an assult rifle.
The first calculator I ever used my my dad's HP-21, which he bought when he was in college. The calcualator is older than I am and still works fine, I have it sitting on my desk right now.
Of course since I learned RPN first I can't stand to use a brain dead 'normal' calcuator.
The US already uses aircraft based on civilan models, such as the E-3 AWACS, the JSTARS, and the KC-135 all of which are based off the popular 707 aircraft. Having 747s wouldn't add to the problem, they have to have prominent military marking on them, and civilan airliners route away from war zones anyway, so they are unlikely to be mistaken for a ABL and shot down.
Roaring Penguin is great. I've got a 386dx40 handling a 1.5mbs dsl line with no problem.
I always liked the ornithopters from the game DuneII. You can't see them really well, but they look sort of like a dragon fly, large thin rounded wings that can flap and a jet thrust for propultion. Those scaled up and shot on screen would look amazing.
Actually a good, non destructive one is to walk up to a win9x box and open the run dialog and enter program.exe. Run it and maximize, (it is the win3.1 program manager interface) then ask the sales guy why this computer has win3.1 and not win9x on it.
Except that with cell phones that functionality changes a bit. Figure out how to power on this model of phone. Oh, type is some security code. Dial the phone number. Is it calling? No. OK now what button do I push on this phone to make it dial. OK, Send, Talk, Pound?
It's not hard to use a cell phone, even someone else's, but it is hardly standard.
I believe the previous poster is refering to the fact that the math co-processor chip (487 ?) you could buy to give a 486sx the math capabilitys of a 486dx was in fact a 486dx chip in a new package which totaly bypassed the original 486sx.
The point of using xor is not so much to keep them from knowing the value, as to keep them from finding the location of the value. Assuming you have the speed right, they could test a given 16 bit memory location in 1 second, but that doesn't help because they don't know which memory location to test. You are trying to make it harder to do a memory scan to locate variables, not place unbreakable(TM) encryption on them.
Assuming that they could restrict their scan to a 20 meg foot print, they would have about 2^20 16 bit addresses to scan, so it given your statement that it would take 1 second to break a 16 bit address it would only take 2^20 seconds, or about 12 days, to brute force the 20 megs. Of course this would probably generate a ton of false positives, so you would have to do this many times to watch for changes.
This would seem to be effective at deterring simple brute force memory scans to locate important variables.
>How recent are your copies of Smith's "Lensman" series?
hmm, about 3-4 years old. I preordered the whole series in early 96 and waited for months to get them. Finally got the last couple sometime in 97.
Of course I'd read the entire series before, it is nice to have a father whoe keep old fiction.
Ah, how about the side of the vehicle assembly building. You could play from a couple miles away :)
Of course not, only cats own their masters.
I seem to recall that states have controll over how their electoral votes are allocated, and I think that Maine has a proportional system, where if the vote split 40, 40, 20 then their electoral votes would be spread around 40%, 40%, 20%, subject to rounding of course.
So if we don't want a winners take all system for the electoral college then try to the states to change their allocation schemes.
I imagine it will do exactly what a F1 driver would do if his tire blew out or his vision was totally blocks. Probably crash... F1 cars run close enough to the edge that if something goes wrong they tend to go into the wall.
And remember in production, the comparison isn't with perfect its with the alternative. They would just have to be better not godlike.
I think thats a quote from some police dept, after they got flak for stopping an armed man with a non-lethal weapon causing him some injuries instead of restraining him without harming him. They pointed out that the alternative by the book method would have been to shoot him because he was threatening the shoot bystanders.
Actually with quicktime 4 the annoying nag screen it shows, asking you to upgrade to pro, is itself a quicktime movie. It you delete its .mov file then the free version doesn't nag you anymore and works normally.
I've got a AMD 386 DX 40 that except for ~10 hours of down time for moves and kernel upgrades has been running 24x7 for the last 4 years. I've never had problems with AMDs burning out if run with proper cooling. (I also have a K6-3 400, and a 800 Mhz Athlon.)
All the comments about fungus from outer space attacking the Mir and possibly satellites is amusing but the fungus in the article is _inside_ the space station, not outside. It was brought up from earth and lives on normal nutrients. It only damages metal and plastic as a by-product of its metabolism. From the space.com article about this which is more informative:
"All the space microorganisms found inside spaceships originated on Earth," she said. "Most of them got into spacecraft on Earth and some of them were brought aboard with the visiting crews
...
Subsistence for the microorganisms was certainly not the metal, glass and plastic of those devices, said Natalia Novikova, a deputy chief of the Department at the Institute of Biomedical Problems (IBMP) in Moscow.
"They consume organic stuff which consists of skin epithelia, lipids and other products of human activity," Novikova said. "These products get into the station atmosphere from human breath, sweat etc....and stick to the station's surfaces."
My 386 linux router had one, until I moved it into my PIII-450. How else could I load those old original 5 1/4" games.
Omega runs so nicely on a PIII.
I think your time scale is a bit off. In the 1870s the US had been an independant country for almost 100 years and had already fought its civil war. I'd say wide scale colonization was brought about by advances in sail powered ships, not steam propultion. Steam ships also somewhat predate the 1870s.
In 1864? 5? the Great Eastern steam ship was in New York harbor. That this was a double hulled all iron steam ship with enought range to cruise from England to Australia around the tip of Africa without refuelling. It was also about 7/8th the size of the Titanic.
Early steam ships had to predate this by quite a bit. But they didn't have the range to cross the atlantic under steam until the Great Western (a precurser to the Great Eastern). Actually the USS Atlanta was the first steam powered ship to cross the atlantic, but it also had sails which it used for about half the trip.