Actually, you probably saw better performance with your Ti 4400 than someone with an FX 5200 would see.
First, the Ti 4400 just doesn't support some of the slower stuff that the game is trying to do - you miss out on stuff like heat effects, while the FX 5200 will try to do all of that.
Second, I'm pretty sure the 4400 actually has more render pipes on it than the 5200, which means it's slightly faster overall.
Between those two effects, I wouldn't be supprised if there was a 10-15 FPS difference between the two cards, in favor of the 4400.
Using the version of DirectX to refer to video card capibilities isn't nessisarily the best plan, but it's pretty common. More useful would probably be to refer to the pixel shader verson..
I had been playing through the origional half-life for the last couple weeks, and after it just forgot about my quicksave I just gave up. It's got some pretty nice concepts, and the areas are awesome, but there's nothing really new in it, and they use some cheesy tricks to make it hard.
The data type you're looking for is the string. For this specific problem, you don't need to do any mathematical operations on any numbers larger than 10 digets - which will hopefully fit in a 32 bit integer, but may not.
Automatic security updates are a hard problem with significant potential for exploits. Think about it for a second - an automatic security update is "Automatically downloading and running arbitrary code on your machine".
Now, they're probably a good idea, but not nessisarily the first thing that should be implemented.
Because of things like scripts, a NX bit doesn't fully solve the problem - in fact, it only solves one very specific aspect of the problem: buffer overflows in C & C++ code.
We have the following bug now: A JPEG can include arbitrary machine code that when parsed by Mozilla will be executed. Given A.) NX is implemented in the hardware, and OS (incl. standard libraries) and B.) Mozilla isn't written to make it not work -- then this bug won't matter, the JPEGs will just be malformed.
Even with NX though, it's easy to imagine a bug where instead of executing arbitrary machine code in the JPEG, Mozilla would execute arbitrary javascript code as "fully trusted". Realistically, there's no difference security-wise between these two issues - both ways the user has been 0wned - you can even use the second bug to emulate the former:
The best realistic way to solve this class of problems is to use and re-use open-source code for a long time. It's been a while since a bug like this has come up in, for example, mutt.
Another good idea is to A.) Try to minimise the use of C and C++, writing only specific routines in them and using a higher level language to glue it together. B.) Don't let that higher level language also be the user-scripting language for the application. and C.) Don't implement dangerous things like filesystem access in the scripting language OR don't ever auto-load scripts.
That's nice, assuming that you don't need scripting functionality anywhere - or at least that all scripts are incapible of doing anything at all dangerous.
now, the annual energy output of our sun is about 121 * 10^41 ergs. this is enough to power about 2.7 * 10^56 single bit changes on our ideal computer; enough state changes to put a 187-bit counter through all its values. if we build a dyson sphere around the sun and captured all of its energy output for 32 years, without any loss, we should power a computer to count up to 2 ^ 192. of course, it wouldn't have the energy left over to perform any useful calculations with this counter.
but that's just one star, and a measly one at that. a typical supernova releases something like 10^51 ergs. (about a hundred times as much energy would be released in the form of neutrinos, but i let them go for now.) if all this energy could be channeled into a single orgy of computation, a 219-bit counter could be cycled through all of its states.
these numbers have nothing to do with the technology of the devices; they are the maximum that thermodynamics will allow. and they strongly imply that brute-force attracks against 256-bit keys will be infeasable until computers are built from something other than matter and occupy something other than space.
Yes, if you overstress your alcohol processing capacity alcohol can be poisonous, but reasonable amounts of it just break down in to sugars pretty quick.
How is it "the most damaging food product you can put in your body... far worse than... pesticides"?
You're aware that there exist computers that are not x86 compatible, right? You know that people really do exist who have them, use them, and run linux on them, right?
There is only one way to cause conservation to occur - raise prices. If there was a $7/gallon tax on gasoline (but no tax on diesel fuel), that would reduce gas usage pretty quick. Same with water/electricity/whatever.
"We shouldn't worry about advancing technology because there are still people starving in the world." Second best argument ever. (The best argument is obviously "Think of the children!")
There are charities / international aid groups that deal with the starving people problem. I'm sure they would claim that they need more money - but so would everyone else, if you really care send some money to Christian's Children's Fund or something.
Since that issue is in the hands of perfectly competant organisations that have been dealing with it pretty well for hundreds of years, we can get back to making the world a better place for the rest of us, and improving communication infastructure is a good way to do that.
Another thing that should be getting better funding is pure scientific research, which has been shown time and time again to pay for itself thousands of times over - heck, we might develop high-protien alge or something that could make starving people a thing of the past.
I really don't understand this concept that bandwidth isn't useful. Are you saying there would be no value to free multiparty voice conferencing? Video Conferencing? Video Chat?
Imagine students getting tutored over video chat by volunteers...
How about FMV/3d web sites? A PBS High-Def peercast?
There is probably a point where coming up with productive things to do with bandwidth is a problem - that point is definately upwards of a terabit/second for home internet.
With a collision attack, you can perform an attack that matters - here's an example:
Imagine that Microsoft won't sign any audio drivers for Windows XP that allow raw audio data to be output to disk. Also imagine that you are the driver release engineer at Creative (Sound Blaster division) and you want to release a driver that can do that.
What you do is build both drivers (one that Microsoft will sign, and one that you want to release with the "unacceptable" feature) with a large static data buffer that isn't used in the binary. You then try to modify both buffers in such a way as the two files will have the same hash (doesn't matter what hash, just that it's the same). This will take about 2^40 worth of work for MD5 instead of the 2^64 that it should take because of this security issue.
Once you've created your two binaries with the same hash, you send the acceptable binary to Microsoft and they sign it. Then, in the release section of your website you post the other binary with the signature you got from Microsoft... and the signature verifys just like they signed it.
There is also a break in the digital check situation, *if* the digital check protocal has random padding (many do) *and* the payee generates the check (also possible).
Slashdot Mirror
Actually, you probably saw better performance with your Ti 4400 than someone with an FX 5200 would see.
First, the Ti 4400 just doesn't support some of the slower stuff that the game is trying to do - you miss out on stuff like heat effects, while the FX 5200 will try to do all of that.
Second, I'm pretty sure the 4400 actually has more render pipes on it than the 5200, which means it's slightly faster overall.
Between those two effects, I wouldn't be supprised if there was a 10-15 FPS difference between the two cards, in favor of the 4400.
Using the version of DirectX to refer to video card capibilities isn't nessisarily the best plan, but it's pretty common. More useful would probably be to refer to the pixel shader verson..
I had been playing through the origional half-life for the last couple weeks, and after it just forgot about my quicksave I just gave up. It's got some pretty nice concepts, and the areas are awesome, but there's nothing really new in it, and they use some cheesy tricks to make it hard.
So he'd be a step up on Bush as president of the USA?
The data type you're looking for is the string. For this specific problem, you don't need to do any mathematical operations on any numbers larger than 10 digets - which will hopefully fit in a 32 bit integer, but may not.
Automatic security updates are a hard problem with significant potential for exploits. Think about it for a second - an automatic security update is "Automatically downloading and running arbitrary code on your machine".
Now, they're probably a good idea, but not nessisarily the first thing that should be implemented.
We have the following bug now: A JPEG can include arbitrary machine code that when parsed by Mozilla will be executed. Given A.) NX is implemented in the hardware, and OS (incl. standard libraries) and B.)
Mozilla isn't written to make it not work -- then this bug won't matter, the JPEGs will just be malformed.
Even with NX though, it's easy to imagine a bug where instead of executing arbitrary machine code in the JPEG, Mozilla would execute arbitrary javascript code as "fully trusted". Realistically, there's no difference security-wise between these two issues - both ways the user has been 0wned - you can even use the second bug to emulate the former:The best realistic way to solve this class of problems is to use and re-use open-source code for a long time. It's been a while since a bug like this has come up in, for example, mutt.
Another good idea is to A.) Try to minimise the use of C and C++, writing only specific routines in them and using a higher level language to glue it together. B.) Don't let that higher level language also be the user-scripting language for the application. and C.) Don't implement dangerous things like filesystem access in the scripting language OR don't ever auto-load scripts.
That's nice, assuming that you don't need scripting functionality anywhere - or at least that all scripts are incapible of doing anything at all dangerous.
Ack, didn't grab the attribution:
The quote is from
bruce schneier, applied cryptography, p 158
in regards to the strength of 256-bit encryption:
now, the annual energy output of our sun is about 121 * 10^41 ergs. this is enough to power about 2.7 * 10^56 single bit changes on our ideal computer; enough state changes to put a 187-bit counter through all its values. if we build a dyson sphere around the sun and captured all of its energy output for 32 years, without any loss, we should power a computer to count up to 2 ^ 192. of course, it wouldn't have the energy left over to perform any useful calculations with this counter.
but that's just one star, and a measly one at that. a typical supernova releases something like 10^51 ergs. (about a hundred times as much energy would be released in the form of neutrinos, but i let them go for now.) if all this energy could be channeled into a single orgy of computation, a 219-bit counter could be cycled through all of its states.
these numbers have nothing to do with the technology of the devices; they are the maximum that thermodynamics will allow. and they strongly imply that brute-force attracks against 256-bit keys will be infeasable until computers are built from something other than matter and occupy something other than space.
You have a source?
... far worse than ... pesticides"?
Yes, if you overstress your alcohol processing capacity alcohol can be poisonous, but reasonable amounts of it just break down in to sugars pretty quick.
How is it "the most damaging food product you can put in your body
Why would you ever use public key encryption for this sort of thing? If you aren't, why would you ever need a symetric key the large?
The compromise is Approval Voting
Any attempt to address that problem should be designed specifically for that problem - not be arbitrary like the electoral college system.
Probably the cleanest system for fixing it is proportional representation.
You're aware that there exist computers that are not x86 compatible, right? You know that people really do exist who have them, use them, and run linux on them, right?
The laser disk version was good in this respect.
Currently, Linux is a bit ahead of FreeBSD in drivers for a normal desktop system. Not by too far, but still a bit ahead.
Defense from who? If I were Norway or France, the attacker I'd be most afraid of is the USA.
I'd have to bet that Debian's market share in the mail server arena is greater than Mozilla's.
I'd be that's a bug in slashcode.
There is only one way to cause conservation to occur - raise prices. If there was a $7/gallon tax on gasoline (but no tax on diesel fuel), that would reduce gas usage pretty quick. Same with water/electricity/whatever.
"We shouldn't worry about advancing technology because there are still people starving in the world."
Second best argument ever. (The best argument is obviously "Think of the children!")
There are charities / international aid groups that deal with the starving people problem. I'm sure they would claim that they need more money - but so would everyone else, if you really care send some money to Christian's Children's Fund or something.
Since that issue is in the hands of perfectly competant organisations that have been dealing with it pretty well for hundreds of years, we can get back to making the world a better place for the rest of us, and improving communication infastructure is a good way to do that.
Another thing that should be getting better funding is pure scientific research, which has been shown time and time again to pay for itself thousands of times over - heck, we might develop high-protien alge or something that could make starving people a thing of the past.
I really don't understand this concept that bandwidth isn't useful. Are you saying there would be no value to free multiparty voice conferencing? Video Conferencing? Video Chat?
Imagine students getting tutored over video chat by volunteers...
How about FMV/3d web sites? A PBS High-Def peercast?
There is probably a point where coming up with productive things to do with bandwidth is a problem - that point is definately upwards of a terabit/second for home internet.
If the only humans left are you, Britney, and Christina, we might as well give up on the continuation of the human race anyway...
With a collision attack, you can perform an attack that matters - here's an example:
Imagine that Microsoft won't sign any audio drivers for Windows XP that allow raw audio data to be output to disk. Also imagine that you are the driver release engineer at Creative (Sound Blaster division) and you want to release a driver that can do that.
What you do is build both drivers (one that Microsoft will sign, and one that you want to release with the "unacceptable" feature) with a large static data buffer that isn't used in the binary. You then try to modify both buffers in such a way as the two files will have the same hash (doesn't matter what hash, just that it's the same). This will take about 2^40 worth of work for MD5 instead of the 2^64 that it should take because of this security issue.
Once you've created your two binaries with the same hash, you send the acceptable binary to Microsoft and they sign it. Then, in the release section of your website you post the other binary with the signature you got from Microsoft... and the signature verifys just like they signed it.
There is also a break in the digital check situation, *if* the digital check protocal has random padding (many do) *and* the payee generates the check (also possible).