In other words, he found the problem then fixed it. Forgive my ignorance, but how else would you possibly go about it? Apply random patches until one kind of works?
Break into Skype's servers/bribe skype employee/etc, get copy of source, change source, compile? Perhaps he's just pointing out he didn't do anything along those lines?
Considering this incident on its own, yes. But I can't help thinking it would be better to fix this once and for all than have to change every single application that tries this kind of stuff.
Like I said, since it's burned into the chip, there's no real way of 'masking' those registers as something else.
Can't you get the OS to look through the code before it's executed and replace the offending instruction with a simulated version, like they do to workaround the pentium f00f bug?
Also, EVERYONE complaining about this is a spammer. They don't think they are spammers, but they are. If the recepients want you on their email, they will put you in their address book and you won't be charged a thing.
You overestimate the typical AOL user. They probably won't think to add the shop they just bought from to their address book - but they sure as hell want to receive their order confirmation.
1) AMD can't do this because some drivers may need to leverage/use HyperTransport features, and other processor-specific features, such a auto-clock throttling features when the processor overheats (SpeedStep? Cool'n'Quiet? PowerNow! -- whatever each vendor calls it.) So these drivers need CPUID to work properly.
There are flags for capabilities like this quite apart from the CPUID. CPUID is meant to be purely informative.
2) AMD does do this in debug versions of their chip. However, these are not available for public consumption.
This would seem to contradict your statement 1). Anyway, if they're already making such CPUs, it should be easy to switch to selling CPUs set up that way.
AMD doesn't AFAIK use software-updateable microcode like intel, so you couldn't change it at that level. An OS-level patch like gets used to work around the pentium f00f bug would almost certainly work though.
AMD should set their CPUID to "GenuineIntel". It's for interoperability grounds - Intel have shown they will use it to try and damage the performance of programs on AMD machines - so there shouldn't be any trademark issue, and it would stop this kind of crap once and for all.
I think it's a great idea, if not specific to spam. People scoff at having sounds for desktop events, but I couldn't manage without them - I rely on them to know when things are happening. Likewise I like to be using as many monitors as possible - it just gives more space for outputting information to me. However, I only seem to be able to input information one way at a time - I don't have enough hands to use keyboard and mouse together, and voice recognition isn't good enough as yet for me to rely on my microphone for text input. Using feet as well just means more ways to input data at the same time - even if it was just as simple as being able to move the cursor while typing with both hands.
Because Apple refuses to license the DRM technology they're using. They're making too much off iTMS, they want it all to themselves. Real attempted to sue them to get them to license it, but I don't think they've succeeded, at least as yet.
The end result is that such viruses could not spread as fast or as far as their Windows counterparts.
I think you overestimate users. I get "Install this critical update from Microsoft" emails at a rate of around two per second. Basic html mockup and an attached executable, obvious as pie, but they're being sent out by someone. There are plenty of stupid users around.
There's speculation that the last one is just random letters left to fuck with us. If so I think that's pretty neat, but it of course renders such efforts useless.
Slashdot Mirror
Break into Skype's servers/bribe skype employee/etc, get copy of source, change source, compile? Perhaps he's just pointing out he didn't do anything along those lines?
Considering this incident on its own, yes. But I can't help thinking it would be better to fix this once and for all than have to change every single application that tries this kind of stuff.
Can't you get the OS to look through the code before it's executed and replace the offending instruction with a simulated version, like they do to workaround the pentium f00f bug?
How can my observation of a murder be alarming when I only observed one of six billion people?
You overestimate the typical AOL user. They probably won't think to add the shop they just bought from to their address book - but they sure as hell want to receive their order confirmation.
Erm, what on earth did you expect. Corporations by definition are devoted solely to making money.
There are flags for capabilities like this quite apart from the CPUID. CPUID is meant to be purely informative.
2) AMD does do this in debug versions of their chip. However, these are not available for public consumption.
This would seem to contradict your statement 1). Anyway, if they're already making such CPUs, it should be easy to switch to selling CPUs set up that way.
AMD doesn't AFAIK use software-updateable microcode like intel, so you couldn't change it at that level. An OS-level patch like gets used to work around the pentium f00f bug would almost certainly work though.
AMD should set their CPUID to "GenuineIntel". It's for interoperability grounds - Intel have shown they will use it to try and damage the performance of programs on AMD machines - so there shouldn't be any trademark issue, and it would stop this kind of crap once and for all.
The university is forbidding doing it against their own servers. I'd say that pretty much shows their stance on it.
Changing it back to a D, then going in later and changing it to an A again, is highly encouraged, however.
...which will be removed by Apple's next firmware update.
I think it's a great idea, if not specific to spam. People scoff at having sounds for desktop events, but I couldn't manage without them - I rely on them to know when things are happening. Likewise I like to be using as many monitors as possible - it just gives more space for outputting information to me. However, I only seem to be able to input information one way at a time - I don't have enough hands to use keyboard and mouse together, and voice recognition isn't good enough as yet for me to rely on my microphone for text input. Using feet as well just means more ways to input data at the same time - even if it was just as simple as being able to move the cursor while typing with both hands.
If AOL users were the type to do that, they'd have done so already. This will succeed. I know too many AOL users.
Because Apple refuses to license the DRM technology they're using. They're making too much off iTMS, they want it all to themselves. Real attempted to sue them to get them to license it, but I don't think they've succeeded, at least as yet.
Konqueror here. I think that would be a little better.
(It's a _joke_, laugh)
I think you overestimate users. I get "Install this critical update from Microsoft" emails at a rate of around two per second. Basic html mockup and an attached executable, obvious as pie, but they're being sent out by someone. There are plenty of stupid users around.
There's speculation that the last one is just random letters left to fuck with us. If so I think that's pretty neat, but it of course renders such efforts useless.
They're not trying to prevent anything. They're trying to sell more TVs, and I suspect they'll succeed at this. Piracy is just an excuse.
Then whence the "Not at all" comment?
There is no such post.
Ah, I get it, you're trying to be incoherent so it's not as obvious that you lost.
That might not be such a bad idea. Remember the 486 overclocked to run half-life?
You're seriously denying having written that?
What effect?
Verbal LSD
I don't see anything quoted, except my question.
Look back at the post where I wrote "right back at you".
http://www.gnunet.org/
My money's on gnunet. Not only does it have the whole anonymity thing, but it also actually works quite well as a filesharing network.